GlueX Offline Meeting, June 10, 2015

From GlueXWiki
Revision as of 10:15, 11 June 2015 by Marki (Talk | contribs) (Offline Monitoring)

Jump to: navigation, search

GlueX Offline Software Meeting
Wednesday, May 27, 2015
1:30 pm EDT
JLab: CEBAF Center F326/327

Agenda

  1. Announcements
    1. New releases (Mark)
  2. Review of minutes from May 27 (all)
  3. Offline Monitoring (Kei et al.)
  4. Spring 2015 Commissioning Simulations (Sean)
  5. Git for GlueX? (Mark)
  6. Action Item Review

Communication Information

Remote Connection

Slides

Talks can be deposited in the directory /group/halld/www/halldweb/html/talks/2015 on the JLab CUE. This directory is accessible from the web at https://halldweb.jlab.org/talks/2015/ .

Minutes

Present:

  • CMU: Curtis Meyer
  • JLab: Mark Ito (chair), David Lawrence, Kei Moriya, Eric Pooser, Simon Taylor, Beni Zihlmann
  • NU: Sean Dobbs

Announcements

  • New Releases. Mark reminded us of the recent releases of HDDS and Sim-Recon as announced on the email list.
  • Jana 0.7.3: David has release a new version of Jana. Details will be coming out shortly but some highlights are:
    • event numbers changed from int32 to int64 to accommodate long runs
      • implementation accommodates 32-bit event numbers currently used by sim-recon
    • search for associated objects done recursively, the new default, depth of search can be limited by user
    • a list of all possible command line options can be generated

Spring 2015 Commissioning Simulations

Sean, Justin and Mark have put in a lot of adjustments to the conditions for the simulation, mainly to correct oversights. There is now a web page listing these conditions in addition to Sean's original wiki page.The system is ready to go, but we will wait a bit for new version of the CDC track finding software from Simon before we start. For now we plan not to use the new BCAL code from Tegan Beattie while it goes through validity checks by the Calorimenter Group.

Offline Monitoring

Kei summarized the state of the periodic offline monitoring jobs. See his slides for the complete story. He covered:

  • statistics for the current launch (last Friday)
  • a problem with the farm last weekend that delayed processing
  • the status of the start counter plug-in
  • deprecation of the 2-track skim
  • success/failure comparisons between the launches for the Spring data
  • a problem with FCAL ADC data
  • crashes due to an EVIO parse error
  • schedule for the next launch (June 19)

David will send out an email describing how to avoid the EVIO parse error.

Updating Information from the Analysis Workshop

Sean reminded us that part of the guidance for new collaborators, students in particular, is to review the analysis workshop we held in the Summer of 2013. He reported that the details of some of those activities have changed significantly since then, a cause of confusion. Since the concrete examples are stored in a virtual machine (which avoided the problem of everyone having to build their own system) they are not easy to update.

Eric told us that he has a wiki page with notes on the sessions and solutions to the problems. He will link it to the workshop wiki page.

We discussed ideas to address the problem but did not come to firm conclusions. We might want to hold another such workshop at some point.

Git for GlueX?

Mark gave us his take on issues surrounding a possible transition from Subversion to Git for a source code version control system. Please see his slides to see all the bullets (they are also on the DocDB). He discussed:

  • Conversion of reconstruction code (i. e., not everything under Subversion)
  • Multiple repositories in Git
  • Git commits: staging code before checking it in
  • Some common Git commands
  • Workflow models: how to organize the multiple repositories
  • Nice Git features
  • Extra steps in implementing and using Git
  • How to manage Conversion?
  • Why we should change

We did not make any decisions; in fact we did not event discuss a decision-making process. There are some things to work out before a change can be proposed, mainly how the group would transition to a new system without seriously impeding code development work.