Update docs

ISISComputingGroup · Oct 8, 2024 · ac720b9 · ac720b9
1 parent 695ad61
commit ac720b9
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/doc/architectural_decisions/002-use-ophyd-async.md b/doc/architectural_decisions/002-use-ophyd-async.md
@@ -34,6 +34,4 @@ We will use `ophyd-async`.
 - `ophyd-async` will allow us to do fly scanning, if required in future, more easily than `ophyd`
 - Developers will need to understand more details about `asyncio`
 - Developers will have to write somewhat less boilerplate code in `ophyd-async` as compared to `ophyd`
-- Our devices should be more comparable to other facilities on site (e.g. DLS) who are using `ophyd-async`.
-- Less expertise with this library on site (mitigation: don't do too much which is very complicated with it)
-- Potentially duplicates some of mantid's functionality: (mitigation: use scipp for "simple" things, use mantid in future if people want to do "full" data reduction pipelines)
+- Our devices should be more comparable to other facilities on site (e.g. DLS) who are using `ophyd-async`.
diff --git a/doc/architectural_decisions/004-use-scipp.md b/doc/architectural_decisions/004-use-scipp.md
@@ -17,4 +17,6 @@ We will be using scipp.
 - `scipp` is being developed at ESS with past input from STFC, so is well suited for neutron counts data.
 - `scipp` has a `numpy`-like interface but handles units and uncertainties by default under-the-hood.
 - Neither `numpy` or `uncertanties` have exactly the functionality we would need, so the solution using them would be a mix of the libraries and our own code, there would be more places to go wrong. Maintainability.
-- Developing our own uncertainties library will take time to understand and then implement. All of the functionality that we need has been done beforehand, so better to not waste time & effort.
+- Developing our own uncertainties library will take time to understand and then implement. All of the functionality that we need has been done beforehand, so better to not waste time & effort.
+- Less expertise with this library on site (mitigation: don't do too much which is very complicated with it)
+- Potentially duplicates some of `mantid`'s functionality: (mitigation: use `scipp` for "simple" things, use `mantid` in future if people want to do "full" data reduction pipelines)