Difference between revisions of "AIEC Weekly Meeting Sep. 23, 2021"

From epsciwiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 36: Line 36:
 
# Good file list (Nikhil)
 
# Good file list (Nikhil)
 
# PrimEx run plan (Naomi)
 
# PrimEx run plan (Naomi)
 +
#* CPP projected start date: May 2, 2022
 
# Time-to-Distance (Diana)
 
# Time-to-Distance (Diana)
 
# CLAS12 Data prep (Torri)
 
# CLAS12 Data prep (Torri)
 +
#* getting good run list from RGA data
 +
#* making trees with "non standard" banks: TBHits, TBTracks
 +
#* totally remade GitHub repo
 
# Deployment System/Shift Worker Interface
 
# Deployment System/Shift Worker Interface
 +
# Publication planning
 +
#** Calibration parameter prediction
 
# AOT
 
# AOT
  
 
=== Minutes ===
 
=== Minutes ===
−
''TBD''
+
Attendees: Naomi J., Torri J., Nikhil K., Thomas B., Kishan R., Mike G., David L.
 +
 
 +
* Diana's Document on Gain Correction Factor
 +
** Not enough people read it. Assign as action item for next week
 +
** Diana identified a couple of more items to add
 +
*:
 +
* Why is 2018 data so bad?
 +
** Naomi thought about some possibilities
 +
*** Beam trips were much worse
 +
*** Diamond was worse (Alex A. reported strong dependence on orientation)
 +
*** Beam tune (at one point better agreement between orientations noticed after high-quality beam tune)
 +
** How to address
 +
*** Naomi suggested we focus on using the CDC HV board currents instead of external beam parameters.
 +
*** Some concern over how much time to spend on reproducing GCF for 2018 data as it prevents us from moving towards the final goals of the project.
 +
*:
 +
* Good File List (Nikhil)
 +
** Nikhil was able to produce a list of runs for which the 001 file (the one used for calibrations) was "good" (i.e. no beam trips)
 +
** System scrapes data from CCDB utilities.
 +
*** It was noted that there is a python API for CCDB. This was not pointed out to Nikhil earlier, but he now has a working system so we go with that.
 +
*** Run the system over the 000 and 002 files from 2018 so we can identify if which runs have at least one "good" file amongst the first 3
 +
*:
 +
* PrimEx Run Plan
 +
** CDC is expected to be turned on about 9.5 days from now (n.b. that schedule has since changed)
 +
** Expect 16 shifts with beam on (4 days)
 +
** One of us will need to sit in as additional remote shifter to handle determining the HV setting and implementing it between runs
 +
** We will need to set up a schedule for which of us will be online
 +
*** Thomas, Naomi, Torri, and David will likely be the ones implementing this.
 +
*** We will set up internal training
 +
*:
 +
* Time to Distance Calibration
 +
** No progress last week
 +
*:
 +
* CLAS12 (Torri)
 +
** Trying to get a good run list. Not clear how to obtain this
 +
** Able to produce Trees now
 +
** Setup a GitHub page listing projects
 +
*** Need to add everyone's Github account to it
 +
 
 +
 
 +
==== Action Items ====
 +
# Read the Gain Correction Factor Status Document (Everyone)
 +
# Check for "good" runs in the first 3 files (0,1,2) of the 2018 data (Nikhil, Torri)
 +
# Schedule for who from our group will be on shift to change HV settings
 +
#* [https://halldweb.jlab.org/DocDB/0052/005221/001/AIEC_HV_plans.pdf Plans] (Naomi's slides)
 +
#* [https://halldweb.jlab.org/wiki/index.php/Run_Coordination_Meetings:Summer2021 PrimEx Run Plan]
 +
# Add everyone's Github account to the Github [https://github.com/JeffersonLab/AIEC/projects AIEC Projects page] (Torri)

Latest revision as of 10:13, 28 September 2021


The meeting time is 4:00pm.


Connection Info:

You can connect using BlueJeans Video conferencing (ID: 122 747 574). (Click "Expand" to the right for details -->): 

Meeting URL
 https://bluejeans.com/122747574/3273?src=join_info

Meeting ID
122 747 574

Want to dial in from a phone?

Dial one of the following numbers:
+1.888.240.2560 (US Toll Free)
(see all numbers - https://www.bluejeans.com/premium-numbers)

Enter the meeting ID and passcode followed by #

Connecting from a room system?
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode

Agenda:

  1. AIEC Gain Factor Summary
  2. PI Exchange (see right)
    PI Exchange e-mail
  3. Good file list (Nikhil)
  4. PrimEx run plan (Naomi)
    • CPP projected start date: May 2, 2022
  5. Time-to-Distance (Diana)
  6. CLAS12 Data prep (Torri)
    • getting good run list from RGA data
    • making trees with "non standard" banks: TBHits, TBTracks
    • totally remade GitHub repo
  7. Deployment System/Shift Worker Interface
  8. Publication planning
      • Calibration parameter prediction
  9. AOT

Minutes

Attendees: Naomi J., Torri J., Nikhil K., Thomas B., Kishan R., Mike G., David L.

  • Diana's Document on Gain Correction Factor
    • Not enough people read it. Assign as action item for next week
    • Diana identified a couple of more items to add
  • Why is 2018 data so bad?
    • Naomi thought about some possibilities
      • Beam trips were much worse
      • Diamond was worse (Alex A. reported strong dependence on orientation)
      • Beam tune (at one point better agreement between orientations noticed after high-quality beam tune)
    • How to address
      • Naomi suggested we focus on using the CDC HV board currents instead of external beam parameters.
      • Some concern over how much time to spend on reproducing GCF for 2018 data as it prevents us from moving towards the final goals of the project.
  • Good File List (Nikhil)
    • Nikhil was able to produce a list of runs for which the 001 file (the one used for calibrations) was "good" (i.e. no beam trips)
    • System scrapes data from CCDB utilities.
      • It was noted that there is a python API for CCDB. This was not pointed out to Nikhil earlier, but he now has a working system so we go with that.
      • Run the system over the 000 and 002 files from 2018 so we can identify if which runs have at least one "good" file amongst the first 3
  • PrimEx Run Plan
    • CDC is expected to be turned on about 9.5 days from now (n.b. that schedule has since changed)
    • Expect 16 shifts with beam on (4 days)
    • One of us will need to sit in as additional remote shifter to handle determining the HV setting and implementing it between runs
    • We will need to set up a schedule for which of us will be online
      • Thomas, Naomi, Torri, and David will likely be the ones implementing this.
      • We will set up internal training
  • Time to Distance Calibration
    • No progress last week
  • CLAS12 (Torri)
    • Trying to get a good run list. Not clear how to obtain this
    • Able to produce Trees now
    • Setup a GitHub page listing projects
      • Need to add everyone's Github account to it


Action Items

  1. Read the Gain Correction Factor Status Document (Everyone)
  2. Check for "good" runs in the first 3 files (0,1,2) of the 2018 data (Nikhil, Torri)
  3. Schedule for who from our group will be on shift to change HV settings
  4. Add everyone's Github account to the Github AIEC Projects page (Torri)
Retrieved from "https://wiki.jlab.org/epsciwiki/index.php?title=AIEC_Weekly_Meeting_Sep._23,_2021&oldid=897"