Difference between revisions of "To Do List, Assignments"

From HallCWiki
Jump to navigationJump to search
 
(One intermediate revision by the same user not shown)
Line 18: Line 18:
 
*** '''Production Run Plan''' - '''Simona''' (with students Deb, Lauren)
 
*** '''Production Run Plan''' - '''Simona''' (with students Deb, Lauren)
 
*** '''Most of the following are done, need to post to wiki'''
 
*** '''Most of the following are done, need to post to wiki'''
***** Choice of kinematics
+
***** Choice of kinematics - done
***** Radiative corrections calculation
+
***** Radiative corrections calculation - working on it
***** Charge-symmetric background calculation
+
***** Charge-symmetric background calculation - done
***** Pion rates calculation
+
***** Pion rates calculation - done
***** Estimation of detector rates
+
***** Estimation of detector rates -  done
***** Summary of trigger setup: trigger configuration, thresholds for various detectors
+
***** Tentative Trigger rates - done
***** Trigger rates
+
***** Order of kinematic production running - done
***** Order of kinematic production running
+
***** Coordinate with Dave Gaskell for combined E12-10-002/E12-10-008 running -  ongoing
***** Coordinate with Dave Gaskell for combined E12-10-002/E12-10-008 running
 
  
  
Line 44: Line 43:
  
 
*** '''Online analysis coordination''' - '''Simona''', with students: Deb (HU), Kayla (U. of Tennessee), Lauren (W&M)
 
*** '''Online analysis coordination''' - '''Simona''', with students: Deb (HU), Kayla (U. of Tennessee), Lauren (W&M)
*** '''This is the Summer project I chose for Lauren Liegey (W&M graduate student); she will spend 2 months at JLab working with me on this (she starts on 05/23/16) and my hope is that she will join Deb as a Ph.D. student on F2'''
+
*** '''This is the Summer project I chose for Lauren Liegey (W&M graduate student); she will spend 2 months at JLab working with me on this (she starts on 05/23/16) '''
  
 
**** Codes to monitor quality of data online: check deadtimes, efficiencies and quality of calibrations  
 
**** Codes to monitor quality of data online: check deadtimes, efficiencies and quality of calibrations  

Latest revision as of 10:38, 23 May 2016

This page is maintained by Simona Malace; send e-mails to simona@jlab.org for comments, questions..

  • Spokespeople for E12-10-002


    • Simona Malace - spokesperson, contact
    • Eric Christy - spokesperson
    • Thia Keppel - spokesperson
    • Ioana Niculescu - spokesperson


  • To Do List/Assignments


    • 'In preparation for running:'


      • Production Run Plan - Simona (with students Deb, Lauren)
      • Most of the following are done, need to post to wiki
          • Choice of kinematics - done
          • Radiative corrections calculation - working on it
          • Charge-symmetric background calculation - done
          • Pion rates calculation - done
          • Estimation of detector rates - done
          • Tentative Trigger rates - done
          • Order of kinematic production running - done
          • Coordinate with Dave Gaskell for combined E12-10-002/E12-10-008 running - ongoing


      • Non-production run plan - Eric (with Deb)
          • Elastics
          • BCM calibrations
          • Luminosity scans
          • Beam position on target
          • Rate dependence of tracking
          • Optics and pointing checks
          • Trigger checkout/optimization
          • External Rad. Corr. checks
          • What else?


      • Online analysis coordination - Simona, with students: Deb (HU), Kayla (U. of Tennessee), Lauren (W&M)
      • This is the Summer project I chose for Lauren Liegey (W&M graduate student); she will spend 2 months at JLab working with me on this (she starts on 05/23/16)
        • Codes to monitor quality of data online: check deadtimes, efficiencies and quality of calibrations
          • Simona already has these in fortran/kumac; with Lauren will convert to C
        • Hcana working and ready for online replay
          • Simona ran the hcana on few of the Jan05 runs, with Lauren will do some higher level analysis to make sure we get all we need from the analyzer
        • Cross section code ready for online cross sections extraction
          • Will use the Rosen07 framework, Simona is already running this for Rosen07


      • Online analysis coordination - Eric (Ioana ?)
        • Calibrations codes ready - in C; the colorimeter calibration code is already written; need the rest and also we need to post how to's and why's on the wiki
        • Use MC to produce acceptance corrections at the kinematics of E12-10-002
        • Data - MC comparison codes


      • Items needed for efficient running - All
        • Shift checklist: create/post on wiki - Ioana?
        • Run sheets: create/post on wiki - Ioana?
        • Post production run plan on wiki - Simona
        • Post non-production run plan on wiki - Eric
        • Post on wiki procedures/how to's (+ most common problems and how to solve them) for:
          • HV operation - Simona
          • Beam restoration: BeO, harp scan, C-hole run, bull's eye scan etc. - Eric
          • CODA running - Eric, Ioana ?
          • Change of spectrometers momenta - Ioana?
          • Change of spectrometers angle - Ioana?
          • Online histograms monitoring - Simona


    • 'While running:'


      • Make sure shifts are staffed - All
      • Make sure we have run coordinators - All
      • One spokesperson (at least) should be in the counting house most of the time to follow progress of running or fill in shifts, if needed - Eric, Simona, Ioana (we rotate)
      • Make sure the online analysis progresses so we can make decisions on the fly about changes in the run plan - Simona (and all)


    • 'After running:'


      • Offline analysis coordination: includes organizing/chairing weekly meetings, establishing analysis task and timeline, making sure analysis progresses according to the plan and ensuring that the analysis is properly documented - Simona (primary), Eric (back-up)
      • Organizing Collaboration meetings (at JLab) which involve spokespeople, students from the other commissioning experiments (probably one a month in the beginning) - All, we rotate
      • Ensure maximum physics output from data- All