DiamondLightSource / DiamondLightSource/mx-bluesky
Hyperion-blueapi reports PATH_PROVIDER not defined, fails collection in commissioning mode
- Dominant language
- Python
- Stars
- 4
- Forks
- 5
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 2
Description
When `hyperion-blueapi` is run in commissioning mode
* graylog message appears during panda setup:
```
File "/dls_sw/i03/software/bluesky/mx-bluesky_1.6.4/dodal/src/dodal/common/beamlines/beamline_utils.py", line 175, in get_path_provider
return PATH_PROVIDER
^^^^^^^^^^^^^
NameError: name 'PATH_PROVIDER' is not defined
```
* When no crystal is found, UDC stops instead of continuing
This is due to the path provider and the commissioning mode signal not being registered during beamline instantiation.
(the path provider is also not set during vanilla in-process UDC mode, but it does not cause an error as the exception is never bubbled up and it only determines the PCAP file location).
## Acceptance Criteria
- PCAP files are created
- hyperion-blueapi works in commissioning mode
Contributor guide
Assessment
This issue has not been assessed yet.