1 / 5

AMORE, QA & DQM

AMORE, QA & DQM. Generalities, FEEDBACK from DQM meeting and REquests. Generalities. Data Pool. Monitor Objects. Agent. Data samples. Client. GDC LDC File. Monitor Objects. Histograms & Images. Event. AliRoot QA. QA can run online, steered by AMORE

mircea
Download Presentation

AMORE, QA & DQM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AMORE, QA & DQM Generalities, FEEDBACK from DQM meeting and REquests

  2. Generalities Data Pool Monitor Objects Agent Data samples Client GDC LDC File Monitor Objects Histograms & Images Event AliRoot QA QA can run online, steered by AMORE QA is used as a black box from AMORE’s point of view

  3. New feature: Macros • Motivation: development cycle for a simple change in the QA of a detector is long (about 2 weeks) • Solution: execute macros in the generic QA agent • Macros are stored in the database at P2 and can be quickly and easily modified and tested. Immediate feedback. • Now, objects’ quality can be changed as well  possible discrepancies between online and offline •  Integrate macro development in the offline QA • Documentation + examples on the AMORE website

  4. DQM meeting feedback DQM meeting on Friday every ALICE mini-week All people involved should work hand in hand: AMORE, QA, detectors, DQM shifter and leader QA is used online by all detectors apart TRD Custom modules are also used whenever available See in indico for the full minutes

  5. Requests for the QA framework • Add a few per-object properties in the QA • Default draw option (eg. colz) • Display hint (eg. logz) • Description • Owner of the object (eg. QA framework or AMORE) • Savannah 67596, assigned to Yves • Add some general reconstruction QA for the DQM shifter (eg. main vertex, reconstruction) • Various trigger classes: how to manage this ? Event species ?

More Related