Hmmm, missing ti_time_offsets table. If I’m looking correctly, looks like it’s only used by rundb/datacat stuff. And it doesn’t have any entries in the “conditions” table like normal conditions, but a separate entry for every run. Jeremy, do you know what this is?
> On May 9, 2019, at 08:31, Andrea Celentano <[log in to unmask]> wrote:
>
> Dear all,
> Nathan just took new data, with run number 9004
>
> You can find this at JLab: /work/hallb/hps/data/led/evio/
>
> The command I use is:
>
> java -cp /local/celentano/eclipse_workspace/hps/distribution/target/hps-distribution-4.4-SNAPSHOT-bin.jar org.hps.evio.EvioToLcio -d HPS-ECalCommissioning -r -x /org/hps/steering/monitoring/EcalLedSequenceStandalone.lcsim led_data/hpsecal_009004.evio.0000* -b -DoutputFile=009004.histo
>
>
> I get now a new error:
>
>
> Exception in thread "main" java.lang.RuntimeException: No TiTimeOffset condition exists for run 9004
> at org.hps.conditions.trigger.TiTimeOffsetConverter.getData(TiTimeOffsetConverter.java:24)
> at org.hps.conditions.trigger.TiTimeOffsetConverter.getData(TiTimeOffsetConverter.java:11)
> at org.lcsim.conditions.CachedConditionsImplementation.getCachedData(CachedConditionsImplementation.java:20)
> at org.hps.evio.LCSimEngRunEventBuilder.conditionsChanged(LCSimEngRunEventBuilder.java:104)
> at org.lcsim.conditions.ConditionsManagerImplementation.fireConditionsChanged(ConditionsManagerImplementation.java:122)
> at org.lcsim.conditions.ConditionsManagerImplementation.setConditionsReader(ConditionsManagerImplementation.java:69)
> at org.lcsim.conditions.ConditionsManagerImplementation.setDetector(ConditionsManagerImplementation.java:53)
> at org.hps.conditions.database.DatabaseConditionsManager.setDetector(DatabaseConditionsManager.java:801)
> at org.hps.evio.EvioToLcio.checkConditions(EvioToLcio.java:229)
> at org.hps.evio.EvioToLcio.bufferEvents(EvioToLcio.java:202)
> at org.hps.evio.EvioToLcio.run(EvioToLcio.java:514)
> at org.hps.evio.EvioToLcio.main(EvioToLcio.java:92)
>
> The error also appears If I use as detector: HPS-PhysicsRun2016-Pass2
>
> Thanks
>
> Andrea
>
> On 5/7/19 1:32 PM, Andrea Celentano wrote:
>> Hi,
>> I am ignoring the output redirecting to /dev/null. It seems the output data is correct - however, it looks like the code is extremely lower than how it was when I used it in 2016. Maybe related to this error?
>> I was not yet able to analyze the data of a full run due to this speed issue, I run it on a single evio file (and it took ~ 45 minutes!). I am running over the full evio fileset (6 files) of run 81 now, I’ll be able to report later on this (not today, probably).
>>
>> Andrea
>>
>>> On May 7, 2019, at 12:42, Maurik Holtrop <[log in to unmask]> wrote:
>>>
>>> Hi Andrea,
>>>
>>> If you ignore those errors, do you still get useful output?
>>> This is why I suggested to pipe all the error output to /dev/null
>>>
>>> Best,
>>> Maurik
>>>
>>> -----------------------------------------------
>>>
>>> On May 7, 2019, at 3:40 AM, Andrea Celentano <[log in to unmask]> wrote:
>>>
>>>> Dear all,
>>>> If I set run 8000, errors I reported before are no longer present. During reconstruction, I get an error reported once per event:
>>>>
>>>>
>>>> 019-05-07 09:39:41 [SEVERE] org.hps.evio.LCSimTestRunEventBuilder getTriggerData :: null
>>>> java.lang.reflect.InvocationTargetException
>>>> at sun.reflect.GeneratedConstructorAccessor19.newInstance(Unknown Source)
>>>> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>>>> at org.hps.evio.LCSimTestRunEventBuilder.getTriggerData(LCSimTestRunEventBuilder.java:173)
>>>> at org.hps.evio.LCSimTestRunEventBuilder.getEventData(LCSimTestRunEventBuilder.java:115)
>>>> at org.hps.evio.LCSimEngRunEventBuilder.makeLCSimEvent(LCSimEngRunEventBuilder.java:143)
>>>> at org.hps.evio.EvioToLcio.run(EvioToLcio.java:608)
>>>> at org.hps.evio.EvioToLcio.main(EvioToLcio.java:92)
>>>> Caused by: java.lang.RuntimeException: Invalid Data Length: 6
>>>> at org.hps.record.triggerbank.HeadBankData.decodeData(HeadBankData.java:76)
>>>> at org.hps.record.triggerbank.HeadBankData.<init>(HeadBankData.java:23)
>>>> ... 8 more
>>>>
>>>> This is not causing the reconstruction to crash, however.
>>>>
>>>>
>>>> Talk to you about this at today's meeting.
>>>>
>>>> Bests,
>>>> Andrea
>>>>
>>>>
>>>> On 5/6/19 11:30 PM, maurik wrote:
>>>>> Hello Andrea,
>>>>>
>>>>> There seem to be multiple issues with running this analysis.
>>>>>
>>>>> The first one is that there are errors in the conditions manager that are triggered when you have a run number that is in the “test run range”. I don’t know exactly where the bounds are, but 81 and 82 are definitely in the test run range. You can specify a higher run number on the command line with say, -R 8000, and now the conditions database is happy.
>>>>>
>>>>> When I do that, the code gets a lot further but start spitting out an insane number of errors that getTriggerData() is null.
>>>>>
>>>>> What works temporarily is:
>>>>>
>>>>> java -cp $HPSJAVAdev org.hps.evio.EvioToLcio -d HPS-PhysicsRun2016-Pass2 -r -x /org/hps/steering/monitoring/EcalLedSequenceStandalone.lcsim hpsecal_000081.evio.00000 -b -DoutputFile=000081.histo -R 8000 2> /dev/null
>>>>>
>>>>> I have this running now and will see if I get a histogram file at the end. :-)
>>>>>
>>>>> I will look into what is happening at the getTriggerData() part.
>>>>>
>>>>>
>>>>> Best,
>>>>> Maurik
>>>>>
>>>>>> On May 6, 2019, at 4:50 PM, Andrea Celentano <[log in to unmask]> wrote:
>>>>>>
>>>>>> Hi Maurik,
>>>>>> EVIO files from runs n. 81 and 82 at JLab are located here:
>>>>>>
>>>>>> /work/hallb/hps/data/cosmic/evio
>>>>>>
>>>>>> Bests,
>>>>>> Andrea
>>>>>>> On May 6, 2019, at 22:37, maurik <[log in to unmask]> wrote:
>>>>>>>
>>>>>>> Hello Andrea,
>>>>>>>
>>>>>>> To be able to do any testing of this it would be very useful to know where the data file resides. Could you please email us the path of the two evio files?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Maurik
>>>>>>>
>>>>>>>
>>>>>>>> On May 6, 2019, at 12:16 PM, Andrea Celentano <[log in to unmask]> wrote:
>>>>>>>>
>>>>>>>> Dear all,
>>>>>>>> I'd like to use HPS-java to analyze LED data just taken. The two run numbers are: 81 and 82.
>>>>>>>>
>>>>>>>> In the past (2016 run), the command I used to perform this task was:
>>>>>>>>
>>>>>>>> java -cp /path/to/hps-distribution-VERSION-SNAPSHOT-bin.jar org.hps.evio.EvioToLcio -d DETECTOR_NAME -r -x /org/hps/steering/monitoring/EcalLedSequenceStandalone.lcsim led_data/hpsecal_000081.evio.00000 -b -DoutputFile=000081.histo
>>>>>>>>
>>>>>>>> * As DETECTOR_NAME, I always used HPS-ECalCommissioning.
>>>>>>>>
>>>>>>>> I get the following condition-system related errors.
>>>>>>>>
>>>>>>>> 1) If I use hps-distribution-4.1-SNAPSHOT-bin.jar, the error is:
>>>>>>>>
>>>>>>>> [...]
>>>>>>>> 2019-05-06 18:12:36 [CONFIG] org.hps.conditions.database.DatabaseConditionsManager setDetector :: Initializing conditions system with detector 'HPS-ECalCommissioning' and run 81
>>>>>>>> 2019-05-06 18:12:36 [INFO] org.hps.conditions.database.DatabaseConditionsManager openConnection :: Opening connection ...
>>>>>>>> connection: jdbc:mysql://hpsdb.jlab.org:3306/
>>>>>>>> host: hpsdb.jlab.org
>>>>>>>> port: 3306
>>>>>>>> user: hpsuser
>>>>>>>> database: hps_conditions
>>>>>>>> [...]
>>>>>>>> 2019-05-06 18:12:44 [INFO] org.hps.detector.svt.SvtDetectorSetup loadTestRun :: loading Test Run SVT conditions onto subdetector Tracker
>>>>>>>> 2019-05-06 18:12:44 [INFO] org.hps.detector.svt.SvtDetectorSetup loadTestRun :: setting up 36 SVT sensors
>>>>>>>> 2019-05-06 18:12:44 [INFO] org.hps.detector.svt.SvtDetectorSetup loadTestRun :: channel map has 12800 entries
>>>>>>>> Exception in thread "main" java.lang.ClassCastException: org.lcsim.detector.tracker.silicon.HpsSiSensor cannot be cast to org.lcsim.detector.tracker.silicon.HpsTestRunSiSensor
>>>>>>>> at org.hps.detector.svt.SvtDetectorSetup.loadTestRun(SvtDetectorSetup.java:233)
>>>>>>>> at org.hps.detector.svt.SvtDetectorSetup.conditionsChanged(SvtDetectorSetup.java:95)
>>>>>>>> at org.lcsim.conditions.ConditionsManagerImplementation.fireConditionsChanged(ConditionsManagerImplementation.java:122)
>>>>>>>> at org.lcsim.conditions.ConditionsManagerImplementation.setConditionsReader(ConditionsManagerImplementation.java:69)
>>>>>>>> at org.lcsim.conditions.ConditionsManagerImplementation.setDetector(ConditionsManagerImplementation.java:53)
>>>>>>>> at org.hps.conditions.database.DatabaseConditionsManager.setDetector(DatabaseConditionsManager.java:712)
>>>>>>>> at org.hps.evio.EvioToLcio.checkConditions(EvioToLcio.java:229)
>>>>>>>> at org.hps.evio.EvioToLcio.bufferEvents(EvioToLcio.java:202)
>>>>>>>> at org.hps.evio.EvioToLcio.run(EvioToLcio.java:514)
>>>>>>>> at org.hps.evio.EvioToLcio.main(EvioToLcio.java:92)
>>>>>>>>
>>>>>>>>
>>>>>>>> 2) If I use hps-distribution-4.4-SNAPSHOT-bin.jar, the error is:
>>>>>>>>
>>>>>>>> [...]
>>>>>>>> 2019-05-06 18:03:29 [CONFIG] org.hps.conditions.database.DatabaseConditionsManager setDetector :: Initializing conditions system with detector 'HPS-ECalCommissioning' and run 81
>>>>>>>> Exception in thread "main" java.lang.NullPointerException
>>>>>>>> at org.lcsim.conditions.ConditionsManagerImplementation.registerConditionsConverter(ConditionsManagerImplementation.java:78)
>>>>>>>> at org.hps.conditions.database.DatabaseConditionsManager.registerConverters(DatabaseConditionsManager.java:748)
>>>>>>>> at org.hps.conditions.database.DatabaseConditionsManager.setDetector(DatabaseConditionsManager.java:791)
>>>>>>>> at org.hps.evio.EvioToLcio.checkConditions(EvioToLcio.java:229)
>>>>>>>> at org.hps.evio.EvioToLcio.bufferEvents(EvioToLcio.java:202)
>>>>>>>> at org.hps.evio.EvioToLcio.run(EvioToLcio.java:514)
>>>>>>>> at org.hps.evio.EvioToLcio.main(EvioToLcio.java:92)
>>>>>>>>
>>>>>>>> I also tried to change the detector to the one used in 2016 pass-0 (HPS-PhysicsRun2016-Nominal-v4-4-fieldmap), I get same errors as before.
>>>>>>>>
>>>>>>>> Thanks in advance,
>>>>>>>> Bests,
>>>>>>>> Andrea
>>>>>>>>
>>>>>>>> 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
>>>>>>
>>>>>
>>>>
>>>>
>>>> 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
>
########################################################################
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
|
