bliss-tomo merge requestshttps://gitlab.esrf.fr/tomo/bliss-tomo/-/merge_requests2024-03-26T20:15:28+01:00https://gitlab.esrf.fr/tomo/bliss-tomo/-/merge_requests/227New align2024-03-26T20:15:28+01:00Valentin VallsNew alignWould be better to rebase it on top of !224
I do not expect it to work before BLISS 2.1.
- Feature a `Procedure` object, that i would like to expose in more contexts. Basically to identify a procedure in "user" point of view, which is...Would be better to rebase it on top of !224
I do not expect it to work before BLISS 2.1.
- Feature a `Procedure` object, that i would like to expose in more contexts. Basically to identify a procedure in "user" point of view, which is usually not a scan.
- Create an align procedure in order to be displayed in daiquiri.
- [ ] Rework it as sequence
- [ ] Store nabu result in the sequence
- [ ] OR feature shared params in the `procedure`
- [ ] Optionally feature `request_user_input` to wait for user input during the procedureValentin VallsValentin Vallshttps://gitlab.esrf.fr/tomo/bliss-tomo/-/merge_requests/224Draft: Rework align2024-03-26T19:07:28+01:00Valentin VallsDraft: Rework alignRework the alignment script in order to be used in Daiquiri.
- [x] Clean up the actual code
- [ ] Rework it as a "normalized" sequence
- [ ] Add some regression tests
- [ ] Check what we can do with daiquiriRework the alignment script in order to be used in Daiquiri.
- [x] Clean up the actual code
- [ ] Rework it as a "normalized" sequence
- [ ] Add some regression tests
- [ ] Check what we can do with daiquiriValentin VallsValentin Vallshttps://gitlab.esrf.fr/tomo/bliss-tomo/-/merge_requests/220Draft: add possibility to define one detector axis per tomo detector like on ...2024-03-07T15:27:25+01:00Clemence MuzelleDraft: add possibility to define one detector axis per tomo detector like on bm05add unit test for tomo detector with detector axis configured on it
prevent to configure detector axis on tomo detectors and tomo detectoradd unit test for tomo detector with detector axis configured on it
prevent to configure detector axis on tomo detectors and tomo detectorClemence MuzelleClemence Muzellehttps://gitlab.esrf.fr/tomo/bliss-tomo/-/merge_requests/214Allow to interrupt task when we push a new version of a PR2023-11-24T17:37:32+01:00Valentin VallsAllow to interrupt task when we push a new version of a PRValentin VallsValentin Vallshttps://gitlab.esrf.fr/tomo/bliss-tomo/-/merge_requests/200Draft: tiling: Added continuous scan2024-03-05T09:22:19+01:00Valentin VallsDraft: tiling: Added continuous scanRelated to https://gitlab.esrf.fr/ui/daiquiri-tomo/-/issues/337
This create a new option to tiling scan and sequence to make it work with a continuous scan.
- Create an helper to use fscan like default BLISS scans
- Update `tiling_runn...Related to https://gitlab.esrf.fr/ui/daiquiri-tomo/-/issues/337
This create a new option to tiling scan and sequence to make it work with a continuous scan.
- Create an helper to use fscan like default BLISS scans
- Update `tiling_runner` to support fscan on sz
- Update the tiling sequence with the `continuous` optional argument
- [ ] When a single vertical scan is only needed the continuous scan also have to be used
- [ ] Test that the new implementation works at beamlineValentin VallsValentin Vallshttps://gitlab.esrf.fr/tomo/bliss-tomo/-/merge_requests/190Draft: Rework menu to follow bliss menu API2023-07-21T19:11:22+02:00Valentin VallsDraft: Rework menu to follow bliss menu APIHere is an example of what we can do.
BLISS provides a generic `menu` to call such menu on a device
```
import tomo.optic.revolvedpeter_optic_dialog
config.get("test_revolvedpeter")
menu(test_revolvedpeter)
```
We could try to implem...Here is an example of what we can do.
BLISS provides a generic `menu` to call such menu on a device
```
import tomo.optic.revolvedpeter_optic_dialog
config.get("test_revolvedpeter")
menu(test_revolvedpeter)
```
We could try to implement that for some of them.
![image](/uploads/f62120e2b5f27263eba794e5a9e56d1b/image.png)Valentin VallsValentin Valls