Description, motivation and use case
Both hardware_name and model_name need to be implemented.
This will allow to make the link between the different names in pyAML:
name = pyAML unique identifier.
hardware_name = control system name.
model_name = lattice name.
Proposed solution
Add new properties to pyAML elements:
hardware_name corresponding to the reference string in the control system.
model_name corresponding to the element name in the lattice if any (model_name is not unique).
These properties are accessible in all control modes (live, design, ...).
The hardware_name is accessible if a control system has been defined in configuration.
The model_name is accessible if a simulator has been defined in configuration.
Example
Sextupole.name # returns 'SX.12.3'
Sextupole.hardware_name # returns 'AN01-AR/EM/SX.03'
Sextupole.model_name # returns 'SX.12'
Description, motivation and use case
Both
hardware_nameandmodel_nameneed to be implemented.This will allow to make the link between the different names in pyAML:
name= pyAML unique identifier.hardware_name= control system name.model_name= lattice name.Proposed solution
Add new properties to pyAML elements:
hardware_namecorresponding to the reference string in the control system.model_namecorresponding to the element name in the lattice if any (model_nameis not unique).These properties are accessible in all control modes (live, design, ...).
The
hardware_nameis accessible if a control system has been defined in configuration.The
model_nameis accessible if a simulator has been defined in configuration.Example