-[Entry 1: Physical test using exe scripts I](#entry-1-physical-test-using-exe-scripts-i)
-[Entry 1: Physical test using exe scripts I](#entry-1-physical-test-using-exe-scripts-i)
-[2024-11-18:](#2024-11-18)
-[2024-11-18:](#2024-11-18)
-[Entry 1:](#entry-1)
-[Entry 1:](#entry-1-1)
-[Entry 2](#entry-2)
-[Entry 2](#entry-2)
-[2024-11-07:](#2024-11-07)
-[2024-11-07:](#2024-11-07)
-[Entry 1:](#entry-1-1)
-[Entry 1:](#entry-1-2)
-[Entry 2:](#entry-2-1)
-[Entry 2:](#entry-2-1)
-[Current situation:](#current-situation)
-[Current situation:](#current-situation)
...
@@ -48,11 +51,17 @@
...
@@ -48,11 +51,17 @@
## Entries 2024
## Entries 2024
### 2024-12-12
#### Entry 1:
Worked on some infrastructure; creating scripts which can pass parameters on to a conda-script
### 2024-12-11
### 2024-12-11
#### Entry 1: EditArrayMap fix
#### Entry 1: EditArrayMap fix
was able to fix this issue by inputting **13** input variables, not **12** as the UL documentation say. The MapIndex parameter, which is missing, is probably a typo.
was able to fix this issue by inputting **13** input variables, not **12** as the UL documentation says. The MapIndex parameter, which is missing, is probably a typo.
#### Entry 2: Inspecting API function parameters
#### Entry 2: Inspecting API function parameters
...
@@ -63,6 +72,12 @@ Created two (hopefully) useful functions, which can return info about functions
...
@@ -63,6 +72,12 @@ Created two (hopefully) useful functions, which can return info about functions
These can be found inside utils
These can be found inside utils
#### Etrny 3: Meeting with Unchained Labs (Docs, examples)
Had a meeting with Unchained Labs. Presented the issue from the last few days, pointed out that the documentation contains typos.
Bjorn was interested in use cases for the closed loop, where they could present some mimimum working examples.
