LISTSERV 16.5 - HPS-SOFTWARE Archives

Using an updated trunk, the Proposal2017 detectors seem to be giving a conditions-related error during recon:

java.lang.RuntimeException: No conditions were found with key: beam_energies
        at org.hps.conditions.database.AbstractConditionsObjectConverter.getData(AbstractConditionsObjectConverter.java:101)
        at org.lcsim.conditions.CachedConditionsImplementation.getCachedData(CachedConditionsImplementation.java:20)
        at org.hps.recon.particle.ReconParticleDriver.detectorChanged(ReconParticleDriver.java:366)
        at org.lcsim.util.Driver.detectorChanged(Driver.java:170)
        at org.lcsim.util.DriverAdapter.detectorChanged(DriverAdapter.java:86)
        at org.lcsim.util.DriverAdapter.recordSupplied(DriverAdapter.java:72)
        at org.freehep.record.loop.DefaultRecordLoop.consumeRecord(DefaultRecordLoop.java:832)
        at org.freehep.record.loop.DefaultRecordLoop.loop(DefaultRecordLoop.java:668)
        at org.freehep.record.loop.DefaultRecordLoop.execute(DefaultRecordLoop.java:566)
        at org.lcsim.util.loop.LCSimLoop.loop(LCSimLoop.java:152)
        at org.lcsim.job.JobControlManager.run(JobControlManager.java:949)
        at org.hps.job.JobManager.main(JobManager.java:33)

Specifically, the "HPS-Proposal2017-Nominal-v2-6pt6-fieldmap" detector was used with run 1000000.

Strangely, the readout works fine with the same detector and run.

I have seen this error before in standard recon, but it has gone away with recent updates (at least since Nov17) and the other detector geometries work using the same jar.

Does anyone know if the conditions for run 1000000, which affects L0 detector geometries, would have missed any recent fixes related to recon?

-Bradley