Up: l1joint_0330_confdb
Previous: Configuration Database (2)
Other Stuff
- Nothing yet for run parameter type settings.
- Also, little thought on software configuration (but DAQ -1
schema already has a lot of what we need)
- For test activities, we may want hardware configuration
to be more dynamic (like run parameters) than final database objects?
- Leave physics trigger settings (thresholds, etc) to the CTP for
now?
- Connections between modules, mappings to towers, cells etc.
Really not sure how to do this.
- Some vague ideas on organisation of calibration data...
- Eric suggested a module inventory, service history database.
Should be implemented soonish or probably never...
Next Steps
- Turn Erics list into a proper document?
- More thought - eg small brainstorming session?
- Outline requirements for data access library
- Discuss with DAQ -1 people
- Small scale test: replace some configuration/run parameters
in the DAQ
- Choice of GUI for run parameter editing: Java, ROOT, Qt, ...
Up: l1joint_0330_confdb
Previous: Configuration Database (2)
Murrough Landon (m.p.j.landon@qmw.ac.uk)