 |
 |
SLIC saves the detector name in the LCIO file. All the HPS detector geometries are compiled into the hps-java JAR (in the detector-data module), so hps-java selects the geometry file with the same name. So if the LCDD file ued by SLIC doesn't match the detector with the same name in detector-data, you get problems. But it looks like your LCDD file is up to date. Luca Colaneri has been having a similar issue (same error, with current LCDD file). Let's take further discussion off the list until we figure out what's going on. Can you send me (or put on web space somewhere) your LCIO file? On Mon, 17 Feb 2014, Chad Civello wrote: > Attempting to run readout simulation again, it seems that in the command to > run HPS2014ReadoutNoPileup.lcsim I have not specified any LCDD detector > file to use. After pointing to the jar file and the steering file, it only > takes an input and an output name. Is there a way to tell the driver which > LCDD I am using? > On Feb 17, 2014 2:17 AM, "Sho Uemura" <[log in to unmask]> wrote: > >> Yes. Usual cause is running hps-java on an LCIO file that was created (in >> slic) using a different detector geometry - SLIC places hits where it >> thinks the detector volumes are, and then hps-java gets confused because >> the hits are outside where it thinks the detector volumes are. >> >> Can you send me the LCDD file you used? I guess the jar you used is the >> one at http://www.lcsim.org/maven/releases/org/hps/hps- >> distribution/3.0.0/hps-distribution-3.0.0-bin.jar? >> >> On Mon, 17 Feb 2014, Chad Civello wrote: >> >> Hi All, >>> >>> I am a student at the University of New Hampshire, attempting to continue >>> work on the true muonium section of the HPS experiment. I am looking to >>> run >>> true muonium data through the simulation software and then analyze the >>> reconstructed tracks. I have successfully used the software in the past, >>> but am currently running into an error with readout simulation that I have >>> never encountered. >>> >>> I am using hps-distribution-3.0.0-bin.jar, which I believe is the latest >>> stable release, with detector HPS-Proposal2014-v5-6pt6 and a true muonium >>> data file that was created by assuming the same decay properties as the >>> heavy photon, except with a mass of 211 MeV. Below is the command that I >>> am >>> using to run readout simulation and the error I receive. Is this error >>> familiar to anyone? Thank you for any help. >>> >>> Regards, >>> Chad Civello >>> >>> [ccivello@taro Out_files]$ java -jar hps-distribution.jar -r >>> /org/lcsim/hps/steering/readout/HPS2014ReadoutNoPileup.lcsim -i >>> TM_6786MeV_Fall2013_HPS-Proposal2014-v5-6pt6.slcio >>> -DoutputFile=TM_6786MeV_Fall2013_HPS-Proposal2014-v5-6pt6_readout >>> --- Drivers --- >>> org.lcsim.job.EventMarkerDriver >>> eventInterval = 1000 >>> org.lcsim.hps.conditions.CalibrationDriver >>> org.lcsim.hps.recon.ecal.EcalEdepToTriggerConverterDriver >>> readoutCollection = EcalReadoutAnalogHits >>> applyBadCrystalMap = false >>> truncateScale = 1 >>> constantGain = 0.15 >>> org.lcsim.hps.recon.ecal.EcalRawConverterDriver >>> runBackwards = true >>> rawCollectionName = EcalReadoutHits >>> ecalCollectionName = EcalReadoutAnalogHits >>> org.lcsim.hps.recon.ecal.CTPEcalClusterer >>> ecalName = Ecal >>> ecalCollectionName = EcalReadoutAnalogHits >>> clusterCollectionName = EcalTriggerClusters >>> org.lcsim.hps.readout.ecal.FADCTriggerDriver >>> clusterCollectionName = EcalTriggerClusters >>> outputFileName = >>> TM_6786MeV_Fall2013_HPS-Proposal2014-v5-6pt6_readout.triggers >>> deadTime = 0 >>> lcioFile = TM_6786MeV_Fall2013_HPS-Proposal2014-v5-6pt6_readout.slcio >>> org.lcsim.hps.recon.tracking.SimpleSvtReadout >>> noPileup = true >>> org.lcsim.hps.util.ClockDriver >>> org.lcsim.recon.tracking.digitization.sisim.config.ReadoutCleanupDriver >>> --- End Drivers --- >>> No input files in XML file. >>> Got ConditionsEvent with run: 0 >>> Reading calibrations calibSVT/base for run: 0 >>> Use this calibration from run -1: calibSVT/default.base >>> Reading calibrations calibSVT/tp for run: 0 >>> Use this calibration from run -1: calibSVT/default.tp >>> Loading the SVT bad channels for run 0 >>> File daqmap/svt0.badchannels was not found! Continuing with only QA bad >>> channels >>> Loading SVT gains ... >>> Loading SVT t0 shifts ... >>> Loading fieldmap for run 0 >>> reading ECal DAQ map >>> reading ECal bad channels >>> reading pedestals for ECal >>> reading pedestals for ECal >>> FADCTriggerDriver: Setting trigger for 6.6 GeV beam >>> >>>> Event 0 >>>>> >>>> java.lang.RuntimeException: Distance is outside of sensor by more than >>> 0.001. Distance = -0.24857335945534142. 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:478) >>> at >>> org.lcsim.recon.tracking.digitization.sisim.CDFSiSensorSim. >>> depositChargeOnSense(CDFSiSensorSim.java:241) >>> at >>> org.lcsim.recon.tracking.digitization.sisim.CDFSiSensorSim. >>> computeElectrodeData(CDFSiSensorSim.java:110) >>> at >>> org.lcsim.hps.recon.tracking.SimpleSvtReadout.doSiSimulation( >>> SimpleSvtReadout.java:198) >>> at >>> org.lcsim.hps.recon.tracking.SimpleSvtReadout.process( >>> SimpleSvtReadout.java:116) >>> at org.lcsim.util.Driver.doProcess(Driver.java:273) >>> at org.lcsim.util.Driver.processChildren(Driver.java:284) >>> at org.lcsim.util.Driver.process(Driver.java:198) >>> 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:153) >>> at org.lcsim.job.JobControlManager.run(JobControlManager.java:392) >>> at org.lcsim.job.JobControlManager.main( >>> JobControlManager.java:168) >>> >>> ######################################################################## >>> 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