Stakeholder meeting notes – 2016/01/07

Stakeholder meeting notes – 2016/01/07 by Paul S Russo


Christopher Backhouse, Kurt Biery, Tim Doody, Lynn Garren,
Chris Jones, Tom Junk, Kyle Knoepfel, Rob Kutschke, Adam Lyon,
Brian Rebel, Paul Russo, Erica Snyder

Resolved Issues.

* 9830 Inherit sam metadata

Kyle Knoepfel described how to configure the new feature
from the command line and from fhicl files.

Marc Paterno indicated this will make it into the next release.

* 11340 MemoryTracker and TimeTracker file sqlite db crash


Marc Paterno pointed out that the fix required us to drop
database locking semantics, so no other process should
attempt to access the database while the art job is
in progress.

Marc Paterno enquired if this fix needs to be released as
soon as possible, and Herb Greenlee responded that
MemoryTracker and TimeTracker are useless until this is
released because the users must work on a nfs-mounted area in
the gpvm systems.  Lynn Garren indicated that the next build
for LArSoft is next week, so we could do it then.

Acturus Issues

The new flexible output file handling scheme discussions are
continuing and progress is being made.

* 11118 SelectEvents setting should respect filters by default

This is a request from Christopher Backhouse.

There was a long discussion about the pros and cons of
retaining the current behavior or of creating various kinds
of new behavior.

Marc Paterno asked Christopher Backhouse to write up a proposal
describing the new behavior he seeks.  Marc will then send that
proposal out to the stakeholders for vote.

* 11119 Allow an EDFilter to not produce all products if it’s
returning false

Marc Paterno says we will wait until #11118 is settled before
considering this one.

New Issues

Herb Greenlee asked if we can inherit sam data_stream, event
though it is set by RootOuput and not by the file catalog.
Kyle Knoepfel thinks this can be done.

Rob Kutschke notes a new problem with MemoryTracker or
TimeTracker in that certain information is printed as all
zeroes on output even though the data in the database is
correct.  He will create a new issue for this one.