From SystemTests, run AnalysisTests?/NOTests/VariableTriggersTest?/
-> put things into CDI... (Lisbon DB)...for now!
To set up CDI:
| Starting the CDI outside the setup_daq application: |
Most people start the setup_daq with "-i cdi" . This is actually the best way to personalise the technology and location of data to be stored. Start your applications as usual.
In the cdi package tree edit the setup_vars.sh script under the scripts folder. In particular edit the TDAQ_COND_DB_PROFILE variable to the location you want the data in the form <database_server>:<database>:<user>:<password>[:<port>] (eg. atlobk02.cern.ch:test_sct:conditions:conditions:3306"). Source the script.
Start the cdi_daq application. It requires two mandatory parameters: the partition (-p) and the backend (-B). To use the Lisbon API use -B 0. For more information execute cdi_daq --help.
By starting the cdi_daq application two objects will be subscribed and stored from the ISServer: RunParams?.RunParams? and RunParams?.Conditions. While the first may not exist and hence will not be stored, the second is specific for the use of CDI. This object must exist in the partition. It lists the objects subscribed to the CDI.
If you want to store aditional objects (eg. all objects matching the pattern "ControlData.TestData*"):
Execute cdi_set_conditions -p SCT -n "ControlData.TestData*"
NB:The order of the execution of these application is not critical.
To look at the data stored:
On http://atlobk02.cern.ch Change the connection definitions to the location where you stored your data.
To look at the example storage of ControlData.TestData do:
- Host: atlobk02.cern.ch
- DB: test_sct_v2
- User: conditions
- Pass: conditions
Open the folder structure.
Information on ISattributes