Currently, profile monitors' resolutions and pixel sizes are obtained by accessing the machine PVs. It would be useful to save them into a yaml file so that they can be accessed when the machine is off, or when creating virtual accelerator lattices without the need of logging into the control room servers.
Ideally, there should be a script to get all profile monitors info and save it in a yaml as follows:
<ELEMENT>:
name: <control system name>
shape:
- <n_rows>
- <n_cols>
pixel_size: <microns>
Example:
OTRH1:
name: OTRS:IN20:465
shape:
- 1040
- 1392
pixel_size: 18.59
OTRH2:
name: OTRS:IN20:471
shape:
- 1040
- 1392
pixel_size: 19.16
OTR2:
name: OTRS:IN20:571
shape:
- 1040
- 1392
pixel_size: 12.66
...
Currently, profile monitors' resolutions and pixel sizes are obtained by accessing the machine PVs. It would be useful to save them into a yaml file so that they can be accessed when the machine is off, or when creating virtual accelerator lattices without the need of logging into the control room servers.
Ideally, there should be a script to get all profile monitors info and save it in a yaml as follows:
Example: