May 17, 2016, Analysis Working Group

From GlueXWiki
Jump to: navigation, search

Meeting Time and Place

The meeting will be on Tuesday May 17, 2016 at 1:30 pm EDT. For those people at Jefferson Lab, the meeting will be in room F326.

Meeting Connections

  1. To join via a Web Browser, go to the page [1] https://bluejeans.com/115815824.
  2. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 115815824.
  3. To join via phone, use one of the following numbers and the Conference ID: 115815824.
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560
  4. More information on connecting to bluejeans is available.

Agenda

  1. Discussion on the role of this working group
  2. REST Production Goals (est. start date June 1):
    • Provide REST data with sufficiency quality for early publications
    • Obtain information for analyses which requires access to the complete dataset of EVIO files:
      • Determination of efficiencies and resolutions for all detectors and reconstructed quantities
        • Example tracking efficiency and resolution study with Spring 2015 data (Paul) (Link)
        • Proposal for the required studies (Paul) (Link)
      • Determination of photon flux and polarization (most relevant data can be obtained from PS skims)
  3. Plugins to include in production run:
    • Required: janadot, danarest, monitoring_hists, track_skimmer (EventStore skims), trackeff_missing (tracking efficiency/resolution), other efficiency/resolution plugins
    • Photon beam diagnostics: polarization (TPOL), photon flux (PS), and live time (EPICS_dump). Some can run independently on PS skims
    • High-level calibration quality monitoring for detectors not covered in monitoring_hists (PS, TPOL, TAGH, TAGM)
  4. Spring 2016 Dataset Summary
  5. Spring 2016 Reconstruction Checklist
  6. More discussion:
    • Working group e-mail list?
    • etc.
  7. AOB

Minutes

  1. REST Production Goals (est. start date June 1):
    • Provide REST data with sufficiency quality for early publications
      • The software and CCDB conditions used in the offline monitoring productions are currently stored in a DB, but should be available on the web for future productions so users can reproduce those conditions in simulation, etc.
      • It was requested to include the e+/e- mass hypotheses in the next REST production
      • As a note for planning the offline monitoring ver05 REST files were ~3 TB total size, and the rough estimate for the full REST data sample would be 25-30 TB.
    • Obtain information for analyses which requires access to the complete dataset of EVIO files:
      • Determination of efficiencies and resolutions for all detectors and reconstructed quantities
        • We went through Paul's example study of tracking efficiency/resolution and discussed the proposal for a complete set of studies for all the different detectors
        • There was agreement that we need to prioritize what studies should to be done for this first production based on the physics measurements we're focusing on initially, ie. beam asymmetries
        • The detector groups should discuss what is reasonable to have ready before the production and communicate with Paul/Justin to prioritize
        • For the studies which don't require the full statistics of the dataset we could run the plugins to characterize the low level detector response in a separate pass over a limited set of the data or provide a limited skim of the data for these studies
      • Determination of photon flux and polarization (most relevant data can be obtained from PS skims)
        • Skims of all the PS triggered data are being produced with the calibration trains for the full dataset, and can be used for the photon flux and TPOL measurements
  2. Plugins to include in production run:
    • We didn't discuss this list in any detail, but noted that the REST production will not include individual user analysis plugins (eg. writing TTrees). Instead this group will organize "analysis launches" which will include analysis plugins from users and process the REST data from the official production.
  3. Spring 2016 Dataset Summary
    • The figure on this page (linked immediately above) attempts to summarize the various conditions that were sampled over the course of the spring run period
    • Some additions suggested at the meeting and afterwards were: PARA/PERP, TPOL status, converter thickness, beam intensity, and trigger. Sasha will provide a list of significant changes to the trigger which we can include in this summary.
    • The data was divided into 4 blocks with the goal of identifying run ranges that we should focus on in the initial analyses, where the conditions were fairly stable.
    • We decided to make the block of runs 11347-11555 the first priority for production, so detector groups should focus on the calibration of that range of runs for the June 1 deadline.
      • After the meeting Alex Barnes reminded us that the improved TAGM gains were not in place until 11572, so the TAGM performance may not be optimal in these runs.
  4. Spring 2016 Reconstruction Checklist
    • Many of the subjects on the checklist are calibration related, so will be discussed further at the calibration meeting tomorrow.
  5. More discussion:
    • We decided to use the physics mailing list for general e-mail discussion in the working group. For the next few weeks e-mail announcements will be sent to the GlueX collaboration mailing list as well for general reminders.
    • Matt noted that the physics mailing list is an open list, and at some point in the future we'll need a private list for discussing internal results prior to conferences and publications.
  6. AOB
    • Our next meeting will be Tuesday May 24 @ 1:30 pm.
Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=May_17,_2016,_Analysis_Working_Group&oldid=80572"