Muon "RF": Specific equipment control for items in the RF ranges tasks

[KathrynBaker]

As someone using IBEX on the Muon instruments I want to be able to use the suite of "RF equipment" to undertake experiments.

Acceptance Criteria

• Requirements for component sharing and saving and restoring device settings are refined (Muon "RF": Refinement of requirements for components and saving and storing device settings #7369)
• There is an IOC to interact with the DG645
• New OPI for the DG645 is created (Muon "RF": DG645 IOC and OPI - more like the device #7367)
• There are three DG645 IOCs (Muon "RF": 3 DG645 IOCs #7366)
• There are 3 IOCs to control the Aeroflex Signal Generators (Muons: IOC & OPI for Aeroflex Signal Generator #6079)
• The capture of images from oscilloscopes has been explored (Driver for Tektronix 3000 series dpo/dso #7318)
• The storing of images and raw data from oscilliscopes is available (see also Muons: Capture Oscilloscope Pictures #6084) - being done via waveforms in blocks
• The interaction with the amplifiers is designed (Muon "RF": Amplifiers - Design #7368) - with the use of the DIO in question this was not needed
• Design of appropriate way to share components between instruments (Muon "RF": Copy Components from one instrument to another - Design #7389)
• Design of appropriate way to save and restore settings for devices which vary by experiment (Muon "RF": Save and Restore Device Settings - Design #7393)
• Implementation of sharing components between instruments (Copy components from one instrument to another - implementation #7515)
• Generate folder and XML for saving and restoring PVs (Save and Restore Device Settings - XML and folders #7854)
• Update blockserver for saving and restoring PVs (Save and Restore Device Settings - Blockserver #7855)
• Add GUI aspects for saving and restoring PVs (Save and Restore Device Settings - Blockserver #7856)

Notes

• This umbrella ticket supersedes any created before September 2022, it has come out of discussions with the instrument scientists (see Muon RF - check what needs to be done [Timebox: 2.5 days] #7298 for the initial work), this covers the work to be done moving forwards rather than a wiki page, as a wiki page would not be detailed enough at this time
• RF is often used in quotes as that is a handy label for the equipment, but is isn't always used in RF experiments
• There are a number of design tickets which can be estimated now, and they will generate implementation tickets afterwards which can then be estimated later
• The remaining two design tickets will be generated after further discussion with the instrument scientists as scope and behaviour are not yet understood
• This was edited to reflect the priority order of the tasks post the meeting for Muon "RF": Refinement of requirements for components and saving and storing device settings #7369, however if ready lower priorities should be completed first. For example, the amplifier interaction requires input from multiple divisions, whilst the following two are entirely within IBEX

[KathrynBaker]

Talking with ISs - for the scope want to be able to select and store raw traces as well as pictures from the scope

[KathrynBaker]

The key device settings for this equipment were handled in a different way to the plans above in the end as there were other alternatives. The save/restore via XML may become handy in the future, it will be added to our list, a new umbrella ticket created and the sub-tickets renamed.