1 / 5

Streamlining rcReport and Run Database Management in Experimental Physics

This document outlines the proposed philosophy for enhancing information management in experimental physics, focusing on the use and customization of available tools like e-logbook and web queries. Emphasizing simplicity, it details the necessary steps to control the pipeline using Warren scripts and populate the run database effectively. Key areas addressed include required fields for rcReport, minimizing duplicate information, and extracting data from various sources. The document advocates for both automatic and manual data input, while ensuring all configurations are up-to-date and easily accessible.

avram-french
Télécharger la présentation

Streamlining rcReport and Run Database Management in Experimental Physics

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. Remarks • Agree with proposed philosophy • Use and customize available tools (e-logbook, runs database, web-queries, pipeline scripts) • Simple and enough • Fill rcReport.out to • control pipeline (Warren scripts) • Populate run database • Why duplicate info also at the ancillary header? Security? • Required fields for rcReport • Same list of fields we want to query on from the web • Minimal to avoid over-crowded info • information extracted from different sources • CU • XY table • Beam • Trigger • Ancillary geometry • Both automatic (A) and manual (M) filling • Use GUIs to gather info, check it and pass it to rcReport • Minimize typing • Complete information passed through files into run directory (LATTE style)

  2. Proposed list and schema ? Ancillary header • Beam momentum (M) • MNP17 magnet current (M) • XY table position and angle (A) Johan GUI ? rcReport Ric • CU configuration (trigger, thresholds, gain) (M) • modify end2end configs drop-down menu, call them BTn • Particle type (M) • e-, tagged-g, full-brems-g, p,e+,m • use available drop-down menu in RunControl Warren Charlotte pipeline Web queries to run database Note Ancillary geometry should not go in rcReport and will not be queried No changes to e-logbook required M = manual input by operator A = automatic extraction from file

  3. Particle type declared in RunControl Will have to warn people that this does not change beam settings and trigger accordingly

  4. Extra information from Johan GUI • Some things must be removed from Johan GUI, he was too fast implementing • Must implement readout of XY table file and tagger alignment file • Must agree on how to pass info to rcReport

  5. Additional info in DataExport dir • Following set of files must be maintained and updated at any change in configuration – will be copied for every run in dataexport dir for reference • XY table snapshot file (from Philippe) • Stepper motor readings • Beam settings • Currents and collimators settings along the line, reported by hand and after setup phase into a file • CERN does not provide files • Trigger configuration • Could also implement a trigger logic readout in the DAQ (if we have time) • Ancillary geometry • Must be updated after tagger alignment • Tagger recon will either use this file (so no need to warn pipeline when geometry is tuned) or we also implement tagger alignment into calibrations database (Joanne?) • Tagger silicon pedestal file (just like for CAL)

More Related