Difference between revisions of "Analysis Expert"

From PREX Wiki
Jump to navigationJump to search
 
(18 intermediate revisions by 3 users not shown)
Line 15: Line 15:
 
[[Main_Page|<B>PREX Main</B>]] << [[Information for Shift Takers]] <br><br>
 
[[Main_Page|<B>PREX Main</B>]] << [[Information for Shift Takers]] <br><br>
  
 +
Sign up for the [https://docs.google.com/spreadsheets/d/1XL5UY-VVrMkUwjbNzQ7xb6f4rYyqHwUpd034jckEjq0/edit#gid=1086928437 Analysis shifts]!
  
 +
== Analysis shift worker ==
 +
The analysis shift worker is tasked with ensuring that the data is analyzed after it is taken, and with assisting in all tasks that the shift leader requests.
  
−
== Analysis Expert Tasks ==
+
There are tools available for the analysis shift worker to check the quality of the data and analyze/reanalyze runs in '''[[Online analysis]]'''
 +
* [[Online analysis | Online analysis How-To]]
 +
* [[PVDB | PVDB]]
 +
* [[Online Plots]]
  
 +
== Analysis Shift Worker Tasks ==
 +
# Ensure shift crew is counting good coulombs properly and recording ABU's properly ((https://logbooks.jlab.org/entry/3785102)
 
# Assist shift crew in data taking as needed
 
# Assist shift crew in data taking as needed
 
#* help diagnose and solve CODA issues
 
#* help diagnose and solve CODA issues
 
#* answer questions about plots in Panguin
 
#* answer questions about plots in Panguin
 +
#* remind the TO to check the Panguin plots frequently
 
# Makes sure online analysis is up to date
 
# Makes sure online analysis is up to date
 
# Look at beam quality
 
# Look at beam quality
Line 28: Line 37:
 
#* Log anything that you think is an issue that needs to be investigated and email the WAC
 
#* Log anything that you think is an issue that needs to be investigated and email the WAC
 
# Decide when to change IHWP settings
 
# Decide when to change IHWP settings
−
#* Each slug should have ~8 runs, but the real measure is a total charge of at least 1.2 C (but not too much more than this)
+
#* Each slug should have ~15 runs(at 50% efficiency), but the real measure is a total charge of at least 4.0 C (but not too much more than this, like 4.2C)
 
#* Keep track of the accumulated charge in the slug using the [[PVDB#Accumulated_charge_monitor | counter]]
 
#* Keep track of the accumulated charge in the slug using the [[PVDB#Accumulated_charge_monitor | counter]]
 
#** If the current run had steady beam and no known issues, check the accumulated charge before it ends
 
#** If the current run had steady beam and no known issues, check the accumulated charge before it ends
−
#** If the accumulated charge is >1.3 C including all runs but the current run, and the current run is good, you can probably increment the slug
+
#** If the accumulated charge is >4.0 C including all runs but the current run, and the current run is good, you can probably increment the slug
 
#** Ask the shift leader to follow the instructions at [[Flipper]]
 
#** Ask the shift leader to follow the instructions at [[Flipper]]
 +
 +
== Remote Shifts ==
 +
=== Connecting to JLab ===
 +
* Call into the always-on Bluejeans call (even if no-one else calls in immediately): https://bluejeans.com/779147679
 +
* Open these standard webpages:
 +
** [https://logbooks.jlab.org/book/halog HALOG]
 +
** [https://hallaweb.jlab.org/halog/screen_snapshots/target/ Online Target]
 +
** [https://hallaweb.jlab.org/halog/screen_snapshots/controls/ Hall A Tools]
 +
** [https://prex.jlab.org/analysis/ Prompt Plots] (note the useful links section)
 +
** [https://hallaweb.jlab.org/parity/prex/onlinePlots/panguin_online_shiftcrew.php Online Panguin Plots]
 +
* Connect to the persistent '''Analysis shift worker VNC session''' running on aonl1 - From there, as needed, please pull up useful plots and analysis tools that you may need
 +
** Select from the list of suitable connection options in the section [[Analysis_Expert#Modes_of_JLab_Connection|below]]
 +
* Use shared-computer etiquette - [https://hallcweb.jlab.org/DocDB/0008/000868/001/Counting_House_TipsTricks-Jun2017.pdf JLab Hall A computer tips and tricks]
 +
* Be aware of the Hall A phone numbers [in the counting house] (please try to use Bluejeans to keep the CH phones open for official communications) and [https://userweb.jlab.org/~sanghwa/prex/running/HallA_Phone.pdf in the hall]
 +
 +
=== Monitoring the Shift ===
 +
The Analysis shift worker should rely first on those standard webpages mentioned above, both to minimize taxing the Hall A computers' resources and to ease the adherence to a standard work-space among analysis shift workers.
 +
 +
That being said, analysis shift workers are encouraged to connect to the '''Analysis shift worker VCN session''' (described below) which should have useful screens and GUIs that persist between analysis shifts among the different workers (again, to make life easier)
 +
 +
===Standard Screens and Where to Find Them===
 +
* Strip Charts
 +
** From apar@adaq2
 +
ssh -f hacuser@hacweb7 'myaplot .....'
 +
* Expert (alarm-lite) GUI
 +
** From apar@adaq2
 +
ExpertGUI
 +
* JMenu or NewTools
 +
** From a-onl@aonl1
 +
jmenu or NewTools
 +
 +
=== Modes of JLab Connection ===
 +
* JLab's VDI Windows 10
 +
** In a Browser: https://vdi.jlab.org/portal/webclient/index.html#/desktop
 +
** From your local VDI Application:
 +
* SSH (from any functioning terminal with X11 forwarding in place)
 +
* SSH display tunneling
 +
* JLab VPN: https://vpn.jlab.org/+CSCOE+/portal.html, sign in with mobile pass
 +
 +
=== VNC Sessions ===
 +
We have 3 dedicated VNC sessions maintained by the collaboration for general use:
 +
* a-onl@aonl1 :1 - For the Shift Leader and Target Operator to share between themselves, containing useful GUIs and anything that they may want to both visualize without physical proximity
 +
* a-onl@aonl2 :1 - For the official analysis shift workers. This one should be maintained and contain standard useful screens for the analysis shift workers to share amongst themselves
 +
* a-onl@aonl3 :1 - For any experts on call who may need to access standard screens, without interfering with the dedicated shift workers. Use of this VNC session should be coordinated by the on call experts and the Run Coordinator
 +
To access one of these VNC sessions execute:
 +
vncviewer aonl# :1 --Shared=1
 +
or
 +
CREX-VNC
 +
 +
More dedicated VNC sessions can be created for use by experts off site to speed their data analysis and investigations. Please contact Cameron before adjusting any VNC sessions or settings, or to obtain the VNC password.

Latest revision as of 10:18, 10 August 2020

Quick Links
HOW TOs
CODA
WAC Tools
Online analysis How-To



PREX Main << Information for Shift Takers

Sign up for the Analysis shifts!

Analysis shift worker

The analysis shift worker is tasked with ensuring that the data is analyzed after it is taken, and with assisting in all tasks that the shift leader requests.

There are tools available for the analysis shift worker to check the quality of the data and analyze/reanalyze runs in Online analysis

Analysis Shift Worker Tasks

  1. Ensure shift crew is counting good coulombs properly and recording ABU's properly ((https://logbooks.jlab.org/entry/3785102)
  2. Assist shift crew in data taking as needed
    • help diagnose and solve CODA issues
    • answer questions about plots in Panguin
    • remind the TO to check the Panguin plots frequently
  3. Makes sure online analysis is up to date
  4. Look at beam quality
    • Look at runs from a previous good period and compare to the current runs
    • Watch for changes in means and widths over time
    • Log anything that you think is an issue that needs to be investigated and email the WAC
  5. Decide when to change IHWP settings
    • Each slug should have ~15 runs(at 50% efficiency), but the real measure is a total charge of at least 4.0 C (but not too much more than this, like 4.2C)
    • Keep track of the accumulated charge in the slug using the counter
      • If the current run had steady beam and no known issues, check the accumulated charge before it ends
      • If the accumulated charge is >4.0 C including all runs but the current run, and the current run is good, you can probably increment the slug
      • Ask the shift leader to follow the instructions at Flipper

Remote Shifts

Connecting to JLab

Monitoring the Shift

The Analysis shift worker should rely first on those standard webpages mentioned above, both to minimize taxing the Hall A computers' resources and to ease the adherence to a standard work-space among analysis shift workers.

That being said, analysis shift workers are encouraged to connect to the Analysis shift worker VCN session (described below) which should have useful screens and GUIs that persist between analysis shifts among the different workers (again, to make life easier)

Standard Screens and Where to Find Them

  • Strip Charts
    • From apar@adaq2
ssh -f hacuser@hacweb7 'myaplot .....'
  • Expert (alarm-lite) GUI
    • From apar@adaq2
ExpertGUI
  • JMenu or NewTools
    • From a-onl@aonl1
jmenu or NewTools

Modes of JLab Connection

VNC Sessions

We have 3 dedicated VNC sessions maintained by the collaboration for general use:

  • a-onl@aonl1 :1 - For the Shift Leader and Target Operator to share between themselves, containing useful GUIs and anything that they may want to both visualize without physical proximity
  • a-onl@aonl2 :1 - For the official analysis shift workers. This one should be maintained and contain standard useful screens for the analysis shift workers to share amongst themselves
  • a-onl@aonl3 :1 - For any experts on call who may need to access standard screens, without interfering with the dedicated shift workers. Use of this VNC session should be coordinated by the on call experts and the Run Coordinator

To access one of these VNC sessions execute: 

vncviewer aonl# :1 --Shared=1

or 

CREX-VNC

More dedicated VNC sessions can be created for use by experts off site to speed their data analysis and investigations. Please contact Cameron before adjusting any VNC sessions or settings, or to obtain the VNC password.

Retrieved from "https://prex.jlab.org/wiki/index.php?title=Analysis_Expert&oldid=11374"