Difference between revisions of "2020-03-10"

From GlueXWiki
Jump to: navigation, search
(Agenda)
(Agenda)
 
(4 intermediate revisions by 3 users not shown)
Line 18: Line 18:
 
* Issues concerning running
 
* Issues concerning running
 
** Run coordinator report (Justin)
 
** Run coordinator report (Justin)
** Report concerning strategy for shifts and viruses [http://www.jlab.org/~zihlmann HallD Shift Operations] (Beni)
+
** Report concerning strategy for shifts and viruses [http://www.jlab.org/~zihlmann/halld_shift.pdf HallD Shift Operations] (Beni)
 
** Need for run coordinators
 
** Need for run coordinators
 
*** April 1 - April 8
 
*** April 1 - April 8
Line 32: Line 32:
 
*** any others?
 
*** any others?
 
* Report on PrimEx monitoring launch and REST production (Igal/Sasha/Sean) https://halldweb.jlab.org/wiki/index.php/RunPeriod-2019-01_Validation
 
* Report on PrimEx monitoring launch and REST production (Igal/Sasha/Sean) https://halldweb.jlab.org/wiki/index.php/RunPeriod-2019-01_Validation
* Cross section workfest (3/26-3/27):  guidance and preparation (Justin)
+
* Cross section workfest (3/26-3/27):  [https://halldweb.jlab.org/wiki-private/index.php/Spring_2020_Cross_Section_Workfest#Preparation guidance and preparation] (Justin)
 
* Status of GlueX NIM paper (Elton)
 
* Status of GlueX NIM paper (Elton)
 
* Report from the CB (Reinhard)
 
* Report from the CB (Reinhard)
Line 59: Line 59:
  
 
* Hardware Working Groups:
 
* Hardware Working Groups:
** Engineering Activities:  FCAL-II, CPP, other (Tim)
+
** Engineering Activities:  FCAL-II, CPP, other [https://halldweb.jlab.org/wiki/index.php/February_26,_2020_FCAL_2_Design_Meeting FCAL 2 February 26, 2020]
 +
*** [https://halldweb.jlab.org/wiki/index.php/February_27,_2020_CPP_Design_Meeting#Agenda CPP February 27, 2020] (Tim)
 
** Electronics and Firmware (Fernando)
 
** Electronics and Firmware (Fernando)
 
** Beamline Status [[BLTWG_Meeting_03/03/2020 | March 3, 2020]] (Richard)
 
** Beamline Status [[BLTWG_Meeting_03/03/2020 | March 3, 2020]] (Richard)

Latest revision as of 15:42, 10 March 2020

Meeting Coordinates

The meeting will be on Tuesday March 10, 2020 at 11:15am EDT. For those people at Jefferson Lab, the meeting will be in room F326.

Connecting

  1. To join via a Web Browser, go to the page [1] https://bluejeans.com/660743227.
  2. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 660743227.
  3. To join via phone, use one of the following numbers and the Conference ID: 660743227.
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560
  4. Upon connection all microphones are automatically muted. To unmute your mike on a Polycom or equivalent unit, enter *4. Unmuting on a computer is trivial as there is a microphone button than can be clicked.
  5. More information on connecting to bluejeans is available.

Agenda

  • Announcements
  • Issues concerning running
    • Run coordinator report (Justin)
    • Report concerning strategy for shifts and viruses HallD Shift Operations (Beni)
    • Need for run coordinators
      • April 1 - April 8
      • April 22 - April 29
  • Critical path issues for GlueX-II production
    • Understanding track extrapolation issues to DIRC (Simon/Justin)
    • Track reconstruction and covariance matrix determination; need help in examining high-level yields? (Sean)
    • Complete calibrations -- brief summary of outstanding items (Sean)
      • Tagger hodoscope timewalk
      • BCAL gains
      • FCAL timing
      • TOF time offsets
      • any others?
  • Report on PrimEx monitoring launch and REST production (Igal/Sasha/Sean) https://halldweb.jlab.org/wiki/index.php/RunPeriod-2019-01_Validation
  • Cross section workfest (3/26-3/27): guidance and preparation (Justin)
  • Status of GlueX NIM paper (Elton)
  • Report from the CB (Reinhard)
    • short-range correlation proposal and review
    • neutral pion polarizability proposal and review
    • physics coordinator election
  • Specific areas where specialized help is needed
    • resolving issues concerning MC generation on OSG; specifically, management of random trigger files (Sean)

Additional brief reports from working groups as needed