LISTSERV 16.5 - HPS-SOFTWARE Archives

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:

[log in to unmask]" class=""> 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