Shift Instructions for Cosmic Runs

General Information For Cosmic Runs

Requirements For Cosmic Runs

Regularity: 2-3 runs per week

Trigger rate + runtime: 20Hz for 2h

Components To Include

  1. Check in Detector Power Control (in the detector slow control) that all components are ON (CE, SSP, Wire Bias, Field Cage Terminations).
  2. Check in the SSP info Panel that the SSP bias is ON.

Note, the Wire Bias of APA 3 (US-BR) G-Plane is always OFF, disconnected G-Plane. The Field Cage Termination on the US-BR side is OFF for the Endwall because of a broken connection.

Include ALL cold electronics and SSPs Do NOT include the felix hitfinder nodes and trigger nodes.

Current cosmic ray detector configuration

Cosmic Runs Spreadsheet

After each run please fill in the details into this spread sheet FROM TOP (by adding a new column) https://docs.google.com/spreadsheets/d/1gPqQbPFoOZjDLPfPVHBfCrZz9g0IQoqWUUhFnKVx6aQ/edit?usp=sharing

Be careful not to delete any content of this file and keep the formatting that is defined there. This sheet is being used by offline people for reconstruction. Changes in formats can lead to problems in the reconstruction.

Slack channels

Coordinate with others on the np04-shifterassistance channel

np04 Logbook

Use this to log your run, detector issues and puity monitor readings.

https://pdspelog.web.cern.ch/elisa/display

Log the runs in the spread sheet (noting the purity from the PrM in the title) https://docs.google.com/spreadsheets/d/1gPqQbPFoOZjDLPfPVHBfCrZz9g0IQoqWUUhFnKVx6aQ/edit?usp=sharing

How To Take A Cosmics Run

Before taking a cosmics run you want to take a purity monitor reading if one has not been taken for ~1day. Add the results to the logbook. You can check on the latest purity measurement in two ways:

On the online Slow Control https://np04-slow-control.web.cern.ch/np04-slow-control/app/#!/purity

On the DCS (detector slow control) Panel on the computer next to the Run Control, go to the purity monitor panel through the navigation panel by clicking on the parrot/sail.

Running The Purity Monitor

Open the DCS navigation Panel

  1. Unbias the SSP's through the SSP info Panel (there is an interlock that does not allow to run the purity monitors if SSPs are biased)
  2. From Navigation Panel open the node Purity Monitor Panel.
  3. On the top in the DCS box you will see a green box with "STATUS OK"
  4. For "Choose a HV config" pick -50V/250V from the drop down menu
  5. For "Choose a Digitizer config" pick 40mV amplitude range
  6. Click "Run Purity Monitor"

This will take about 3min, the purity monitors are run twice in this time. You can read the in the PRM DAQ box (next to the DCS box) the DAQ status. The latest measurement will be displayed in the first line under Electron Lifetime.

Bias again the SSPs from the SSP info Panel and start the cosmic run.

Run Control

If you are remote: 1. log into np04-srv-024 as np04daq (ssh -XC np04daq@np04-srv-024 from LXPLUS). 1. Start run control by executing the alias RC 1. Enter you CERN credentials when prompted

You now have the NP04 Run Control GUI available for operation.

In order to start a run follow this steps (clicking on the ProcessManager button you will open the DAQInterface real-time log):

  1. Identify an available Partition (preferably Partition 0) (all nodes are grayed out) browsing the tab menu.
  2. Click on the (open) lock icon next to the Partition top node and select "Take" to get the exclusive command of the Partition.
  3. Before booting the system, click on the BoardReaders node in the left tree viewer. This will open the BoardReaders page, allowing you to include or exclude APAs and components.
  4. Repeat the previous point with the EventBuilders node in order to define your data acquisition system.
  5. From the top Partition node, select the artdaq folder from which to execute the acquisition system.
  6. After defining the desired system, click on the Partition state button (now displaying UNKNOWN state). You can now click on BOOT
  7. When the included processes are BOOTED, you can now CONFIGURE the processes. The CONFIGURE command requires the user to select the desired configuration and Run type from the activated drop-down menu. After the selection, the configuration files are applied to the processes.
  8. Select START from the top node to start a new run. Run number will be automatically fetched.
  9. The system is now RUNNING
  10. The previous step enables the optional "Trigger options" panel. Select a trigger rate and Enable the triggers.
  11. The system transitions to RUNNING with the InhibitMaster inhibiting all trigger. You need to click on the "Allow trigger" button in order to get triggers flowing.
  12. In order to stop a run, select STOP from the top node.
  13. After stopping the run, use SHUTDOWN to terminate and kill the processes. The system will then transition to UNKNOWN state.

Runs can be stopped after ~2 hours at 20Hz trigger rate.

After it has stopped, add the run details to the spreadsheet. Please be careful to add at the ?top? of the spreadsheet.

-- DavidGeoffreySavage - 2019-06-19

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2019-06-20 - FrancescaStocker
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CENF All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback