Difference between revisions of "Checklist maintenance (HCO) Expert"

From Hall D Ops Wiki
Jump to: navigation, search
(Expert personnel)
 
(24 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Checklist maintenance  ==
+
== Checklist (HCO) maintenance  ==
The barrel calorimeter (BCAL) is a lead-scintillating fiber matrix readout with 3840 S12045 Hamamatsu multi-pixel photon counters (MPPCs).
+
Hall D is using the accelerator-developed system of checklists, commonly referred to as the hot checkout (HCO). The system is driven by a [https://accweb.acc.jlab.org/hco web-based interface] with many features that can be discovered interactively. However, there are a few infrequent actions that require specific instructions. Note that some of these require special permissions, not generally granted.
The MPPC light sensors operate a bias voltage less than 76 V. Liquid coolant is circulated through the readout assemblies to set and
+
maintain the temperature of the sensors at their operating temperature between 5 and 25 degrees C.
+
  
== Routine operation==
+
===Subsystem participation===
 +
After adding a subsystem, it must be enabled. To enable the "participation" of a particular component in the checklist, use the [https://accweb.acc.jlab.org/hco/setup/component-participation setup component participation] page. Use the filter to select the particular component of interest and then 'click' on the column that requires that component. At least one box must be checked for the component to be listed in the readiness or signoff pages.
  
Instructions for shift personnel are available in the [[Barrel Calorimeter Shift | Barrel Calorimeter instructions for shift personnel]].
+
===Modification of groups===
 +
Changes to checklist groups and the addition/removal of members to a particular group can be done only by accelerator software experts. Send the request with the name of the group to be modified, the name of the person to be added/removed and his/her computer username to Theo Larrieu or Ryan Slominski.
  
===Saving and Comparing Save/Restore Files===
+
===Sign-off authority===
Specific voltage settings can be saved (from electronics to file) or restored (from file to electronics). This is done via the "Save/Restore" button on the top right of the GUI. The files are automatically saved with the date/time to /gluex/data/burt/voltages/BCAL_BIAS/. We have renamed the files incorporating the date/time temperature and 10 times the overvoltage (to avoid an additional "." in the name). A soft link is created in that directory to point to the nominal file for the current run. The voltages from different files can be compared using the script compare_snap_voltages.C which is located in /gluex/Subsystems/BCAL/scripts.
+
Changing the sign-off authority is enabled/disabled by the accelerator software group. The lists of authorized personnel can be found under Reports/Group Leader.
  
===Chiller Operation===
+
===View checklist comments===
 +
To view the comments entered when checklists were completed, use the [https://accweb.acc.jlab.org/hco/reports/activity-detail 'reports / activity detail'] page. Select your subsystem, select the beam destination, and make sure the period range covers the time of interest. A specific group can also be selected. The generated list contains changes to the status of that particular system/component and the comments entered at the change.
  
The chiller temperature should be set to 2 degC less than the desired SiPM temperature. The chillers are normally in 'remote' mode. (You can still change the temperature manually). To change the 'set' temperature, use the up/down arrows on the front key pad to the desired temperature. The values are in deg F. Wait for the 'readback' temperature
+
Alternatively, from the Readiness page, click on the subsystem of interest (not a specific group). This will bring up a table with 'Group Signoff', where one may sign off or view the history for each group. A second table below has a listing of each group with links to their checklist.
to settle to the 'set' value, as it may overshoot at first. At startup it may be
+
necessary to pull the reset (green) switch forward that is accessed through the hole on the side of the chiller closest to the front.
+
  
==LED Runs for BCAL Checklist==
+
===Downgrading status===
  
===LED Data Runs===
+
09/11/18:  Automatic downgrades: Use the "Bulk Signoff" page under the [https://accweb.acc.jlab.org/hco/setup/bulk-signoff Setup Tab].  You can use this page to set the status of all signoffs for one or more subsystems at once. Set category to 'Hall D', then usually exclude 'Hall D Shutdown' and downgrade all to 'Not Ready'. This procedure supersedes instructions below.
  
Up to now, the DAQ runs are taken independently using the local master trigger interface (TI) for north and south, but should be consolidated by feeding the LED triggers to the trigger supervisor (TS).
+
Downgrading by Hand: Downgrading the status can be done on the signoff page.  For any given system there can be multiple responsible groups so you'll need to decide if all groups will have their signoff downgraded or just a subset.  The group signoffs in a particular subsystem are ordered left to right so choose the group at which downgrades should begin and all groups to their right will be cascaded down. For Hall D, select the "mechanical group," which is usually the first one (left-most) and all other groups will be downgraded also. After selecting the group/subsystem combination, use the 'Downgrade options' on the bottom right to select the downgrade action requested for a given status. Then use the 'Edit Signoff' button at the top left to complete the downgrade.
* The checklist entries for the 2015 spring commissioning run are recorded in Log Entries [https://logbooks.jlab.org/entry/3322823 3322823] and [https://logbooks.jlab.org/entry/3322905 3322905].
+
* The checklist entry for the fall 2014 commissioning run is recorded in Log Entry [https://logbooks.jlab.org/entry/3297440 3297440].  
+
  
Data were first taken with all LEDs on so that the timing could be checked. Once offsets were adjusted, data were taken using Orlando's script (BCAL_test.py) to pulse the LED.  (More information can be found at [https://halldweb.jlab.org/wiki/index.php/Barrel_Calorimeter BCAL DAQ Instructions]). The following procedure was followed.
+
Tips:  Use the blue arrow button on the top of the signoff table to select an entire column of signoffs. You may find using the "Start with Category" checkbox found in the top right corner of the signoff screen makes navigating the component tree easier for the downgrading task, especially if you decide "Checked" is not downgraded far enough and you need to change your group selection without losing your subsystem selection. Also an error message with a race condition occurs if both boxes (Downgrade Options) are not both set to "Not Ready."
# Make sure that SiPM and LED voltages are off
+
#* Turn off SiPM bias voltage
+
#* Turn off LED bias voltage
+
#* Make sure no triggers are enabled or running.
+
# Start [[Data Acquisition Shift | DAQ system]].
+
#* Complete prestart/start sequence, leaving system ready and waiting for triggers
+
# Open a terminal and login to hdops@gluon02-05
+
#* cd $DAQ_HOME/tools/bcal_pulse_sequence
+
#* BCAL_test.py -s U -q 2,3 -n 10 -b 7    // Run the south side, upstream LED pulser, quadrants 2 and 3, 10 pulses per setting and (large) bias of 7 V.
+
#* BCAL_test.py -s D -q 1,4 -n 10 -b 7      // Same for north side, downstream LED pulser, quadrants 1 and 4, 10 pulses per setting and (large) bias of 7 V.
+
#* BCAL_test.py –h                                    // Help option
+
# The script with the above arguments should loop through a total of 320 triggers (10 pulses x 4 voltages x 4 columns x 2 quadrants).
+
#* End run
+
  
===Status Occupancy Plots===
+
===Masking===
  
After the raw data were taken, the following procedure was used to generate root files starting from the /gluex/Subsystems/BCAL/data/ directory:
+
Masking a component can be done on the [https://accweb.acc.jlab.org/hco/setup/component-list component list setup page].  Use the filter form to find the component in question then click on the table row containing the component to select the component and click the "Mask/Unmask Selected" button. This action requires special permissions.
  
# generate root file to dump wave forms
+
== Expert personnel ==
#* hd_root -PPLUGINS=DAQTree /gluonraid2/rawdata/active/RunPeriod-2015-01/rawdata/Run002514/hd_rawdata_002514_000.evio -o /gluex/Subsystems/BCAL/rootfiles/hd_rawdata_002514_000.root
+
The individuals responsible from Hall D for checking that the checklists are prepared to be filled for a given run period are shown in following table.
#* display waveforms
+
Additional experts on the software itself from accelerator are listed in case issues come up with their implementation.
#* root [0] .L /gluex/Subsystems/BCAL/scripts/dump_tree_waveform_dalton.C+
+
#* root [0] dump_tree_waveform_dalton("/gluex/Subsystems/BCAL/rootfiles/hd_rawdata_002514_000.root");
+
# generate root file to create occupancy plots
+
#* hd_root -PPLUGINS=DAQTreeBCAL /gluonraid2/rawdata/active/RunPeriod-2015-01/rawdata/Run002514/hd_rawdata_002514_000.evio -o /gluex/Subsystems/BCAL/rootfiles/hd_rawdata_002514_000_status.root
+
#* create occupancy plot for FADCs
+
#* root [0] .L /gluex/Subsystems/BCAL/scripts/SiPM_Test_fADC.C+
+
#* root [0] SiPM_Test_fADC("/gluex/Subsystems/BCAL/rootfiles/hd_rawdata_002514_000_status.root");
+
#* root [0] c1->SaveAs("/gluex/Subsystems/BCAL/plots/LED_status/hd_bcal_n-led_up_mode8-ADC_R2514.pdf");
+
# create occupancy plot for TDCs
+
#* root [0] .L /gluex/Subsystems/BCAL/scripts/SiPM_Test_TDC.C+
+
#* root [0] SiPM_Test_TDC("/gluex/Subsystems/BCAL/rootfiles/hd_rawdata_002514_000_status.root");
+
#* root [0] c1->SaveAs("/gluex/Subsystems/BCAL/plots/LED_status/hd_bcal_n-led_up_mode8-TDC_R2514.pdf");
+
  
== Remote Control PDU ==
 
 
[[Image:PDU_web_interface.png | thumb | 400px | Fig. 2.  Screen shot of the PDU web interface.]]
 
 
 
The bias (ISEG) and low voltage (MPOD) supplies providing power to the SiPMs are plugged into remotely controllable power distribution units (PDUs). This allows us to recycle the power to the crates via a web interface. Each of the four ISEG/MPOD crates is plugged into its own PDU. At the present time, only the first output of the distribution strip is used. The following PDUs are being used, given by the name of the rack followed by -pdu.
 
* n1-1-pdu
 
* n1-6-pdu
 
* s1-1-pdu
 
* s1-6-pdu
 
The remote access to the crate is via a web browser in the Counting House pointing to the name of the PDU (e.g. type s1-1-pdu into browser and confirm with user/pass=admin/admin). See the screen shot of the web interface. To cycle the power
 
* Click on the Actions, then Loads button.
 
* Highlight the first line (Load 1). The On/Off/Cycle buttons should become enabled
 
* Click on the Off and confirm preference. It will take about half a minute to complete the command (patience!). After "Output Current Changed" message appears under Alarm Status, the status should turn from 'On' to 'Off', then message disappears.
 
* Repeat reverse action to turn PDU input back on.
 
 
== External Cosmic-Ray Trigger ==
 
The external cosmic-ray trigger was setup using some scintillation counters located above and below the magnet yoke to signal the passing of cosmic rays through the central detectors.
 
[https://logbooks.jlab.org/entry/3275972 Log Entry 3275972] and [https://logbooks.jlab.org/entry/3285969 Log Entry 3285969] contain detailed information about the setup.
 
To control the high voltage using the CAEN power supply use the following procedure starting from a terminal on the local network:
 
* telnet u1-9-top 1527
 
* login: user/user
 
* Use 'tab' to move from one column menu heading to another.
 
* Use keypad 'up' and 'down' arrows to select submenus under the header. Select Main/Channels to view voltages.
 
* Use 'tab' to move back to Main menu, 'down' key to 'Log Out' and exit
 
 
== Expert personnel ==
 
The individuals responsible for checking that the BCAL is ready to take data  and setting its operating parameters  are shown in following table.
 
Problems with normal operation of the BCAL should be referred to those individuals and any changes to their settings must be
 
approved by them. Additional experts may be trained by the system owner and their name and date added to this table.
 
  
 
  {| border=1  
 
  {| border=1  
|+ Table:  Expert personnel for the BCAL system
+
|+ Table:  Expert personnel for the HCO system
 
|- bgcolor=#DFDFDF   
 
|- bgcolor=#DFDFDF   
 
! width=200px | Name    !!  width=100px | Extension !! Date of qualification  
 
! width=200px | Name    !!  width=100px | Extension !! Date of qualification  
 
|-
 
|-
| Elton Smith     ||  align=center | 269-7625   ||  align=center | May 20, 2014
+
| Hovanes Egiyan     ||  align=center | 269-5356   ||  align=center | January, 2015
 +
|-
 +
| Ryan Slominski    ||  align=center | 269-6495  ||  align=center |
 +
|-
 +
| Theo Larrieu      ||  align=center | 269-7708  ||  align=center |
 
  |}
 
  |}

Latest revision as of 23:41, 5 February 2023

Checklist (HCO) maintenance

Hall D is using the accelerator-developed system of checklists, commonly referred to as the hot checkout (HCO). The system is driven by a web-based interface with many features that can be discovered interactively. However, there are a few infrequent actions that require specific instructions. Note that some of these require special permissions, not generally granted.

Subsystem participation

After adding a subsystem, it must be enabled. To enable the "participation" of a particular component in the checklist, use the setup component participation page. Use the filter to select the particular component of interest and then 'click' on the column that requires that component. At least one box must be checked for the component to be listed in the readiness or signoff pages.

Modification of groups

Changes to checklist groups and the addition/removal of members to a particular group can be done only by accelerator software experts. Send the request with the name of the group to be modified, the name of the person to be added/removed and his/her computer username to Theo Larrieu or Ryan Slominski.

Sign-off authority

Changing the sign-off authority is enabled/disabled by the accelerator software group. The lists of authorized personnel can be found under Reports/Group Leader.

View checklist comments

To view the comments entered when checklists were completed, use the 'reports / activity detail' page. Select your subsystem, select the beam destination, and make sure the period range covers the time of interest. A specific group can also be selected. The generated list contains changes to the status of that particular system/component and the comments entered at the change.

Alternatively, from the Readiness page, click on the subsystem of interest (not a specific group). This will bring up a table with 'Group Signoff', where one may sign off or view the history for each group. A second table below has a listing of each group with links to their checklist.

Downgrading status

09/11/18: Automatic downgrades: Use the "Bulk Signoff" page under the Setup Tab. You can use this page to set the status of all signoffs for one or more subsystems at once. Set category to 'Hall D', then usually exclude 'Hall D Shutdown' and downgrade all to 'Not Ready'. This procedure supersedes instructions below.

Downgrading by Hand: Downgrading the status can be done on the signoff page. For any given system there can be multiple responsible groups so you'll need to decide if all groups will have their signoff downgraded or just a subset. The group signoffs in a particular subsystem are ordered left to right so choose the group at which downgrades should begin and all groups to their right will be cascaded down. For Hall D, select the "mechanical group," which is usually the first one (left-most) and all other groups will be downgraded also. After selecting the group/subsystem combination, use the 'Downgrade options' on the bottom right to select the downgrade action requested for a given status. Then use the 'Edit Signoff' button at the top left to complete the downgrade.

Tips: Use the blue arrow button on the top of the signoff table to select an entire column of signoffs. You may find using the "Start with Category" checkbox found in the top right corner of the signoff screen makes navigating the component tree easier for the downgrading task, especially if you decide "Checked" is not downgraded far enough and you need to change your group selection without losing your subsystem selection. Also an error message with a race condition occurs if both boxes (Downgrade Options) are not both set to "Not Ready."

Masking

Masking a component can be done on the component list setup page. Use the filter form to find the component in question then click on the table row containing the component to select the component and click the "Mask/Unmask Selected" button. This action requires special permissions.

Expert personnel

The individuals responsible from Hall D for checking that the checklists are prepared to be filled for a given run period are shown in following table. Additional experts on the software itself from accelerator are listed in case issues come up with their implementation.


Table: Expert personnel for the HCO system
Name Extension Date of qualification
Hovanes Egiyan 269-5356 January, 2015
Ryan Slominski 269-6495
Theo Larrieu 269-7708