What needs changing in the OKS schema for configuration.
Going towards doing physics runs, so there may be some parameters that need setting up that weren't before.
For instance:
- Trigger types in ROD and TIM (per ROD/crate, global, or from RunConfig??)
- Trigger enables in TIM
- Different for cosmics and physics running and depends where resets and other things are coming from (but maybe get this from the LTP configuration)
- BC offset, TIM or ROD
- Other TIM parameters?
- Which BOC parameters to include, delays are useful, but for instance clock mode is a temporary thing used in raw scans.
These are probably transient, controlled by a scan or by methods:
- Whether to trap TIM, TTC or ROD triggers
- Formatters in expanded, edge mode etc.
Some suggestions from Peter.
- Add "ALL" to PowerParams? type
- Done, need to look at semantic changes
- The optional "errorMask" attribute is missing from the channel schema. Two of these may be defined, one for each of the input fibres.
- This needs adding
- The grouping of output, stream 0 and stream 1 fibre mappings in one optional class seems slightly strange to me, as in many cases only one of these need be defined.
- Putting the two points above together, maybe we should now choose to fill all "optional" attributes with the default values. This could provide an opportunity to regroup the structure somewhat (eg one channel comprises ine "tx" object and two "rx" objects)
- This is changed in the development version
- Not trivial to do this, but we could use the ABCD chip serial numbers as the chip identifier in place of "serialnumber:chipnumber" as used at present.
- Some of the defined ranges are excessive, eg Strobe delay runs from 0 to 63, shaper and bias DACs are 5 bit.
Extra power supply crate parameters:
For the DCS canbus configuration:
- HOST (string, name of DCS Local Control Station)
- BUS (number, canbus interface, typically between 1 and 4)
- NODE (number, CC identifier on the canbus, typically = crate +1)
- DRIVER (string, typically "KVcanserver+")
- PORT (number, not sure of meaning)
- BaudRate? (number, typically 125000)
For the physical rack mapping
- RACK (string, eg Y.23-15.S2 for US15 or Y.28-11.A2 for USA15)
- CRATEwithinRACK? (number 0 to 3)