No, 'ecal_pulse_widths' is the only ECal conditions set that is identical between cases. All the other sets seem to be old (2014) for the current jar, and updated with notes for the July15 jar. Also, the 'runStart, runEnd' are both set to 0 for the current jar. July 15: name: ecal_channels runStart: 2000 runEnd: 999999 tableName: ecal_channels collectionId: 2 updated: 2015-05-04 16:26:12.0 created: 2015-03-05 18:02:56.0 tag: online createdBy: baltzell notes: standard ECAL channel map 2017-09-28 13:15:22 [INFO] org.hps.conditions.database.AbstractConditionsObjectConverter getData :: loading conditions set... id: 2388 name: ecal_gains runStart: 7000 runEnd: 9999 tableName: ecal_gains collectionId: 2976 updated: 2016-11-01 14:43:58.0 created: 2016-11-01 14:43:58.0 tag: null createdBy: holly notes: adjusted single channel gain which was very low for testing 2017-09-28 13:15:22 [INFO] org.hps.conditions.database.AbstractConditionsObjectConverter getData :: loading conditions set... id: 1354 name: ecal_calibrations runStart: 7350 runEnd: 99999 tableName: ecal_calibrations collectionId: 1970 updated: 2016-02-21 11:03:28.0 created: 2016-02-21 11:03:27.0 tag: null createdBy: baltzell notes: 200nA peds, DAC3280, nosplitter 2017-09-28 13:15:22 [INFO] org.hps.conditions.database.AbstractConditionsObjectConverter getData :: loading conditions set... id: 1424 name: ecal_time_shifts runStart: 7000 runEnd: 99999 tableName: ecal_time_shifts collectionId: 2018 updated: 2016-03-21 10:47:10.0 created: 2016-03-21 10:47:09.0 tag: null createdBy: holly notes: time offsets corrected for cable swap Current: [INFO] [org.hps.conditions.database] loading conditions set... id: 32 name: ecal_channels runStart: 0 runEnd: 0 tableName: ecal_channels collectionId: 1 updated: 2014-10-29 00:46:35.0 created: 2014-03-18 16:56:24.0 tag: dev createdBy: jeremym notes: null [INFO] [org.hps.conditions.database] loading conditions set... id: 2 name: ecal_gains runStart: 0 runEnd: 0 tableName: ecal_gains collectionId: 1 updated: 2014-10-29 00:46:35.0 created: 2013-09-24 16:48:39.0 tag: dev createdBy: jeremym notes: null [INFO] [org.hps.conditions.database] loading conditions set... id: 4 name: ecal_calibrations runStart: 0 runEnd: 0 tableName: ecal_calibrations collectionId: 1 updated: 2014-10-29 00:46:35.0 created: 2013-09-30 17:25:21.0 tag: dev createdBy: jeremym notes: null [INFO] [org.hps.conditions.database] loading conditions set... id: 33 name: ecal_time_shifts runStart: 0 runEnd: 0 tableName: ecal_time_shifts collectionId: 1 updated: 2014-10-29 00:46:35.0 created: 2014-04-02 14:39:20.0 tag: dev createdBy: jeremym notes: null ________________________________ From: Nathan Baltzell <[log in to unmask]> Sent: Thursday, September 28, 2017 7:20:35 AM To: Bradley T Yale Cc: HPS-SOFTWARE; Mathew Graham; Norman A. Graf Subject: Re: Very few events being readout with current jar Is the ecal conditions part of the log messages identical for the two cases? > On Sep 28, 2017, at 6:15 AM, Bradley T Yale <[log in to unmask]> wrote: > > > When doing 2016 recon with a current jar, very few events are getting written. At first I thought it was from applying a beam position offset when making zero beamwidth events, or something specific to the iss154 branch. > > However, it happens during readout, and also with a current master branch. > This is a comparison of readout from around the last official release (which I have been using for production) and a current trunk: > > July 18 readout: > > Trigger Processing Results > Single-Cluster Cuts > Total Clusters Processed :: 4692 > Passed Seed Energy Cut :: 4692 > Passed Hit Count Cut :: 4295 > Passed Total Energy Cut :: 4243 > > Cluster Pair Cuts > Total Pairs Processed :: 1727 > Passed Energy Sum Cut :: 1683 > Passed Energy Difference Cut :: 1679 > Passed Energy Slope Cut :: 1622 > Passed Coplanarity Cut :: 1278 > > Trigger Count :: 1278 > > > The same events with an updated master: > > Trigger Processing Results > Single-Cluster Cuts > Total Clusters Processed :: 4289 > Passed Seed Energy Cut :: 4289 > Passed Hit Count Cut :: 1021 > Passed Total Energy Cut :: 1017 > > Cluster Pair Cuts > Total Pairs Processed :: 107 > Passed Energy Sum Cut :: 107 > Passed Energy Difference Cut :: 107 > Passed Energy Slope Cut :: 106 > Passed Coplanarity Cut :: 79 > > Trigger Count :: 79 > > The only difference in the steering files is the absence of the ConditionsDriver in the updated one. Does anyone know what change could be causing this? It looks like more events are failing the cluster hit count cut. Is this expected behavior? > > -Bradley > > > Use REPLY-ALL to reply to list > To unsubscribe from the HPS-SOFTWARE list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1