From 443c40c07cee93b1996005f9448de4f9108f9495 Mon Sep 17 00:00:00 2001
From: Illimar Rekand <illimar.rekand@uib.no>
Date: Fri, 3 Jan 2025 10:38:16 +0100
Subject: [PATCH] implement scripts into HPLC dil assay

---
 Electronic_Labnotebook/NotebookLog.md | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/Electronic_Labnotebook/NotebookLog.md b/Electronic_Labnotebook/NotebookLog.md
index 3771892..4822c02 100644
--- a/Electronic_Labnotebook/NotebookLog.md
+++ b/Electronic_Labnotebook/NotebookLog.md
@@ -7,6 +7,9 @@
 <details> 
   <summary> Table of Contents (click to expand) </summary>
 
+- [Entries 2025](#entries-2025)
+  - [2025-02-01](#2025-02-01)
+    - [Entry 1: HPLC dilution assay](#entry-1-hplc-dilution-assay)
 - [Entries 2024](#entries-2024)
   - [2024-31-12](#2024-31-12)
     - [Entry 1: Dictionary](#entry-1-dictionary)
@@ -49,7 +52,15 @@
 
 </details>
 
+## Entries 2025
 
+### 2025-02-01
+
+#### Entry 1: HPLC dilution assay
+
+Starting integrating the previous scripts into this assay. Wrapped the os.system() command in a function called "runEditExps" (I really think EditExps should be renamed, but to what?)
+
+Further adaptations made to EditExps so that it can also run experiment - idea is to create one single script which can perform all sorts of operations, including editing and running experiment, essentially replacing the .exe-files and having one "superscript" which can be reused for any given experiment.
 
 ## Entries 2024
 
@@ -69,7 +80,7 @@ Worked on some infrastructure; creating scripts which can pass parameters on to
 flowchart TD;
     subgraph 64-bit Conda environment
       subgraph Layer 1  
-          Comment1(Calculations, e.g. volume, are performed and passed down)
+          Comment1(Calculations, e.g. volume, are performed and passed down in input_dict )
           Layer1.py 
       end
     end
@@ -85,13 +96,13 @@ flowchart TD;
       Layer1.py-->|Required+Optional parameters|EditExps;
       EditExps-->ls10;
       subgraph Layer 4
-        Comment4(LSAPI)
-        Layer4
+        LSAPI
       end
-      ls10-->|Datatypes prepared for C# + </br> Default optional requirements set if not defined|Layer4;
+      ls10-->|Datatypes prepared for C# + </br> Default optional requirements set if not defined|LSAPI;
     end
 ```
 
+
 1) Layer1: Top layer, where calculations can be performed. 64-bit Python. Calculations and parameters are calculated here, and passed down.
 2) Layer2: EditExps New parameters are sent to this layer, which are in a 32-bit environment. 
 3) Layer3: ls10 In this layer, inputs are prepared to be compatible with the LSAPI
-- 
GitLab