Run Plan for May 13 - June 20, 2016:
Units are PAC days
- Photon Beam Tuning (~1 day)
- HyCal with GEM on Transporter and off the beam line;
- Target cell off the beam line;
- Tagger radiator off, collimator off;
- Tagger magnet on (for Ee = 2.2 GeV).
- establish a good electron beam (Ee = 2.2 GeV, Ie = 5 nA) on the tagger dump;
- take electron harp scans 2C21A and 2C24A, check the position, widths and peak to tails ratio;
- study beam halo by setting the harp wire in the tail region and ramping beam current up to 100 nA;
- lower beam current to 0.1 nA
- insert radiator 10-5 r. l.;
- check tagger counter scalars;
- setup MOR logic for calibration (gain equalizing) trigger T5 only;
- HyCal Gain Equalizing, GEM efficiency measurements (~2.5 days)
- establish HyCal temperature to T=16o and keep it stable;
- collimator in, 6.4 mm;
- target cell off the beam;
- HyCal is in “Bottom Right” position;
- 1”x1“l scintillator counters are installed in the beam line just after the Vacuum box and surveyed;
- establish good timing for the beam scintillator counters (record TDCs and ADCs for them)
- establish good timing for the HyCal readout;
- establish good timing for the GEM readout;
- adjust trigger delays, if necessary;
- set the gain value: E=2 GeV to ADC=4000 channel;
From part #2.10 “Set the gain …”
- T5 is in the MOR trigger (E(T33) = 0.5 x Ee, so, Eg(T5) = 2.2 x 0.9 = 1.10 GeV)
- Start with the closest part of the Pb-glass area. Move HyCal to the center of the Pb-glass cluster (the one which has right, left, up and down Pb-glass modules)
- Check/calibration of the HyCal Transporter coordinate axis):
- move HyCal to the “center” check left/right ADCs and total sum amplitude on the scope (writhe them down)
- move HyCal 1. cm left(right), check ADCs and total some amplitude.
- Move HyCal +1. cm do the same
- Move HyCal +1 cm, do the same
- Move HyCal +1. cm, do the same
- You suppose to be left (right) edge of the module vs. the initial center. If the right (left) module to the center does not show much “amplitude” that shows that the Transporter is possibly okay. If no, try to “feel” the center.
- The same check procedure for the Y-direction
- Setting the Gain value:
- HyCal is in the middle of that particular module (Pb-glass): increase the voltage to have average total sum value (scope) at 130 mv. Check the ADC of that module (pedestal is subtracted), it should be not more than 5000.
- REMEMBER: max HV for Pb-glass is 1850 V, for the PbWO is 1300 V.
- Move to closest PbWO cluster, position HyCal to the center of that cluster. Do the same as in the part (a).
- Check this process (a or c) for few neighboring modules. If voltage upper limits is are not “closer” then continue it as in 2.11
- Continue as in the item 2.11
- start the gain equalizing process: scan to each module’s center, show the anode and dynode ADC distributions on the computer screen, by changing the HV set anode ADC=4000 channel (with ~ 5% precision), record the dynode signal value, save the HV, ADC and anode/dynode ratio, store the data from GEM, HyCal and trigger scintillator detectors;
- repeat part (k) for all HyCal modules (~15 hours).
- HyCal Gain Calibration, GEM efficiency measurements (~3.0 days):
- run HyCal with HV unchanged for ~ 3 hours after the “Gain Equalizing” in the part #2;
- the beam and the beam line are the same as in the part #2 “Gain Equalizing”;
- tagger trigger: all T1-T19 tagger counters and several T-counters from the middle part, DAQ readout without the “sparsification” option;
- start from the “Top Left” position and with a continuous motion (~0.3 min/module) “illuminate” all modules, store the data (HyCal + GEM) with the HyCal’s X,Y positions from EPICS;
- stop the HyCal motion by the end of each row, make new DAQ run with pedestals and LMS, store the files;
- repeat item (e) for all rows of HyCal, and store the data;
- run on-line calibration programs for the gain constants, store the data.
- Setup configuration, change from calibration to run:
- HyCal is off from the Transporter to the run cart, assembling the beam line, check the vacuum levels in the beam line, engineering survey (~4 days).
- Request for the Beam Energy Change to Ee = 1.1 GeV (0.5 day, during the same time).
- Electron Beam Tuning and Target Commissioning (~4 days)
- target cell off the beam line, no gas flow in the cell and chamber;
- collimator out;
- set threshold energy for the HyCal trigger E ~ 0.5xEe ;
- request electron beam (E = 1.1 GeV, I = 1 nA);
- take harp scans 2C21A, 2C24A and 2H01, check position and widths, establish a good electron beam and fix the beam line parameters;
- record HyCal trigger rate with no cell and no gas flow, take one short DAQ run (GEM+HyCal);
- electron beam off; insert the target cell in the beam line, still empty, ask for the beam back;
- target cell is empty (no gas flow into the cell and chamber);
- record HyCal trigger rate, take one short DAQ run;
- gas flow in the cell (Pcell = 6 torr, Pcham = 5 mtorr);
- record HyCal trigger rate, take one short DAQ run;
- move the cell on X-axis by +/- 3 mm with 0.2 mm steps and record the HyCal rate;
- move the cell on Y-axis by +/-3 mm with 0.2 mm steps and record the HyCal rate;
- change the cell angles and record the HyCal rate, get optimal cell direction;
- center the cell in the beam line based on those measurements;
- no gas flow into the cell and chamber, record the HyCal rate;
- gas flow into the cell (Pcell = 6 torr, Pcham = 5 mtorr);
- record HyCal trigger rate, take one short DAQ run;
- gas flow into the chamber only (Pcell = Pcham = 5 mtorr);
- record HyCal trigger rate, take one short file with ADCs (in-beam residual gas effect);
- If there is no sizable effect between cell in/out, skip following steps.
- beam off, 12.7 mm collimator in, target cell in, ask for beam;
- no gas flow in cell, record HyCal rate;
- gas flow in the cell (Pcell = 6 torr, Pcham = 5 mtorr), record HyCal rate;
- beam off, insert 6.4 (?) mm collimator in, take beam and repeat items (w) and (x);
- make a decision about the size of the collimator.
- Data taking with Ee = 1.1 GeV (5 days)
- beam intensity: Ie = 10 nA;
- collimator in (with the diameter defined in 5 (z);
- HyCal trigger is set, DAQ is ready, all slow control readout is ready;
- target cell in with maximum density (2.x1017 H/cm3);
- take data for 2 days, record all information on disk and on tape;
- no gas in the cell, take data for 0.5 day (empty target run);
- gas in the cell, run for 2 days (same as in (e));
- no gas in the cell, take data for 0.5 day (empty target run);
- REQUEST FOR Beam Energy CHANGE to Ee = 2.2 GeV (0.5 day)
- Data taking with Ee = 2.2 GeV (6 days)
- intensity: : Ie = 10 nA;
- collimator in (with the diameter defined in 5 (z);
- HyCal trigger is set, DAQ is ready, all slow control readout is ready;
- target cell in with maximum density (2.x1017 H/cm3);
- take data for 2 days, record all information on disk and on tape;
- no gas in the cell, take data for 0.5 day (empty target run);
- gas in the cell, run for 2.0 day (same as in (e);
- no gas in the cell, take data for 0.5 day (empty target run).
|
General Instructions:
Locking up the hall (5:00 pm)
- At (4:30)pm check the status of the activities in the hall and notify RC if there are potential delays for the lockup at (5:00pm)
- Work with the hall work coordinator (Doug Tilles or his designee) to make sure hall is ready for sweep : vacuum is good, magnet power supplies are turned ON and on remote, LCW is on.
- Make sure experts, beamline, HyCal, GEM, and slow controls, checked their systems befor the lockup.
- When ready notify MCC to start seep and lockup of the hall.
- Make sure all necessary monitoring GUIs are up and running.
- Make sure beam viewer screens are up.
Acceptable Beam Conditions:
- To establish good beam conditions:
- First send beam to the tagger dump (ask MCC to turn ON the tagger magnet).
- Check that beam type is "Photon" on the BTA GUI (can be opened from "Beam" GUI).
- Check the beam position on the tagger viewer, it should be approximately in the centre of the screen
- Check profile using 2C21 and tagger harp scans, and compare the positions and widths with previous scans ([logbook link to be added]). Positions on both harps should be with +/- 1mm, widths on 2C21 should be <~0.1+/-0.05 mm, and on the tagger harp (2C24) <~0.35 +/- 0.1mm.
- Halo counters UPS-L/R and TAG-L/T/T2 should be ~few Hz/nA [logbook link to be added]
- Check HyCal HV is On
- Send beam to the Faraday cup
- Tune beam profile on (2H02A harp ? ). The required beam profile at (2H02A harp)? is: X-width <~ ?? mm, Y-width <~ ?? mm.
- Check the beam spot on chromax viewer
- Positions on BPMs must be close to what they were before [logbook link to be added]
- Insert the target without turning off the beam. ??
- Before accepting beam, make sure all the previous conditions are met. Always read previous log entries, compare settings of BPMs and correctors with previous settings.
Every Shift:
- Follow run plan as outlined by RC
- If any concern about beam stability, ask MCC if orbit locks are on (they should be).
- Keep shift summary up to date in HBLOG. Record all that happens.
- Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
- Document any beam condition change and send scaler GUIs to HBLOG
- Fill and submit the shift checklist in the logbook (login first) { Shift CheckList }
- check GEM gas bottle (location is behind the counting room )
- Perform 2H02A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer)
- With any issue contact On-Call Experts or RC
Every Run:
- Be sure LMS phase number is 1 (can be seen on camera :hallbcam09.jlab.org, you can manually change the LMS phase)
- LMS phase number will automatically change to 2 after taking 20,000 events.
- Record LMS phase number once during taking the physics events (event number > 30,000 on CODA).
- Record any LMS phase change during the production run, and manually change the LMS phase to an even number (2, 4, 6).
- After "Prestart" but before "Go", (to be added )
- After "Go": (to be added)
- Update the run spreadsheet on [logbook link to be added].
- See the whiteboard for everything else that should be done on a per-run basis.
CODA Instructions:
- On clonpc14, open a terminal, check if EXPID and SESSION is set correctly.
- >echo $EXPID (should return prad)
- >echo $SESSION (should return clasprad)
- reset the two variables if they are not correct
- >setenv EXPID prad
- >setenv SESSION clasprad
- open run control "runcontrol -rocs"
HyCal Instructions:
- HV must be always ON during the experiment including the period of moving from the Transporter to the running table .
- Periodically check the HyCal temperature either by the camera or from the computer monitor.
- Periodically check the chiller operation by checking the input/output pressure on camera (numbers should be between 20 to 30)
- HyCal HV control
- Do not change HyCal HV before contacting to experts (Li, Ashot)
- If it is permitted then ssh pradrun@prad , type: primexHV , password is PUs&r.
Online monitoring Instructions:
- HyCal online monitor
- on clonpc15 , type : cd PRad/PRadEventViewer-master/ [Enter].
- then type: source source env_scripts/setup_env_prad.csh [Enter], then: type: ./PRadEventViewer [Enter].
- now you should see the GUI of online monitor, at menu choose online mode -> start online mode
- GEM Online Monitor
- GEM Online Monitor is installed on clonpc13, locate this pc, label is at the bottom side of one Screen Monitor.
- go to : ~/PRad/GemView/
- then: source set_env.csh
- then: ./GemView
- There will be two GUI windows, first one is for all individual APVs, on this window, there are 72 separate histograms; second one for the decoded hit information.
- The first window is the main window to check, there are some printouts on good APV behaviors on the table, make sure all APVs behave similarly to those on the printout.
- Booster Online Monitor
- Boosters' current should be always larger than 0.001
- To monitor the booster power supplies do:
- on clonpc19
- ssh clonsl1 [Enter], then : konqueror [Enter].
- open the PRad wiki with this browser and click the following link,
- or you can type pradbst1.jlab.org for booster1 , pradbst2.jlab.org for booster2 and so on.
- Then choose DC power table.
GEM High Voltage Instructions:
- There are two high voltage modules for GEMs, module 1 is controlled by clondaq7, module 2 is controlled by clon10; log into those two PCs to start the GUI if needed. High Voltage GUI should be always open, they are usually opened on clonpc18 or clonpc19, please check those PCs before start a new GUI.
- Module GEM1: ssh -X prad@clondaq7 password: prad123 Module GEM2: ssh -X clasrun@clon10, no password needed for clon10
- On clondaq7, 1), source ~/GemView/set_env.csh; 2), go to ~/xb/GEM_HV_Module2 (Yes, it's named module2, actually controls GEM module 1 ) 3), root -l 4), .L gem_hv.cxx+ 5), .x main.cxx after these 5 steps, the GUI should pop up.
- On clon10, 1), go to ~/GEM_HV_Control/GEM_HV , 2), root -l , 3), .L gem_hv.cxx+ , 4), .x main.cxx . then the GUI should pop up.
- Operating Voltage for Both GEMs, 4050V; current: 735uA.
GEM Data Taking Instructions:
- Every day before beam starts, do a specific pedestal run for GEM. Needs to change readout list.
- ssh clondaq6, go to ~/PRad/Gem_Dev/,
- modify gem.cfg, change RUNTYPE to PEDESTAL, analyze 3000 events to generate a new pedestal. assign a name to pedestal file. name should include date(like 20150531), run number(like 1000), and shift information(like day shift). example: pedestal_20160531_day_run1000.root
- ./main /data/prad/prad_001XXX.evio.0
- copy the generated pedestal root file to ../Convert_Pedestal/ directory, generate txt files. do ./convert_pedestal /the/pedestal/root/file
- a new pedestal.txt will be produced in the ../Convert_Pedestal directory.
- copy this pedestal.txt file to $CODA/src/gem/run/pedestal.txt , before this, make a backup to the original pedestal.txt.
- There's a history track directory : /home/clasrun/PRad/Gem_Dev/GEM_pedestal_mapping_track . Everyday make a backup for pedestal and mapping to this directory. Follow the rules specified in the README.txt file. Keep a record of the run numbers in match with the pedestal and mapping files.
|
