For more information, please contact Robert Michaels, rom@jlab.org,
Alexandre Camsonne, camsonne@jlab.org
Expert Call List
Name | Phone | Status/detector | |
---|---|---|---|
Jessie Butler | (757) 269-5544 | jbutler@jlab.org | Hall A W/C |
Jack Segal | (757) 320-9977 | segal@jlab.org | Detector Support |
Kondo Gnanvo | (321) 604-8026 | kagnanvo@jlab.org | GEM |
Nilanga Liyanage | (434) 924-6596 | nl8n@virginia.edu | GEM |
Evaristo Cisbani | (757) 269-5584/+39 06 4990 2847 | cisbani@jlab.org | GEM |
Brian Quinn | (412) 268-3523 | bquinn@cmu.edu | HCAL |
Alexandre Camsonne | (757) 260-5064 | camsonne@jlab.org | DAQ |
Scott Barcus | (757) 269-5352 | skbarcus@jlab.org | HCAL |
Juan Carlos | (757) 741-8095 | cornejo@jlab.org | HCAL |
Todd Averett | (757) 561-6702 | tdaver@wm.edu | GRINCH |
Rachel Montgomery | 00 44 141 330 5531 | rmontgom@jlab.org | Timing Hodoscope |
Arun Tadepalli | (757) 269-6989 | arunts@jlab.org | Shower, Pre-shower |
Albert Shahinyan | (757) 269-5516 | shahinya@jlab.org | Webpage |
Eric Fuchey | efuchey@jlab.org | Software | |
David Flay | (914) 844-2927 | flay@jlab.org | Beamline, Target |
Donald Jones | (757) 768-1148 | tug38144@temple.edu | Run Coordinator Team Manager |
Shift Checklist
Albert's Shift Checklist
Donald's Shift Checklist
- If you are not already logged in, do so by clicking in the upper right of the page
- You should now be able to click Log in the upper left
- In log mode, you will be able to add notes in the boxes at the right
- The checkbox at the left of each item is optional and has no effect on the checklist, similarly the bold link lines are for informational purposes only (though you can feel free to add comments about the status of our documentation in them)
Item Instructions
- Entering shift info
- Enter the names of the shift workers (Shift Leader, Target Operator, Expert Shift Member, Compton Shift Member)
- Indicate which shift the checklist is for (day, swing, or owl)
- Alarm Handler
- Beam and Hall checks
- Left Arm Checks
- CODA
- Beamtime accounting
- HALOG - Instructions
- It is important to exit Online Monitors/Panguins, JMenu/StripCharts, and excess Firefox and Terminals when not in use. Otherwise the adaq computers run out of /tmp/ file system storage and RAM and cannot take data efficiently.
- Empty drip tray and place mug under spout on coffee maker
- Press the buttons on either side of the tray and pull toward you
- Place a mug under the spout while emptying the tray (and the previous mug) in the bathroom sink
- Replace the tray by sliding back into the machine
- Place a mug under the spout to help keep the tray from overflowing
Alarm Handler
Experimental Python Alarm Handler
For full documentation see Alarm Documentation
The new python alarm handler lives (for now) in a SBU JLab GitHub Repository
Start a new Instance:- Sound Server
- From within the hacuser acount on hacweb7, cd to ~/parity-alarms/ and execute "./bserver" to allow the alarm handler to make sounds
- Verify the alarm handler makes sound successfully by either using the Hall A Alarm Handler sound test, or by unsilencing some alarming alarm for a few seconds
- Parity Alarm Handler GUI
- From within the apar account on adaq1, execute the ~/bin/ command "ParityAlarms"
- If the online analysis is running then live JAPAN data alarms should be updating in the background
- To enable audible alarms please run the AlarmServer command from a new and separate terminal on the hacweb7 (EPICS) computer
- If the Parity Alarm handler complains about not finding numbers or config parameters then restore a back up of alarm.csv or alarmConfig.txt into the ~/alarm/ folder and try again (if that doesn't fix it ask Cameron)
Hall A/Target Alarm Handler
Start a new instance of the Hall A Alarm handler
- First check if any other instances are running, don't duplicate alarm handlers
- From the EPICS control computer (hacweb7), click on the red toolbox in the lower left corner (see Figure 1)
- Click on "AlarmHandler" in the popup menu
- The window shown in Figure 2 should appear
- Move the alarm handler window to the upper right of the screen
- Pin the window to all of the desktops
- Right Click on the "AlarmHandler" in the upper left corner
- Mouse over "To Desktop"
- Choose "All Desktops" at the top of the drop down menu
- Keep Above All Windows
- Right Click on the "AlarmHandler" in the upper left corner
- Go to Advanced, and select "Keep Above Others"
- Open the Current Alarm History
- Click the "View" context menu and select "Current Alarm History Window"
- This is most useful for getting detailed information about timing and values of alarms as they accumulate
- Information about alarms is also accessible by double clicking on items in the right half-panel
Checking or changing the Compton background rate alarm levels on the Hall A alarm handler
- To check the Compton background rate alarm levels:
- Open a terminal as hacuser@hacweb7
- Run the command:
caget ComptonDSbg1.HIHI ComptonDSbg2.HIHI ComptonUSbg1.HIHI ComptonUSbg2.HIHI
- To change the Compton background rate alarm levels:
- Check with Adam Zec or David Gaskell before changing the alarm settings
- Open a terminal as hacuser@hacweb7
-
ssh hacuser@hlal00
- Execute a caput command to set each channel's "HIHI" level
- For example, use this to change the ComptonDSbg1 limit to 7500:
caput ComptonDSbg1.HIHI 7500
- For example, use this to change the ComptonDSbg1 limit to 7500:
- After changing the four settings, run
caget ComptonDSbg1.HIHI ComptonDSbg2.HIHI ComptonUSbg1.HIHI ComptonUSbg2.HIHI
and post the new alarm settings in the HALog and email Adam (ajz3ee@virginia.edu)
Start a new instance of the Target Alarm Handler
- Make sure the target gui is running on the poltarac computer
cd ~/Desktop/PRex ./tgtgui Select the ALARMS button
- It should be similar to the Hall A alarm handler, but with difference tracked EPICS variables
Responding to an (audible) alarm
- Click on the alarm handler window in the upper right of the hacweb7 monitor (see Figure 2)
- This will open a window that lists the various pieces of equipment (see Figure 3)
- Please feel free to make strip charts out of any interesting EPICS variables that you find in the Alarm Handler or other GUIs. See Strip chartfor more information.
- If an alarm is white then it is a communications failure from an EPICS Input/Output controller (IOC) and should rectify itself in a minute or less (otherwise call the RC)
- If an alarm is red it means that some important parameter is out of range
- Please keep track of the set points and current value of anything that alarms, and if the alarm isn't transient and trivial please make a HALOG entry about it
- If the alarm continues for more than a few seconds please try to understand the nature of the issue and contact the RC or other nearby experts if it isn't immediately clear how to resolve it
- To increase/decrease the volume of parity alarm
- There are some sound level bars at the bottom left of the screen, use the mouse to pull those bars up/down to increase/decrease the volume.
VESDA Hall A Fire Alarm System
Is the VESDA System OK? (VESDA is the smoke/fire detection and alarm system. Check the Hall A VESDA Console on the wall beside the door to the computer room. Every light should be green and in the minimum lowest alert setting.Beam and Hall Checks
Alarm Handler
- VESDA System OK? (see Figure 8)
- VESDA is the smoke/fire detection and alarm system
- Check the Hall A VESDA Console on the wall behind the door
- Every light should be green and in the minimum lowest alert setting.
- Is alarm handler running on hacweb7?
- On hacweb 7, you should see a window in the upper right corner of the screen
- Look first in the "Alarm Handler" desktop to see if it is there
- Check all the windows if not
- If not open, see Alarm Handler
- On hacweb 7, you should see a window in the upper right corner of the screen
- Is the volume up on hacweb7? (both hardware and software)
- Go to Alarm Hall A Alarm Handler -> Setup -> Test Beep Sound
Hall A Tools and related menu screens
Beamline
- Visual Hall Inspection OK? (see Figure 9)
- Make sure to move the camera around and zoom in (See Figure 10)
- when complete, zoom all the way back out
- Beam Energy (MeV) (see Figure 2)
- Beam Current (µA)
- Current Target (45 degree ladder/90 degree ladder)
- See Target GUI on Target computer
- Or JMenu -> Search for Target GUI -> "Hall A Target Lifter" and it has the same information (as well as raster and other useful information)
- Beam Position Monitor (BPM) X/Y (mm) A
- Beam Position Monitor (BPM) X/Y (mm) E (Called BPM B in Hall A Tools)
- Downstream raster (labelled B or 2, US raster is not in use) on?
- Check the Oscilloscope in Counting House Middle Room: Yes/No
- when raster is off, looks like Figure 3
- when raster is on, something like halog 3654466
- Raster size (x vs. y in mm)?
- You can also check with the JMenu -> Hall A Fast Raster screen
- Fast feedback (FFB) on? Yes/No - should be on during Parity Production
- The easiest check is to look at the FFB information in bottom left corner of Hall A General Tools
- An additional way to check whether the FFB is on or off:
- in a terminal window, type JMenu
- search for "fast"
- Choose "Fast Feedback Control" (see Figure 5, which shows the upper left corner when FFB is OFF)
- The status is indicated by the button that is depressed (OFF and RUN in the figure)
- Do not use any of the Hall A Fast Feedback Control menus other than the "Fast Feedback Control" one. The screen should be small and have Hall A and C on it. You should NOT be able to edit any of the parameters.
- FFB should be ON during normal production running!
- However, FFB will be paused during beam modulation
- If BPMs are saturated or for FFB troubleshooting see: FFB troubleshooting
- Is the Beamline Vacuum OK?
- JMenu -> "vacuum hall a shield to target" -> Hall A Shield Wall To Target
- Or pull up stripcharts in LivePlot and monitor them through your shift
- BCM temperature (K) (PV, PS, Thermocouple)
- These temperature readbacks are located in the middle DAQ room, in rack CH0B06 (far left) at the very top (see Figure 4)
- If these differ by +/-.5 from (110.0, 110.0, ~115.0) (Fahrenheit) contact RC and halog
- It is important that these temperatures stay stable within 0.5 Fahrenheit or else the BCM current readout will become uncalibrated (only the two values on the right are critical)
- Accelerator Arc Beam Energy NMR locked?
- JMenu -> Search for "Energy Lock GUI" -> Applications section -> "Energy Locks"
- Verify if the box locked is ON/OFF - should be on during Parity Production
- If the 3 "OR", and "1A" lights are green then the energy is locked. In FFB on mode "2A" will be yellow or red and this is OK, in non-FFB mode it needs to be green too - HALOG 1, 2, 3, 4
- Is BPM 11X (IPM1C11) saturated? It needs to be not saturated during all Parity Quality Beam, or else
we cannot take useful data.
- If Fast Feedback is OFF: Check in JMenu -> Search "iocse9" -> Choose Application: SEE BPM Live Display Screen - iocse9 -> Check the many green boxes for IPM1C11 Hi X Sat channel (its a red or green box, Green is good, Red is bad and you should call the RC)
- If Fast Feedback is ON: The above menu will be frozen and not useful, instead check the Online Plots of BPM11 and Event Cut information from Parity Analyzer (should be in the Crucial Systems and Event Cut tabs)
Hall Status
- Are the Compton Background Rates sufficiently low (<30kHz according to Adam)?
- JMenu -> Plots -> MyaPlot -> Right Click and Load a Configuration -> Select PREX in Directories -> Compton Background Rates -> Ok Move to Now
- Units are in Hz
- If you see anything above 30kHz in any of the strip charts, this is bad, and the Compton Expert on shift should be notified
- Is the Compton DAQ running? (It should be during Parity Production)
- Ask the Compton expert on shift
- Is the Compton Photon Detector PMT High Voltage on? (It should be during Parity Production)
- On the HV computer go to workspace 3. There should be a HV GUI there labeled hatsv5:2003.
- Naviagte to Slot 5 and look at channel L1.9. It should be set to -1569 V and turned on.
- If either it is not turned on and we are in production, or the voltage is lower (as in more negative) than -1612 V, contact Adam immediately.
- Is the Moller Polarimeter within operational temperature limits? See Figure 11 for reference or
Simona's elog entry
- The screen can be obt ained through: NewTools -> JMenu -> "Moller Polarimeter Temperature Monitor" -> Hall A Moller Temperature
- The optimal points are: Cryocooler (T1) ~ 3K, Magnet (T2) ~3K, Magnet Lead #1 ~40K, Magnet Lead #2 ~ 40K
- If something happens for the Moller Polarimeter, Call Simona
- Septum current (A) and polarity? Matches whiteboard set-point?
- Big Bite: JMenu -> Search for Big Bite Septum or Hall A Septum
- HES: Hall A Tools GUI, find the HES Dipole button in the top right section
- Before adjusting septum please read and sign the septum OSP document (in the yellow OSP folder)
Gases
- Pressures (see Figure 6)
- Argon pressure (psi)
- Ethane pressure (psi)
- CO2 pressure (psi)
Left Arm Checks
- Open Hall A General Tools
- Left Arm momentum (GeV)
- The blue box called P0 SET (0.00000 GeV/c in Figure 1)
- Left Arm Q1, Q2, D, Q3 regulators on (yes/no?)
- Click on the small blue square next to P0 SET (GeV/c) (see Figure 2)
- Regulator status for each magnet is indicated by the depressed button (all regulators are off in Figure 2)
- Check the whiteboard for intended settings
- Left Arm cryo flow level OK (Green)?
- He > 60% (Ignore Nitrogen)
- In the column labelled L(%) (100.2, 90.3, and 89.3 in Figure 1)
- Left Arm NMR OK? Yes/No
- The NMR field readback is indicated in the "D-N" row of the GUI
- The NMR meter is useful only at > ~GeV set points, so if the magnets are too low then the NMR readback will be useless and fluctuating wildly (in which case the Gauss meter readback is useful, indicated in the "D-G" row)
- The NMR read-back quality can also be determined by looking at the Oscilloscopes in CH main room rack CH01A02 (above the adaq2 terminal). If the NMR is locked then the triangle wave and NMR readback will be synced and locked onto eachother in both scopes.
- Left Arm Q1 B-Field (+/-T), Momentum (GeV/c), Polarity (N/P), current (A)
- Left Arm Q2 B-Field (+/-T), Momentum (GeV/c), Polarity (N/P), current (A)
- Left Arm D B-Field (+/-T), Momentum (GeV/c), Polarity (N/P), current (A)
- Left Arm Q3 B-Field (+/-T), Momentum (GeV/c), Polarity (N/P), current (A)
- Are the magnets properly meeting their setpoints (are the read-back values within 0.5% of the
setpoints?)
- Check the setpoints and readbacks by clicking on the I(A) menu button and looking at each magnet's GUI independently
- On the bottom left in the black box called BOX CONTROLS are the Setpoint (Amps) and the ReadBack (Amps)
- Be careful , as you are able to change the settings from within these GUIs.
- Also, all magnets should be in negative polarity for Prex/Crex
- Left VDC gas flow on (top/bottom)?
- Indicated by Orange "Gas Flow" panel in Hall A General Tools screen T_VDC/B_VDC l/h readbacks
- Left VDC HV on (top/bottom)?
- See VDC HV GUI for more information
- Look at the kV values in the VDC HV section of the Hall A Tools (Figure 3)
- VDC thresholds (yes/no?)
- See Hall A General Tools bottom right corner (Figure 4)
- All 4 set points and readback values should be 3.0 V
- Left s0/s2m HV on? (s0 may be off for production, check with expert)
- Main Detector HV on/off? -
- See LHRS MainDet HVs
- SAM HVs on/off?
- See SAMs HVs
- Have you checked the quality of the most recent online plots for the Left ARM counting mode DAQ (if a run was taken during your shift)?
CODA
Starting Parity DAQ CODA
Starting the GUI
- Log in as apar@adaq1
- In a terminal type startcoda
- 4 xterms will appear (red, orange, green and yellow) as well as the main CODA window (see Figure 1)
- CODA will automatically load the last configuration used. If you are ok with this then just go to Platform->Connect
- To change the configuration, choose Configurations->Cool
- Select the desired configuration from the dropdown list
- Production running would be ALL_PREX
- Once you have loaded a configuration, some of the icons (see descriptions below) will change from grey (see Figure 2) to green (Figures 3-5)
- Press the configure icon (see Figure 3)
- Warnings about waiting for a ROC can be ignored if it does not take too long to respond (~10s) and things are eventually successful
- Error messages should be taken seriously
- You can try a Reset and re-Configure
- If that doesn't work - see DAQ Troubleshooting
- Press the Download icon (see Figure 4)
Starting a Run
- After starting the GUI and loading a configuration (see above)
- Press the Prestart icon (see Figure 4)
- As above, warnings about waiting for a ROC can be ignored (if it does not take too long to respond, ~10s) and things are eventually successful
- Error messages should be taken seriously!
- You can try a Reset and re-Configure
- If that doesn't work - see DAQ Troubleshooting
- Press Go (see Figure 5)
- a window will pop up where you can add notes (see Figure 6)
- you can click the buttons to choose the data that goes to the runDB
- you can also add a comment at the bottom if needed
- Press "CLICK HERE TO ACCEPT AND START THE RUN"
- the event counter should start incrementing (see Figure 8)
- the event rates should be expected values
- a window will pop up where you can add notes (see Figure 6)
- If you made a mistake, such as:
- accidentally loading the wrong configuration
- stop and restart the run
- make a followup halog entry and refer to the run
- take note of it in the run list in the shift summary
- accidentally submitting the wrong notes in the notes window
- you can let the run continue as long it is the correct configuration
- make a followup halog entry and refer to the run
- take note of it in the run list in the shift summary
- accidentally loading the wrong configuration
Ending a Run
- Press End
- A window should open so that you can add any needed comments (see Figure 7)
- add any notes if necessary
- Press "CLICK HERE TO ACKNOWLEDGE AND EXIT"
- if this was a normal end of the run, and it ends successfully
- all the states should change to downloaded
- the Prestart icon should be green
- A window should open so that you can add any needed comments (see Figure 7)
- If the run ends because of a problem with CODA - see DAQ Troubleshooting
Description of the GUI
Numbered from the top left of the GUI window (see any of the Figures):
- Configure (tools) - this opens a drop-down menu to choose the configuration
- Download (floppy disk) - this loads the chosen configuration to the crates
- Prestart (triangle with point to right followed by ||) - this will prepare to start a run
- Go (triangle with point to right) - this starts a run
- End (square) - this ends a run
- Fast Start (double-triangle pointing right) tries to go through all the steps (can be used as long as things aren't changing)
- Reset (double-triangle pointing left) configured, but not downloaded (if you need to change configuration or GUI is wonky)
- Pause (two vertical bars) - pauses a run (rarely used - to quote Paul King "Nothing good can come of this.")
Starting Counting Mode DAQ CODA
"Counting mode" designate 2 independent DAQs for each of the two spectrometers (in contrast with parity DAQ which includes both). It shall be run after beam is set up for counting mode
- For left HRS:
- Run CODA (usual "startcoda" command) on adaq@adaq3;
- default DAQ configuration should be LeftHRS;
- For right HRS:
- Run CODA (usual "startcoda" command) on adaq@adaq2;
- default DAQ configuration should be Righthrs;
Starting Compton DAQ CODA
The information for this has been moved to Compton DAQ HOWTO. Consult there for how to start and stop runs.
Shift checklist
- Latest run type (Test, Physics,..)
- You can get this from the auto-logs of start and stop runs
- It is also in the runstart and runend windows
- Is the auto replay script running?
- ask the analysis expert
- Run added to shift summary?
- keep up with the run list in your shift summary
- Please attach the left/right HV and Scalers Screenshots to the shift report (do we need this)?
- Time of beginning of latest run
- This is at the top of the CODA Run Control Window
- You also can get this from the auto-logs of start and stop runs
- Latest run number
- This is at the top of the CODA Run Control Window
- You also can get this from the auto-logs of start and stop runs
- Check the scalers (snapshot)
Beamtime Accounting
Open your browser on an a-onl@aonl machine
(firefox from an adaq login terminal will work too)
- https://bta/ or https://accweb.acc.jlab.org/bta/
- Login with your CUE username/password
- File->Open Timesheet
- choose: Hall:A -> Day-> Shift: Owl (or Day or Swing)
- click "Open"
- If you want to edit hour(s), Please click very right "pencil" icon, then make a comment or edit time -- DO NOT USE *EDIT ALL* ON THE BOTTOM
- "Load from EPICS" should work in production mode, however you should check the numbers. Also it does not work for other modes like moller commissioning or tests.
- MCC likes to have the sheet updated throughout the course of the shift, and they need the first 7 hours completed right at the 1-hour before the end of your shift mark (their shifts end earlier than ours)
- To save your edited info into DATABASE, just click "V" (check-mark), it's in the same place where the "pencil" icon was. Don't forget to save, your edits will be wasted !
- When MCC call you for BTA (An hour before your shift end), click "SAVE INFO for MCC"
- Read number ABU and BANU. (That's it ! This should work !)
- End of shift, please sign off
- Once you've done, please Logout.
Trained Operational Safety Procedure Form
For more information, please contact Flay, David, flay@jlab.org
Meekins, David, meekins@jlab.org
Shift Leader
- Calculate ABU's when in production mode by counting good Coulombs per run: 150uA each hour = 0.54C. 1hour runs. For each hour long run(s) take #good-Coulombs/0.54C = #ABU's (even when running at a lower current, obsolete method: https://logbooks.jlab.org/entry/3785102)
- Communicate clearly and effectively with shift crews and MCC (7047)
- Arrive ~10 minutes early to your shift to talk with the previous shift crew
- Answer the phone
- Communicate with the RC
- Consult the Daily Run Plan and contact the run coordinator whenever problems happen that cannot be solved by shift workers
- Log any status information to the HALOG (Make sure to log in!)
- Maintain data taking quality and efficient use of beam time
- Use Panguin to evaluate data quality
- Post Snapshots with HALOG of important information at least twice a shift.
- Include- Hall A tools, BPM strip-charts, and BCM strip-charts.
- Include any snapshots of the details after a change
- Please feel free to post these Snapshots more often
- Sample screenshots to make during shifts (examples below during no-beam conditions, purely descriptive): collimator temp, Compton ion chambers, bpms, vacuums, parity controls, FFB, raster, ioc chamber
- Collimator and Beamline temperatures
- Hall A Beamline monitors, and Compton and Moller magnets, and bleedthrough check - useful for evaluating beam set up and tune
- Ion Chambers
- FFB system - these examples show the system while inactive - check a more recent log entry with active FFB for a prescriptive example
- Hall A Raster
- Hall A Tools, magnets
- Hall A Target status
- Scaler GUI
- Injector Loss Monitor - useful for diagnosing large Aq widths and noise problems
- Charge Feedback Monitor
- Compton
- Target motion and mask
- Beamline Vacuum
- Parity Controls
- Keep track of beam time accounting
- Follow the directives in the COO!
- Log the following in an end of shift summary in the HALOG:
- run list (describing the goal of this run: eg production on Pb, BCM calibration...) and report main statistic numbers
- any major events, including hall access (in addition to making log entries when they happen)
- Complete the Shift Checklist at the beginning of the shift - see Instructions
- Note: There is a convenient script in ~/cameronc/SL/auto-SL.sh which will walk you through the steps of the shift checklist and provide easily copyable text-outputs for easy entry into the checklist and comparison with expectations
- Print off additional run sheets (printer "chax"): https://logbooks.jlab.org/entry/3700479
- A GMn analysis shift worker will be on hand for most shifts (although not required by the COO) to help out in high demand situations. Please coordinate with them as well.
- Read Common Problems for information on how to deal with common issues cropping up
Run Plan
Full Run Plan
Overview Table
For more information, please contact Bogdan Wojtsekhowski, bogdanw@jlab.org
Pre-Shower
Presentations
BigBite shower and preshower current status - 10 Jan 2021Preshower and shower disassembling/reassembling status - 24 Feb 2020
Preshower disassembling/reassembling - 17 Feb 2020
Shower
Presentations
BigBite shower and preshower current status - 10 Jan 2021GEMs
Presentations
PREX GEM data analysis - 8 Feb 2021INFN GEM Status - 31 Aug 2020
INFN GEM Cosmic Ray Analysis Status (3) - 12 Dec 2019
INFN GEM Cosmic Ray Analysis Status (2) - 12 Dec 2019
INFN GEM Cosmic Ray Analysis Status (1) - 7 Nov 2019
Status of UVA GEM setup in EEL clean room (3) - 19 Dec 2019
Status of UVA GEM setup in EEL clean room (2) - 19 Dec 2019
Status of UVA GEM setup in EEL clean room (1) - 10 Oct 2019
Update on UVa GEMs - 25 Apr 2019
Preliminary Drawings of SBS FT GEMs with U-V Strips - 16 Jan 2019
INFN GEM – update - 25 May 2019
GMN GEM analysis and GEM DAQ update - 23 May 2019
FT GEM (commissioning) status - 16 May 2019
SBS GEM Test
BigBite GEM digitization - 15 Nov 2017
BigBite DAQ
Trigger GroupsTrigger Logic
Cabling Maps
Cabling Paths
Presentations
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2019/C.Ayerbe-GRINCH_DAQ-20190109.pdfhttps://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/GEMAnalysisAndDAQUpdate_Danning_SBS_WeeklyMeeting_05232018.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/C.Ayerbe-GRINCH_DAQ-20180110.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/tortorici_DAQ_preparation_8.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/DAQ_preparation_7.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/DAQ_preparation_6.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/1611_SBS_DAQ_DOE_review_v1.pdf
SuperBigBite DAQ
Schematic
DAQPresentations
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/SBS-DAQ-Apr-25-2018.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/GEMAnalysisAndDAQUpdate_Danning_SBS_WeeklyMeeting_05232018.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2017/SBS-HCAL-DAQ-Sept-20-2017.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2017/SBS-DAQ-update-Mar15-2017.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/tortorici_DAQ_preparation_8.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/DAQ_preparation_7.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/DAQ_preparation_6.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/1611_SBS_DAQ_DOE_review_v1.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/GEMAnalysisAndDAQUpdate_Danning_SBS_WeeklyMeeting_05232018.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2017/SBS-HCAL-DAQ-Sept-20-2017.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2017/SBS-DAQ-update-Mar15-2017.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/tortorici_DAQ_preparation_8.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/DAQ_preparation_7.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/DAQ_preparation_6.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2016/1611_SBS_DAQ_DOE_review_v1.pdf
HCal
Presentations
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2019/cornejo_20190718_brief_hcal_update.pdfhttps://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2019/Cornejo_HCAL_20190116.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/HCal_update_Aug_07_2018.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/HCal_Status_Sept_05_2018.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/HCAL_Update_2018-Oct-17_final-v2.pdf
GRINCH
Presentations
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2019/C.Ayerbe_GRINCH-Report_20190425.pdfhttps://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2019/2019-11-21_GRINCHStatus.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/SBS_GRINCH_update_12-Sept-2018.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2018/C.Ayerbe-GRINCH_DAQ-20180110.pdf
https://hallaweb.jlab.org/12GeV/SuperBigBite/SBS-minutes/2017/GRINCH_Apr_2017_Update.pdf
Timing Hodoscope
Description
Description of Timing HodoscopePresentations
BigBite Timing Hodoscope Update (2) - 17 July 2019BigBite Hodoscope Update (1) - 26 June 2019
Draft: Observations and Recommendation on the Rebuilding of Hodoscope Bars for the Big Bite Spectrometer - 10 May 2020
BigBite Timing Hodoscope SBS Weekly Meeting Update Hall A Jefferson Lab - 21 September 2020
|
|
|
|
|
---|---|---|---|---|
SBS | https://bluejeans.com/7634370740 | Andrew Puckett | puckett@jlab.org | Monday 10:00 AM |
DAQ | https://bluejeans.com/596873830/ | Alexandre Camsonne | camsonne@jlab.org | Friday 11:00 AM |
GEMs | https://bluejeans.com/8595586919 | Kondo Gnanvo | kagnanvo@jlab.org | Wednesday 10:00 AM |
HCal | https://bluejeans.com/594276564 | Scott Barcus | skbarcus@jlab.org | Tuesday(bw) 10:00 AM |
Software | https://bluejeans.com/7634370740 | Andrew Puckett | puckett@jlab.org | Friday 1:00 PM |
For more information, please contact Nandhu Sridhar, nandhu@jlab.org
GMn Experiment
For more information, contact Albert Shahinyan, shahinya@jlab.org
For more information, please contact Ed Folts, folts@jlab.org
GMn Safety Documents
*
*
*
*
*
*
*
*
*
*
*
For more information, please contact Ed Folts, folts@jlab.org
About
Detectors
Physics Documents
Logbook
New Electronic LogbookPictures















Analysis
Under Construction
Contact Information
Name | Phone Number | |
---|---|---|
Hall A Counting house | 757-269-5501, 757-269-5507 | |
Run coordinator | 757-876-1787 | |
MCC | 757-269-7046, 757-269-7047, 757-269-7048 | |
Crew chief | 757-269-7045 | |
RadCon | 757-876-1743 | |
Guard house | 757-269-5822 | |
Cynthia Keppel Hall A/C | 757-269-7580 | keppel@jlab.org |
Hall A W/C J. Butler | 757-269- 5544 | jbutler@jlab.org |
Jack Segal | 757-320-9977 | segal@jlab.org |
Bogdan Wojtsekhowski, GMn contactperson | 757-269-7191 | bogdanw@jlab.org |
Andrew Puckett, WAPP contactperson | 860-468-7137 | puckett@jlab.org |
Eric Fuchey, nTPE contactperson | efuchey@jlab.org | |
Brad Sawatzky, GEn-recoil contactperson | 757-269-5947 | brads@jlab.org |
Alexandre Camsonne, GMn contactperson | 757-260-5064 | camsonne@jlab.org |