DQM & AMOREstatus and latest improvements

08/03/2012Barthélémy von Haller

2

Overview

AMORE

AliQAThresholds : status and instructions

Reminder about config files

Reminder about QA species

P2

Clean up (configuration files, agents and logs; home)

Software status

08/03/2012Barthélémy von Haller

3

AliQAthresholds (1)

Rationales

Make sure we split code (AliQAchecker) and parameters (AliQAThresholds, set in a config file)

Keep the parameters, the thresholds, in the OCDB for future reuse offline

08/03/2012Barthélémy von Haller

4

AliQAthresholds (2)

08/03/2012Barthélémy von Haller

5

AliQAthresholds (3)

How will you use thresholds ?

1. Create a configuration file «QAThresholds.configfile», save it in the config file database (amoreConfigFileBrowser d XXX)

2. Add elements for each threshold(s) in your config file : threshold1 L 10 ...

3. Run the amore agent (see doc). It will generate the object as it will be in the OCDB.

4. Modify your AliQAChecker (or other classes) to retrieve the AliQAThreshold object from the OCDB (GRP/Calib/QAThresholds). Get your values out of it and use them. Handle the case when there is no threshold.

08/03/2012Barthélémy von Haller

6

AliQAthresholds (4)

5. You can run either in offline mode (copy the object in your OCDB) or online with AMORE (no need to copy the object, it is passed to the QA automatically)

6. When you are happy with your code, commit in AliRoot and ask to port

7. You can already add the config file at P2

8. Once your code is at P2, you should see it working with the thresholds set in the config file

08/03/2012Barthélémy von Haller

7

AliQAthresholds (5)

THIS IS NOT IN PRODUCTION YET !

System will be enabled at P2 this week, but a guinea pig will first try to use it. This could take some time.

For the start of the collisions, carry on as usual with your macros, don’t think about the thresholds.

The documentation will be ready by the time we give you a green light.

08/03/2012Barthélémy von Haller

8

Configuration files (1)

New situation (for QA agents) :

Start amoreConfigFileBrowser with «det» only !

File Content Owner

Config file (optional)Macro file, libraries,

species, reset, trigger cloning histograms

DET (0..1 per agent)

QAdescriptions_DET.configfile

Objects descriptions DET (1 per det)

Macro file(s) Macro(s) DET (0..* per agent)

triggerClassesAliases.configfile

Trigger aliases definition QA (1 global)

defaultEventSpecie.configfile

Default specie for technical runs

QA (1 global)

08/03/2012Barthélémy von Haller

9

configuration files (2)

Consequences

A clearer and more coherent situation

Issue the same command whatever file you want to edit (amoreConfigFileBrowser d <det code or name>)

Trigger cloning definition is under your responsibility

Format : TrigClone1 H1D_Trigger_Type CVHN CVLN CCENT *

The new scheme is already in place at P2

08/03/2012Barthélémy von Haller

10

QA species (1)

FORMER SITUATION

08/03/2012Barthélémy von Haller

11

QA species (2)

IMPROVED SITUATION

08/03/2012Barthélémy von Haller

12

QA species (3)

Consequences

Layout references the «default» plots and thus doesn’t change

By default, only one species published (aka «default»)

Computation of default species might need some refinement

Simple configuration, in case of special needs

The new scheme is already in place at P2 and the layouts have been updated

08/03/2012Barthélémy von Haller

13

Discussion

Many changes => many ways of making bugs

Test early, report early !

Questions