It still gives me the same error. Did something change with run number 1000000? Command I use is here:
java -jar <jar file> -i /nfs/slac/g/hps3/data/Layer0Studies/slic/wab-beam-tri-5mrad/wabv3SF-egsv5_5mrad-triv2MG5-g4v1_HPS-Proposal2017-L0-v3-1pt05-fieldmap_900.slcio -d HPS-Proposal2017-L0-v3-1pt05-fieldmap -R 1000000 -DoutputFile=test_readout -r /org/hps/steering/readout/EngineeringRun2015TrigPairs1_Pass2.lcsim
Thanks.
Matt Solt
________________________________________
From: McCormick, Jeremy I.
Sent: Friday, September 15, 2017 12:55 PM
To: Solt, Matthew Reagan; Alessandra Filippi; Nathan Baltzell
Cc: hps-software
Subject: Re: ConditionsDiriver not found by readout/recon of mc data with Layer0
ConditionsDriver was removed. Use the run and detector arguments to the command line tools (covered in the doc) .
https://confluence.slac.stanford.edu/display/hpsg/Running+HPS+Java
________________________________________
From: [log in to unmask] <[log in to unmask]> on behalf of Solt, Matthew Reagan <[log in to unmask]>
Sent: Friday, September 15, 2017 11:25:30 AM
To: Alessandra Filippi; Nathan Baltzell
Cc: hps-software
Subject: Re: ConditionsDiriver not found by readout/recon of mc data with Layer0
Hi Alessandra,
I am getting the same errors, both with old and new steering files. I haven't run L0 files in a while, so I hadn't run into this before.
I don't know what exactly was done to the conditions database, perhaps Jeremy can comment. But, it is clearly not picking up the conditions for L0 (I got this same error back in January before we set the run number 1000000 specifically for L0 detectors). We need to somehow make sure it picks up the correct conditions for L0 detector, or it will crash in this place every time due to the extra sensors. I don't know the conditions system well enough yet to look into detail.
Also, make sure the run number is 1000000 (I mess this up all the time), and that your readout steering file is "PhysicsRun2016TrigPairs1.lcsim" when looking at 2.3 GeV files (not responsible for the errors, just the trigger cuts in the readout are different).
Matt Solt
________________________________________
From: [log in to unmask] <[log in to unmask]> on behalf of Alessandra Filippi <[log in to unmask]>
Sent: Friday, September 15, 2017 7:12 AM
To: Nathan Baltzell
Cc: hps-software
Subject: Re: ConditionsDiriver not found by readout/recon of mc data with Layer0
sorry, me again...
is -Drun=10000000 still good to process a Layer0 geometry? Does the new
condition db, wherever it is, know about this?
well, the answer is no because it does not work: in spite of
[CONFIG] [org.lcsim.job] defined detector = HPS-Proposal2017-L0-v3-2pt3-fieldmap
[CONFIG] [org.lcsim.job] run = 1000000
[CONFIG] [org.lcsim.job] defined run = 1000000
[CONFIG] [org.lcsim.job] isMC = true
[...]
but then it tells me:
[...]
[CONFIG] [org.hps.conditions.database] Initializing conditions system with
detector 'HPS-Proposal2017-L0-v3-2pt3-fieldmap' and run 0
[...]
and the additional layers are not recognised:
java.lang.RuntimeException:
Failed to find DAQ pair for sensor: module_L1b_halfmodule_axial_slot_sensor0
[...]
so, what should I do now? Which is the correct nun number or how should I
pass it to hps-java?
I am using as steering file EngineeringRun2015TrigPairs1_Pass2.lcsim as
given in hps-java bundle.
Thanks, cheers
Alessandra
On Fri, 15 Sep 2017, Nathan Baltzell wrote:
> Hi Alessandra,
>
> I think ConditionsDriver was intentionally deleted and removed from all steering files. Is your steering file in hps-java, or a local (and now out of date) version?
>
> -Nathan
>
> llama> cd $HPS_TRUNK/steering-files/src/main/resources/org/hps/steering/readout
> llama> git log .
> commit 91882d76e5dca8d12e096656255d27b1ed5d7f93
> Author: JeremyMcCormick <[log in to unmask]>
> Date: Mon Jul 31 20:20:58 2017 -0700
>
> remove ConditionsDriver from all steering files
>
>
>
>> On Sep 15, 2017, at 6:24 AM, Alessandra Filippi <[log in to unmask]> wrote:
>>
>> Hi all,
>> after a few weeks I'm trying to make the readout and reconstruct again some data I simulated with a new geometry including layer0 geometry, HPS-Proposal2017-L0-v3-2pt3-fieldmap. I made a fresh pull to update hps-java and lcsim, and I'm using the following command to get the readout:
>>
>>> java -jar hps-java-current-distribution.jar EngineeringRun2015TrigPairs1_Pass2.lcsim
>> -i HPS-Proposal2017-L0-v3-2pt3-fieldmap.slcio -DoutputFile=HPS-Proposal2017-L0-v3-2pt3-fieldmap_readout -Ddetector=HPS-Proposal2017-L0-v3-2pt3-fieldmap -Drun=100000 -DisMC=true
>>
>>
>> then I get this complaint:
>>
>> Exception in thread "main" java.lang.RuntimeException: The Driver class org.hps.conditions.ConditionsDriver was not found.
>> at org.lcsim.job.JobControlManager.setupDrivers(JobControlManager.java:1198)
>> at org.lcsim.job.JobControlManager.setup(JobControlManager.java:1059)
>> at org.lcsim.job.JobControlManager.setup(JobControlManager.java:1117)
>> at org.lcsim.job.JobControlManager.setup(JobControlManager.java:1084)
>> at org.lcsim.job.JobControlManager.parse(JobControlManager.java:671)
>> at org.hps.job.JobManager.parse(JobManager.java:68)
>> at org.hps.job.JobManager.main(JobManager.java:32)
>> Caused by: java.lang.ClassNotFoundException: org.hps.conditions.ConditionsDriver
>> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>> at org.lcsim.job.JobControlManager.setupDrivers(JobControlManager.java:1196)
>> ... 6 more
>>
>>
>> ... so it looks like ConditionsDriver cannot be found anywhere. Same if I run the reconstruction (on a readout file I was able to produce in august).
>> Where has this driver gone? What am I doing wrong now? Wrong run number again?
>>
>> Thanks for your help,
>> cheers
>> Alessandra
>>
>> ########################################################################
>> Use REPLY-ALL to reply to list
>>
>> To unsubscribe from the HPS-SOFTWARE list, click the following link:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__listserv.slac.stanford.edu_cgi-2Dbin_wa-3FSUBED1-3DHPS-2DSOFTWARE-26A-3D1&d=DwIBAg&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=SyXCERKmF6ZPnHcvjvj_i035JU5-CekNtcXyMlms6kc&m=EsywC-xygRPWHAXZ3voHh_RMzrCKaCHUPIQJqxyI7rg&s=FrdHsmazKMDOKsQrf_yNTd7aqtXRBtxRBUzABXBlRs4&e=
>
>
########################################################################
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
