[Halld-offline] Software Meeting Minutes, January 8, 2019

Mark Ito marki at jlab.org
Wed Jan 9 21:08:46 EST 2019


Folks,

Please find the minutes here 
<https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_January_8,_2019#Minutes> 
and below.

   -- Mark

_________________________________________________________


    Minutes, GlueX Software Meeting, January 8, 2019

Present:

  * *CMU: * Naomi Jarvis
  * *JLab: * Thomas Britton, Ashley Ernst, Mark Ito (chair), Richard
    Jones, Justin Stevens, Simon Taylor

There is a recording of this meeting <https://bluejeans.com/s/dIYPe/> on 
the BlueJeans site. Use your JLab credentials to access it.


      Announcements

 1. *MCwrapper changes (not a release)*. Thomas reported on recent changes.
      * *MCwrapper submission revamp
        <https://halldweb.jlab.org/gluex_sim/SubmitSim.html>*.
          o The CPP experiment has been added to the submission page as
            an entity separate from GlueX. Other experiments can be
            added similarly.
          o The "confirm" button will check for similar MC runs and
            notify the user if they exist. This should lessen
            duplication of effort.
      * *Self-Service error corrections
        <https://halldweb.jlab.org/gluex_sim/SubmitSim.html?prefill=254&mod=1>*.

          o If test of submission fails, form is re-presented to user
            for corrections. Corrections are only allowed if coming from
            the original user. This feature has been used already by
            Peter Pauli.
 2. *hdds updates to eliminate overlaps*. Richard has addressed the
    geometry overlaps as reported by Maria Patsyuk
    <https://github.com/JeffersonLab/HDGeant4/issues/60>.
      * There were 98 occurrences of overlap, many of them of the
        "rounding" variety (insufficient precision in the geometry
        parameters).
      * The most serious overlap was one between the BCAL and FDC. A
        tilt was added to the BCAL to make it consistent with survey
        data. The axis of rotation turned out to be at the upstream end
        of the BCAL, causing an overlap with the FDC at the downstream
        end. Richard changed the rotation to be (effectively) around the
        center of the BCAL, maintaining the amount of tilt.
      * Action Items:
         1. Richard will submit a pull request to the hdds repository.
         2. He will also consult with Sean Dobbs about how to include
            this change into the CCDB-resident geometry files.


      Review of minutes from the December 11 meeting

We went over the minutes 
<https://halldweb.jlab.org/wiki/index.php/GlueX_Software_Meeting,_December_11,_2018#Minutes>. 


  * *Crashing Monitor Launches?*. The cause of the crashes in monitoring
    launches was traced to a Start Counter plugin by Alex Austregesilo.
    It was not related to the reconstruction code itself.
  * *Record of per file event ranges*. We need to ask if progress has
    been made.


      Report from the December 18 HDGeant4 Meeting

We went over these minutes 
<https://halldweb.jlab.org/wiki/index.php/HDGeant4_Meeting,_December_18,_2018#Minutes> 
as well.

Richard reported that has fixed the long-standing problem with missing 
hits along the track 
<https://github.com/JeffersonLab/HDGeant4/issues/66> in the FDC. There 
was a off-by-one error in the layer labeling. This caused layers to be 
rotated incorrectly in HDGeant4.


      Merging the DIRC branches

Justin led us through his email proposing a scheme for merging the DIRC 
branches 
<https://mailman.jlab.org/pipermail/halld-offline/2019-January/003469.html> 
onto the master branches. Please see the email for a nice description of 
the scheme, its features, and a comment on tests completed.

For HDGeant4 (hdg4), since the geometry is defined at run time using 
files from the CCDB, there is no ambiguity about whether the DIRC should 
be included or not. For hdgeant (hdg3) the decision is made at build 
time by pointing to an appropriate build of HDDS, one with or without 
the DIRC as appropriate. We discussed whether we want to even support 
hdg3 with the DIRC; if not we could define hdg3 as a DIRC-free program.

Richard proposed a mechanism where inclusion of the DIRC is determined 
by a CCDB-resident constant. All hdg3 builds going forward would include 
the DIRC, but during initialization, i. e., at run time, if the CCDB 
says there should not be a DIRC, the DIRC geometry will be replaced by 
air. Again, this would only be for hdg3. Richard volunteered to code the 
new initialization step; Justin volunteered to create the new item in 
the CCDB.

Justin mentioned that initially DIRC hits would be put into the REST 
format. This is in contrast to our usual practice of storing only 
reconstructed quantities. The intention is to do this only until the 
DIRC reconstruction code matures. For now having the hits in the REST 
events allows for efficient development of the reconstruction. Justin 
will look into how much this will cost in terms of event size.

No objections to the plan were voiced. Justin plans to submit the pull 
requests tomorrow (Wednesday).


      Developer-friendly, container-based builds

Mark filled in some details in his announcement 
<https://mailman.jlab.org/pipermail/halld-offline/2018-December/003465.html> 
of Oasis-resident builds that can be used for code development. Please 
see his slides 
<https://docs.google.com/presentation/d/1tFgT4Q3qWg72LycfC_72LCffta7KNvQTxHRwtga7qp0/edit?usp=sharing> 
for the details. They are also available as PDF from GlueX Doc 3855 
<https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=3855>.


      Debug and optimized builds of halld_recon and halld_sim

Mark gave further explanation of his announcement of build_scripts 1.44 
<https://mailman.jlab.org/pipermail/halld-offline/2019-January/003468.html>. 
The most significant change is the introduction of "debug levels"; new 
combinations of optimization levels and inclusion/exclusion of debugging 
symbols. See his slides 
<https://docs.google.com/presentation/d/1DpaLMUnviTgtJ_SRT6iZcaORcKeKNOdAxzic-LlFLPY/edit?usp=sharing> 
for the details. They are also available as PDF from GlueX Doc 3856 
<https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=3856>)

The idea is to (a) save disk space (b) tailor builds to the task (i. e., 
debugging, production) via additional choices of build parameters.


      Review of recent issues and pull requests

We decided to forego this section of the agenda.

Retrieved from 
"https://halldweb.jlab.org/wiki/index.php?title=GlueX_Software_Meeting,_January_8,_2019&oldid=90784"

  * This page was last modified on 9 January 2019, at 21:04.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-offline/attachments/20190109/8a25cc0f/attachment-0001.html>


More information about the Halld-offline mailing list