Implement BPM device

[gubaidulinvadim]

The idea is to do more or less the same as for magnets except that BPM names have to be unique in the lattice. An abstract BpmModel has to be implemented as for magnet.

However 2 cases appears:
Control system BPM having offsets (and tilt) implemented and BPM having only a position.

• First case 5 DevciceAccess are required in the pydantic model: h,v,offseth,offsetv,tiltangle (in that case, h,v reading from the CS already add the offsets and already rotate the coordinates)
• Second case only raw h and v come from the CS and offseth, offsetv and tilt angle have to be handled internally in pyaml.

We can focus first on the second case.

Concerning the CS, RBpmArray,RWBpmTiltScalar and RWBpmOffsetArray has to be implemented here and added here

Concerning simulators, RBpmArray, RWBpmTiltScalar and RWBpmOffsetArray has to be implemented here and added here

RBpmArray for [h,v]
RWBpmOffsetArray for [offseth,offsetv]
RWBpmTiltScalar for the tilt angle

For arrays of BPM, it has also be implemented here following same magnet arrays implementation.

[kparasch]

Does the tilt represent a voluntary tilt of the bpm or is it there to correct for involuntary rotations?
If it is the second case, should we treat bpm calibrations and cross-talks also here?

[gubaidulinvadim]

@kparasch, RW (read/write) implies that it is controllable.

[TeresiaOlsson]

I think it also needs to be able to handle the various different ways different machines currently have implemented their BPMs in MML. So far I have found these cases:

• As individual BPMs
• As an orbit object in the control system
• Using the group feature of TANGO

This seems to me like a device where people really have made use of the special function functionality in MML so potentially some review looking at the MML config for different labs could be required to understand the requirements.