added discussions

scienceautomation/index.html

@@ -82,7 +82,21 @@ <h3 class="paragraph-header">
             <p>
             <strong>9:30a-6p: 
 
-            </strong></em> Workshop
+            </strong></em> Workshop: Working with and building open source hardware for laboratory automation.
+            </p>
+            <p>
+            Discussion Theme 1: Current challenges of lab automation and open hardware
+            </p>
+            <p>
+            What are the challenges people are facing when trying to use or develop laboratory automation hardware? There are many different tools already available for laboratory automation, some of which are open source: e.g., OpenTrons, OpenFlexureMicroscope, Mothbox, but integrating them into experimental workflows or developing new tools that are compatible with them remains challenging.
+</p>
+<p>
+            </p>
+            <p>
+            Discussion Theme 2: Community Building, Goal Alignment, Calibration, and Shared Standards
+            </p>
+            <p>
+Shared infrastructure implies that we could run the same experiments on each other’s hardware, perhaps using common control algorithms. However, for that to be possible, we need to calibrate and optimize the tools such that they are actually interchangeable, flexible, robust and generalizable. Is this currently already happening? Could it happen? How could we improve data exchange, sharing methods, and learning best practices from the community?
             </p>
             <p>
             <strong>6-9:00p: 
@@ -100,18 +114,26 @@ <h3 class="paragraph-header">
             <p>
             <strong>9:30a-6p: 
 
-            </strong></em> Workshop
+            </strong></em> Workshop: Creating custom science workflows using open-source science hardware/software.
+            </p>
+            <p>
+            Discussion Theme 3: Where do we go from here?
+            </p>
+            <p>
+There are many different (small) communities working on open-source hardware for laboratory automation. Working together could be synergistic, but organizing a larger community also has overhead. What do we think are (realistic) plans for this community moving forward?
             </p>
             <p>
             <strong>6-9:00p: 
 
             </strong></em> Dinner <strong><a href="https://maps.app.goo.gl/YwmNHs2Hw9q7cZ4R7">at Big Time</a></strong>
             </p>
-            <h3 class="paragraph-header">
+
+
+            <h2 class="paragraph-header">
                 Resources
-            </h3>
+            </h2>
             <p class="paragraph-text">
-                Code, documentation, and other resources used in the April 2024 workshop can be found in this <a href="https://github.com/machineagency/POSE-workshop"><strong>GitHub repository</strong></a>.
+                Code, documentation, and other resources used in the April 2024 workshop can be found in this <a href="https://github.com/machineagency/POSE-workshop"><strong>GitHub repository</strong></a>. Other information such as a link to the Google drive should have been sent to participants in emails from Salt Hale.
             </p>
             <h3 class="paragraph-header">
                 Travel Policies