Revision as of 21:37, 6 October 2021

Overview

This page gives instructions for various aspects of the experiment relating to each of the major subsystems and shift tasks.

Shift Roles

Shift Leader: Executes the Run Plan according to the Run Coordinator's instructions
Target Operator: Monitors the target system
Data Quality Monitor: Starts and stops CODA DAQ runs and monitors the quality of the data that is being recorded

Reporting and Logging

All shift takers should regularly log shift details in HALOG - the Hall A electronic logbook.

Shift leaders should fill out Beam Time Accounting (BTA) information during the shift.

BTA steps

Taking Data

Using the CODA DAQ
- GUI Description
- Starting a Run
- Stopping a Run

Monitoring the data
Online analysis
Shift checklist

online analysis

This section contains instructions for running the replay script with all detectors on a-onl@aonlX.

Instruction for shift crew

Login to a-onl@aonlX (X=1, 2, 3, 4)
once logged in, type gosbs => this takes you to the directory where the analysis should be done, and sets up the correct environment variables.
type ./run_gmn.sh runnum nevents with
- runnum (integer) the run number you want to analyze;
- nevents (long integer) the number of events you want to analyze.

Specific instructions for experts

Login to a-onl@aonlX (X=1, 2, 3, 4)
once logged in, type gosbs => this takes you to the directory where the analysis should be done, and sets up the correct environment variables.
open the analyzer by typing analyzer
once in the analyzer type .L replay_gmn.C+
type replay_gmn(runnum, nevents, firstevent, file_prefix, firstsplit, nsplits, pedestalmode) with:
- runnum (integer) the run number you want to analyze;
- nevents (long integer) the number of events you want to analyze.
- firstevent (long integer) the event number from which you want to start the analysis;
- file_prefix (char*)the prefix of the file you want to analyze;
- firstsplit (integer) the split/segment number at which you want to start the analysis;
- nsplits (integer) the number of splits/segments you want to analyze
- pedestalmode (integer) turn pedestal mode on or off for the GEMs

Recovery Procedures

Systems

High Voltage

SBS EPICS

Alarms

Beam Line

Monitoring the Beam Line
Hall A beam line drawing (to be updated)
SBS checkout procedure
SBS spot++ (beam size verification)
SBS BPM calibration
SBS HARP scan
SBS Polarization Measurements
- Compton: Not Used
- SBS Moller

Target

Magnets

Detectors

BigBite

GEMs
GRINCH
Timing Hodoscope
Preshower and Shower
- How to adjust discriminator threshold on HCAL DAC
- How to run the scalers script to monitor trigger sum scalers

Super BigBite

GEMs
HCAL

@@ Line 29: / Line 29: @@
 == online analysis==
 This section contains instructions for running the replay script with all detectors on a-onl@aonlX.
+=== Instruction for shift crew ===
+* Login to a-onl@aonlX (X=1, 2, 3, 4)
+* once logged in, type ''gosbs'' => this takes you to the directory where the analysis should be done, and sets up the correct environment variables.
+* type          ''./run_gmn.sh runnum nevents''              with
+** ''runnum'' (integer) the run number you want to analyze;
+** ''nevents'' (long integer) the number of events you want to analyze.
+=== Specific instructions for experts ===
 * Login to a-onl@aonlX (X=1, 2, 3, 4)
 * once logged in, type ''gosbs'' => this takes you to the directory where the analysis should be done, and sets up the correct environment variables.
 * open the analyzer by typing ''analyzer''
-* once in the analyzer type ''.L replay_gmn.C''
+* once in the analyzer type ''.L replay_gmn.C+''
-* '''for routine analysis''' type ''replay_gmn(runnum, nevents)'', with:
+* type ''replay_gmn(runnum, nevents, firstevent, file_prefix, firstsplit, nsplits, pedestalmode)'' with:
 ** ''runnum'' (integer) the run number you want to analyze;
 ** ''nevents'' (long integer) the number of events you want to analyze.
-* '''for expert analysis only''' type ''replay_gmn(runnum, nevents, firstevent, file_prefix, firstsplit, nsplits, pedestalmode)'' with:
 ** ''firstevent'' (long integer) the event number from which you want to start the analysis;
 ** ''file_prefix'' (char*)the prefix of the file you want to analyze;

Difference between revisions of "Shift How-To"