DiamondLightSource / DiamondLightSource/mx-bluesky
Rotation scan disarm failed with "Unexpected acquisition id"
- Dominant language
- Python
- Stars
- 4
- Forks
- 5
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 2
Description
The eiger unstage for the rotation for
https://ispyb.diamond.ac.uk/dc/visit/cm40607-3/id/18379201
failed,
hyperion logs reported
```
ESC[32m[I 250618 10:17:20.088 read_hardware:25] Reading status of beamline for event, read_hardware_for_callbacks_during_collectionESC[0m
ESC[32m[I 250618 10:17:20.108 eiger:156] Waiting on filewriter to finishESC[0m
ESC[33m[W 250618 10:18:10.141 status:236] SubscriptionStatus(device=eiger_odin_nodes_node_0_error_status, done=False, success=False) has timed outESC[0m
ESC[33m[W 250618 10:18:10.142 status:236] SubscriptionStatus(device=eiger_odin_nodes_node_1_error_status, done=False, success=False) has timed outESC[0m
ESC[31m[E 250618 10:18:10.143 status:262] SubscriptionStatus(device=eiger_odin_nodes_node_0_error_status, done=True, success=False) encountered an error during _handle_failure()ESC[0m
<...>
```
In the OdinData Status panel in the synoptic, errors were reported:
```Unexpected acquisition id thau_12_3```
however the rotation name was 12_2
This seems to indicate that the errors may have been a hangover from the previous gridscan which should have been detected and were not.
The other possibility is that there is a race condition during staging of the eiger of odin initialisation
Contributor guide
Assessment
This issue has not been assessed yet.