Hi,

When I tried making a new MC file, running it through the HPS-Proposal2014-v3-2pt2 detector with SLIC, and then using the steering file HPSTrackingBunchedMC.lcsim with my own analysis driver, I'm getting the following error message:

--- Drivers ---
org.lcsim.hps.recon.tracking.HPSSVTSensorSetup
org.lcsim.job.EventMarkerDriver
    eventInterval = 1
org.lcsim.hps.recon.tracking.TrackerDigiDriver
    debug = false
org.lcsim.hps.recon.tracking.TrackerReconDriver
    debug = false
    strategyResource = /org/lcsim/hps/recon/tracking/strategies/HPS-Test-Lyr50.xml
org.lcsim.hps.users.joey.AnalysisDriver
org.lcsim.util.loop.LCIODriver
    outputFilePath = signal.slcio_trackRecon
--- End Drivers ---
--- Input Files ---
[1] /home/joey/Research/HPS-Home/HPS-Software/signal.slcio
--- End Input Files ---
Adding SimTrackerHitIdentifierReadoutDriver with readouts: [TrackerHits]
org.lcsim.conditions.ConditionsManager$ConditionsSetNotFoundException: Error reading detector condition item 'compact.xml' for detector 'HPS-Proposal2014-v3-2pt2'
at org.lcsim.util.loop.DetectorConditionsConverter.getData(DetectorConditionsConverter.java:32)
at org.lcsim.util.loop.DetectorConditionsConverter.getData(DetectorConditionsConverter.java:17)
at org.lcsim.conditions.CachedConditionsImplementation.getCachedData(CachedConditionsImplementation.java:19)
at org.lcsim.event.base.BaseLCSimEvent.getDetector(BaseLCSimEvent.java:75)
at org.lcsim.util.DriverAdapter.recordSupplied(DriverAdapter.java:70)
at org.freehep.record.loop.DefaultRecordLoop.consumeRecord(DefaultRecordLoop.java:816)
at org.freehep.record.loop.DefaultRecordLoop.loop(DefaultRecordLoop.java:660)
at org.freehep.record.loop.DefaultRecordLoop.execute(DefaultRecordLoop.java:559)
at org.lcsim.util.loop.LCSimLoop.loop(LCSimLoop.java:151)
at org.lcsim.job.JobControlManager.run(JobControlManager.java:374)
at org.lcsim.job.JobControlManager.main(JobControlManager.java:165)
Caused by: org.jdom.input.JDOMParseException: Error on line 350: cvc-complex-type.3.2.2: Attribute 'file' is not allowed to appear in element 'gdmlFile'.
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807)
at org.lcsim.geometry.compact.CompactReader.read(CompactReader.java:82)
at org.lcsim.geometry.GeometryReader.read(GeometryReader.java:45)
at org.lcsim.util.loop.DetectorConditionsConverter.getData(DetectorConditionsConverter.java:26)
... 10 more
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'file' is not allowed to appear in element 'gdmlFile'.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:489)
... 14 more

Everything seemed to work before a more recent CVS update, so I'm not sure if it's a problem with this particular detector or if there's something else new that must be done to run events through an analysis. Any ideas?

Thanks,
Joey


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