1. Database High-Level Overview
David Forrest
University of Glasgow

2. Scope
Asked to provide a high level overview of the configuration database
No technical detail is presented here – please see preceding presentation at CM24, or CM25 in March

3. Analysis Analysing real data requires knowledge of configuration
Beamline
Settings?
Calibrations?
Cablings?
Also included:
Alarm handler settings
Geometry?
The aim is that much of this will be automated, and that even though MICE will become more complicated (eg more detectors with calibrations), retrieving config parameters won’t need to be

4. Control Room
We currently enter a lot of information by hand (spreadsheet, EPICs magnet control etc)
Can I just load beamline parameters with one click?
I want to tag these settings for future use.
What were my magnet settings yesterday?
I do not see the database replacing the e-Log, but it will replace the run settings spreadsheet and it will allow us to automatically set the magnet currents rather than setting them by hand in 25/50 A steps

5. Other Remote Users
Web interface will be provided for users who want to view configuration data without having to use G4MICE, EPICs etc
Run conditions?
Find me all the runs with these constraints….
Show me the config for run 01436
Easy and quick to develop for specific use cases not listed here

6. Overhead
There is no need for anyone in the collaboration to know anything about databases, SQL, etc (except me)
Much of this functionality will be built into the applications we already use – the user may not even be aware they are using the database, when they ask for the default calibration for run 01333
The goal is to make things easier

7. Clients
The database can provide functionality which client code must call upon
No need to know anything about databases – the database sends and receives xml which is easy to understand.
I can help those wishing to develop code to understand how to easily parse the xml that comes from the db, and can provide them with the xml structure to send back
(not difficult)

8. What’s to do? (non technical)
Requested
Implemented server side
Got client resources for
Web interface
Beamline settings
Alarm Handler Limits
Tagged beamline settings
Geometry
Calibration
Cabling Ö
Partially ?
Notes:
Question marks indicate reliance on a php webserver (Yagmur to advise) – if we can use the mice webserver then these are straightforward. The main thing is G4MICE implementations of geometry, cabling and calibration readers and/or writers. I need to investigate appropriateness of a secure web solution for writing calibrations

9. Delivery
The Database serverside code is at an advanced stage with much of the server functionality complete (eg geometry, beamline settings, calibrations)
Alarm Handler functionality is easy to include
Intention to present a finished system by CM25. This has been scuppered by hardware failures on-site at RAL.
BUT: We are expecting new hardware for the DB end of February. Haven’t yet been advised when that is going to be ready for me (understandable if there is a delay), but when it is ready progress can continue

10. Client Code to be Developed
The main need is for code in G4MICE to interface the db response with the data structures therein
I am available to help people wanting/allocated to do this.
I have to write up, so will become unavailable
The next collaboration meeting should be seen as a last opportunity for face to face discussion
The task is straightforward whilst this help is available