LISTSERV 16.5 - HPS-SOFTWARE Archives

I got this error:

Exception in thread "main" org.lcsim.util.xml.ElementFactory$ElementCreationException: Could not create element: class org.lcsim.geometry.compact.VisAttributes

Is that the same error you had?

From: [log in to unmask] <[log in to unmask]> on behalf of Omar Moreno <[log in to unmask]>
Sent: Thursday, October 27, 2016 9:18:37 PM
To: Bradley T Yale
Cc: Omar Moreno; Holly Vance
Subject: Re: svt geo

The only difference between the 4.4 and v5-0 geometries are the global millipede constants. It should be fine copying over those constants to the 1.5 mm detector. The other change, which corrects the carbon fiber, is done at the converter level so you will pick that up automatically.

I changed the support tilt angles in the compact.xml of the HPS-EngRun2015-1_5mm-v5-0-fieldmap. Try generating an lcdd using the updated compact file

(i tried but got a weird error)

and check if this fixes things.

On Thu, Oct 27, 2016 at 5:26 PM, Bradley T Yale <[log in to unmask]unh.edu> wrote:

Hi Omar,

Actually, I think I know what caused the problem.

The LCDD was made from a Nominal compact.xml by setting a 1.5mm run number, and so of course the new LCDD doesn't match it after reading in the new positions.

I think the only way to do this then is to manually implement all the Nominal-v5-0 fixes into the 1_5mm_v4-4 detector, unless there is a way to generate a new compact from an lcdd.

Do you happen to know if this can be done, or what these v5-0 changes are?

Otherwise, I could just do a diff and power through it.

From: [log in to unmask] <[log in to unmask]> on behalf of Omar Moreno <[log in to unmask]>
Sent: Thursday, October 27, 2016 8:05:32 PM
To: Bradley T Yale
Cc: Omar Moreno; Holly Vance
Subject: Re: svt geo

Bradley, Holly,

Do one of you have a script that runs through an LCIO file and makes plots of MC particle information? I want to check the position of the SimTrackerHits in the LCIO files. I can write something quick tomorrow, but I don't want to keep delaying you guys if you already have something we can use. I want to make sure the hits are in the correct position coming out of SLIC before we move on.

Best,

--Omar Moreno

On Tue, Oct 25, 2016 at 5:59 PM, Bradley T Yale <[log in to unmask]> wrote:

Sorry,

/cache/mss/hallb/hps/production/postTriSummitFixes/slic/ap/1pt05/50/apsignalv2_tc_epsilon-4_HPS-EngRun2015-1_5mm-v5-0-fieldmap_*.slcio

and similar for other masses.

From: [log in to unmask] <[log in to unmask]> on behalf of Omar Moreno <[log in to unmask]>
Sent: Tuesday, October 25, 2016 8:49:55 PM
To: Bradley T Yale
Cc: Holly Vance; Alessandra Filippi
Subject: Re: svt geo

Ok, can you point me to the LCIO files you are using as input.

On Oct 25, 2016 5:22 PM, "Bradley T Yale" <[log in to unmask]> wrote:

Thanks a lot for checking.

The readout never completed due to the error:

java.lang.RuntimeException: Distance is outside of sensor by more than 0.001. Distance = 0.4400545351566796. If this is an isolated event, then perhaps DISTANCE_ERROR_THRESHOLD must be increased in CDFSiSensorSim
        at org.lcsim.recon.tracking.digitization.sisim.CDFSiSensorSim.diffusionDistribution(CDFSiSensorSim.java:493)
        at org.lcsim.recon.tracking.digitization.sisim.CDFSiSensorSim.depositChargeOnSense(CDFSiSensorSim.java:251)
        at org.lcsim.recon.tracking.digitization.sisim.CDFSiSensorSim.computeElectrodeData(CDFSiSensorSim.java:114)
        at org.hps.readout.svt.SimpleSvtReadout.doSiSimulation(SimpleSvtReadout.java:268)
        at org.hps.readout.svt.SimpleSvtReadout.process(SimpleSvtReadout.java:177)
        at org.lcsim.util.Driver.doProcess(Driver.java:261)
        at org.lcsim.util.Driver.processChildren(Driver.java:271)
        at org.lcsim.util.Driver.process(Driver.java:187)
        at org.lcsim.util.DriverAdapter.recordSupplied(DriverAdapter.java:74)
        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:962)
        at org.hps.job.JobManager.main(JobManager.java:35)

Which started the discussion about a possible lcdd/compact mismatch.

The log files are

/volatile/hallb/hps/logDump/postTriSummitFixes/logs/readout/ap/1pt05/60/apsignalv2_HPS-EngRun2015-1_5mm-v5-0-fieldmap_3.10-20160813_pairs1_8.out

/volatile/hallb/hps/logDump/postTriSummitFixes/logs/readout/ap/1pt05/60/apsignalv2_HPS-EngRun2015-1_5mm-v5-0-fieldmap_3.10-20160813_pairs1_8.err

if you'd like to see if there are any other smoking guns.

From: [log in to unmask] <[log in to unmask]> on behalf of Omar Moreno <[log in to unmask]>
Sent: Tuesday, October 25, 2016 7:58:18 PM
To: Bradley T Yale
Cc: Omar Moreno; Alessandra Filippi; Holly Vance
Subject: Re: svt geo

Can you point me to a readout or recon file you generated? I'm looking at the positions, and they look OK.

On Tue, Oct 25, 2016 at 2:44 PM, Bradley T Yale <[log in to unmask]> wrote:

Run 5412.

Thanks for your help!

Sorry for the inconvenience.

From: [log in to unmask] <[log in to unmask]> on behalf of Omar Moreno <[log in to unmask]>
Sent: Tuesday, October 25, 2016 5:37:42 PM
To: Bradley T Yale
Cc: Omar Moreno; Alessandra Filippi; Holly Vance
Subject: Re: svt geo

Hi Bradley,

Sorry for the late reply. SvtDetectorSetup is used to load database conditions onto the sensors. This should also be used when running the readout simulation since we are using the SVT database conditions. I though I had put some debug in that driver that printed a description of each of the sensor objects but it no longer seems to be there.

There is a unit test associated with the driver that will print out detailed sensor info. Let me try running it in order to check kind of info it's getting. Can you remind me what run number you are using?

As for the global constants, they have not been calculated for the 1.5 mm detector and that's why they are set to zero. That should be fine for now.

On Tue, Oct 25, 2016 at 1:52 PM, Bradley T Yale <[log in to unmask]> wrote:

Hi, any update?
My previous question was basically what in the readout uses 'SvtDetectorSetup.java'.

There is also no debug option in

/u/group/hps/hps_soft/svn/hps-java-trunk/detector-model/src/main/java/org/hps/detector/svt/SvtDetectorSetup.java
if that's what you meant.

Comparing the lcdd/compacts, the only difference besides SVT positions is a mismatch in Millipede parameters,

probably from using a Nominal detector to make a 1.5mm one (if this matters):

<         
<         
<
<         
<         <constant name="dOmega_top" value="4e-06" />
<         <constant name="dLambda_top" value="0.000237368375145" />
<         <constant name="dPhi_top" value="0.000581084829307" />
<         <constant name="dD0_top" value="0.622163643926" />
<         <constant name="dZ0_top" value="-0.183211761644" />
<         <constant name="dOmega_bot" value="2.5e-05" />
<         <constant name="dLambda_bot" value="-0.000181541707685" />
<         <constant name="dPhi_bot" value="0.0171848562935" />
<         <constant name="dD0_bot" value="-5.87783635607" />
<         <constant name="dZ0_bot" value="0.116788238356" />
<
<         
<         
<
---
>         
>         <constant name="dOmega_top" value="0.0" />
>         <constant name="dLambda_top" value="0.0" />
>         <constant name="dPhi_top" value="0.0" />
>         <constant name="dD0_top" value="0.0" />
>         <constant name="dZ0_top" value="0.0" />
>         <constant name="dOmega_bot" value="0.0" />
>         <constant name="dLambda_bot" value="0.0" />
>         <constant name="dPhi_bot" value="0.0" />
>         <constant name="dD0_bot" value="0.0" />
>         <constant name="dZ0_bot" value="0.0" />

Alternatively, if I knew exactly what the difference between Nominal-v4-4 and Nominal-v5-0 was, I could just manually make a 1_5mm-v5-0 detector instead, but wasn't sure what all was involved in that.

From: Bradley T Yale
Sent: Friday, October 21, 2016 2:32:28 PM
To: Omar Moreno; Nathan Baltzell
Subject: Re: svt geo

I don't see any debug variable in

/u/group/hps/hps_soft/svn/hps-java-trunk/detector-model/src/main/java/org/hps/detector/svt/SvtDetectorSetup.java

If that's what you're talking about.

What in the steering file calls this? Is it set somewhere else?

From: [log in to unmask] <[log in to unmask]> on behalf of Omar Moreno <[log in to unmask]>
Sent: Friday, October 21, 2016 1:12:06 PM
To: Nathan Baltzell
Cc: Bradley T Yale
Subject: Re: svt geo

You need to enable the debug in SvtDetectorSetup. It should print out the sensor information and global position.

I can take a look at this further in the afternoon if it's not obvious.

On Oct 21, 2016 9:54 AM, "Nathan Baltzell" <[log in to unmask]> wrote:

Hi Omar,

You mentioned in yesterday’s meeting that Brad should have hps-java print the sensor positions (to compare with the lcdd file?). Is there an easy way to have it do that?

-Nathan