Try to add a table

docs/developer/serial-crystallography-on-i24/how-to/run-a-collection.rst

@@ -155,7 +155,7 @@ Once all parameters have been set, press ``Start`` to run the
 collection. A stream log will show what is going on in the terminal.
 
 
-**NOTE** As of version `1.0.0`, the ``Set parameters`` button has been removed and
+**NOTE** As of version ``1.0.0``, the ``Set parameters`` button has been removed and
 the parameters will now be read from the edm and applied to the collection directly
 once the ``Start`` button is pressed. For previous versions however, the button must
 still be pressed before starting the collection. A copy of the parameter file and chip

docs/developer/serial-crystallography-on-i24/project-planning/roadmap.rst

@@ -8,32 +8,49 @@ Ongoing list of TODOs:
 
 1. Improve alignment of chip: get it to work correctly for multiple
  zooms.
+
  - Close to being completed (see issue #44)
+
 2. Refactor and fix the logger.
 3. Use callbacks for file IO eg. to write parameter and map files.
 4. Solution for enabling users to run mx-bluesky instead of old scripts: blocked by permission issues.
+
  - This should also allow us to stop using the Pilatus to make directories during an Eiger collection.
  - The preferred permanent solution is to run mx-bluesky on the beamline kubernetes cluster. I24 should be due to get on in shutdown 4 2024.
  - Other possibility is to run the ```blueapi`` server on procServ. An example of this has now been set up on ws002 on the beamline and is being tested.
  - A temporary workaround in place for beamline staff, who should be starting to run this for testing/in house beamtimes. Staff have started using this set up in September 24.
+
 5. Convert detector set up to use bluesky plans and ophyd_async devices.
+
  - Eiger device in dodal needs to be converted to ophyd_async and updated to work with different Eigers on several beamlines.
  - Investigate using the existing Pilatus in ophyd_async which writes HDF5 instead of CBFs, but we may want to make a CBF-writing Pilatus. However, the Pilatus detector is due to be removed soon.
+
 6. Start looking into moving away from edm screens towards a web-based GUI.
+
  - Prepare generic react components to match the features in the edms.
  - Components for things currently managed by general purpose PVs (eg. map).
  - OAV viewer.
+
 7. Implementation of serial tools to be used at XFELS.
+
  - Reinstate removed code from sacla and move it to bluesky.
  - Add any plans/devices that might be needed for other locations.
+
 8. Reinstate full mapping code using bluesky.
-
-
-
 
 (TBC…)
 
 
+.. list-table:: Roadmap
+ :widths: 25 25 25
+ :header-rows: 1
+
+ * - Work Ongoing
+ - Rough Timeline
+ - Completed
+ * - Improve alignment
+ - Nov. 24
+ - :material-regular:`pending;2em` 
 
 
 Experiment types required