update configuration of smaract in optics hutch and experimental hutch. Correct some parameters in the readout of XBPMs and BIM. We also added an example for a Smaract stage in the user_template.yaml
#218
It would be great if Christian could have a look at this and merge (or pull or whatever)
We think that the readout priority should be baseline for the gains and the general configuration of the amplifiers, but it should be monitored for reading out the actual signals. In the bl_optics_hutch.yaml, the xbpm has readout priority monitored in all cases. This configuration is currently commented out because we are using the MCS to read the XBPM in the optics hutch. So not so critical at the moment...
It would be great if Christian could have a look at this and merge (or pull or whatever)
We think that the readout priority should be baseline for the gains and the general configuration of the amplifiers, but it should be monitored for reading out the actual signals. In the bl_optics_hutch.yaml, the xbpm has readout priority monitored in all cases. This configuration is currently commented out because we are using the MCS to read the XBPM in the optics hutch. So not so critical at the moment...
appel_c
was assigned by diaz2026-06-02 15:51:07 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It would be great if Christian could have a look at this and merge (or pull or whatever)
We think that the readout priority should be baseline for the gains and the general configuration of the amplifiers, but it should be monitored for reading out the actual signals. In the bl_optics_hutch.yaml, the xbpm has readout priority monitored in all cases. This configuration is currently commented out because we are using the MCS to read the XBPM in the optics hutch. So not so critical at the moment...
@diaz Christian is out of office for 2 weeks. I will review it
looks good to me
OK great, thank you!