 |
 |
For completeness, as Sho said, the format tag of the new FADC mode 7 is 0xe102, the same that was previously associated with the old "pulse format" (that now is 0xe10F). Therefore, if one tries to reconstruct test-run data taken in the old pulse format with the new software, this will not work. However, I do not know if this mode was actually used before... Andrea Il 12/09/2014 05:46 PM, Andrea Celentano ha scritto: > Hi all, > the format string of the data produced by the FADC in mode 7 is > coherent with the bank content. > > - The mode 3 format tag is: > > "c,i,l,N(c,N(s,i))" > > - The mode 7 format tag is: > > "c,i,l,N(c,N(s,i,s,s))" > > The two additional shorts reported are the peak "minimum" (i.e. the > pedestal) and the peak "maximum", in FADC units. These are not present > in mode 3. > > I modified the EcalEvioReader to handle this case (I tested it with > the file hps_003001_mode7.evio.0, with positive result). > > I just closed the JIRA issue related to this. > > Jeremy, can you please check if the code looks enough well written? It > works properly, but I'd like a Java expert to have a look at it and > check everything is done properly. > > Andrea > > Il 12/09/2014 05:34 PM, Maurik Holtrop ha scritto: >> Hello Sho, Kyle, >> >> If the format string is different from the actual contents of the >> bank, that that would be a bug in how the DAQ writes out the data. We >> should contact Sergey to have that fixed on the DAQ side as well. >> >> - Maurik >> >> On Dec 8, 2014, at 11:19 PM, Sho Uemura <[log in to unmask]> wrote: >> >>> Looking at hps_003001_mode7.evio.0. I see the mode 7 format, and I see: >>> >>> * the format tag is 0xe102 >>> >>> * the format string is "c,i,l,N(c,N(s,i,s,s))" >>> >>> so the format tag is the same as the old pulse format, but the >>> actual format is different. That's why the EVIO-LCIO conversion >>> isn't working. This will not work until somebody writes the code to >>> do the conversion - this is Jira item #349, I guess, assigned to >>> Andrea. >>> >>> On Mon, 8 Dec 2014, Kyle McCarty wrote: >>> >>>> Hello Sho, >>>> >>>> That's the newest that we have. The file name should indicate the >>>> ones that >>>> were run in mode 7 (the mode we are supposedly using). We aren't >>>> able to >>>> get new data at the moment, unfortunately. >>>> >>>> I made the change that you suggested and tried running the monitoring >>>> application on an older EVIO file (the DAQ is down at the moment; >>>> I'll test >>>> it on the ET ring once i comes up again) and got a different error: >>>> >>>> java.lang.NullPointerException >>>>> at >>>>> org.hps.record.composite.EvioEventAdapter.recordSupplied(EvioEventAdapter.java:92) >>>>> >>>>> 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.hps.record.composite.CompositeLoop.loop(CompositeLoop.java:211) >>>>> at >>>>> org.hps.record.composite.EventProcessingThread.run(EventProcessingThread.java:48) >>>>> >>>>> org.hps.record.RecordProcessingException: No next EVIO record >>>>> available >>>>> from source. >>>>> at >>>>> org.hps.record.composite.EvioEventAdapter.recordSupplied(EvioEventAdapter.java:103) >>>>> >>>>> 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.hps.record.composite.CompositeLoop.loop(CompositeLoop.java:211) >>>>> at >>>>> org.hps.record.composite.EventProcessingThread.run(EventProcessingThread.java:48) >>>>> >>>>> Caused by: org.freehep.record.source.NoSuchRecordException >>>>> at >>>>> org.hps.record.evio.EvioFileSource.next(EvioFileSource.java:109) >>>>> at >>>>> org.hps.record.composite.EvioEventAdapter.recordSupplied(EvioEventAdapter.java:68) >>>>> >>>>> ... 5 more >>>>> org.hps.record.composite.CompositeLoopAdapter.finish >>>>> >>>> I'm not sure if this helps or not. >>>> >>>> Also, it is possible something with the SSP has changed, though I'm >>>> not >>>> sure if that would cause this specific error. >>>> >>>> Thanks, >>>> >>>> Kyle >>>> >>>> On Mon, Dec 8, 2014 at 10:21 PM, Sho Uemura >>>> <[log in to unmask]> wrote: >>>> >>>>> I need a file with pulse mode readout, since that's what the error is >>>>> coming from. >>>>> >>>>> (If you're not running pulse mode, and the reader is >>>>> misidentifying the >>>>> readout mode, that's obviously also a big problem.) >>>>> >>>>> I don't see anything newer than Dec. 4 in >>>>> /volatile/hallb/hps/led/; do you >>>>> mean some other directory? >>>>> >>>>> >>>>> On Mon, 8 Dec 2014, Kyle McCarty wrote: >>>>> >>>>> Hello Sho, >>>>>> I'll give that a try in a moment. >>>>>> >>>>>> For data, we don't have anything since the error started. Do you >>>>>> think it >>>>>> is related to data format? If not, we have some data from earlier >>>>>> today at >>>>>> the LED sub-directory that you can try. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Kyle >>>>>> That points to an EVIO error - either a bug in the reader (you're >>>>>> exercising the pulse mode code, and we never ran pulse mode in >>>>>> the test >>>>>> run), or something unexpected in the data format. >>>>>> >>>>>> In either case, I can probably fix it if I have a file to look >>>>>> at. I don't >>>>>> find any data from this week in /volatile or on tape, but can you >>>>>> tell me >>>>>> where to look? >>>>>> >>>>>> On Mon, 8 Dec 2014, Kyle McCarty wrote: >>>>>> >>>>>> Hello hps-software, >>>>>> >>>>>>> Using the most recent build of hps-java, we obtain the following >>>>>>> error >>>>>>> during event processing on the monitoring application in the >>>>>>> counting >>>>>>> house: >>>>>>> >>>>>>> SEVERE: Error making ECal hits >>>>>>> >>>>>>> java.lang.NullPointerException >>>>>>>> at org.hps.evio.ECalEvioReader.makePulseHits(ECalEvioReader. >>>>>>>> java:259) >>>>>>>> at >>>>>>>> org.hps.evio.ECalEvioReader.makeHits(ECalEvioReader.java:129) >>>>>>>> at >>>>>>>> org.hps.evio.LCSimEngRunEventBuilder.makeLCSimEvent( >>>>>>>> LCSimEngRunEventBuilder.java:47) >>>>>>>> at >>>>>>>> org.hps.record.composite.LcioEventAdapter.recordSupplied( >>>>>>>> LcioEventAdapter.java:82) >>>>>>>> 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.hps.record.composite.CompositeLoop.loop( >>>>>>>> CompositeLoop.java:211) >>>>>>>> at >>>>>>>> org.hps.record.composite.EventProcessingThread.run( >>>>>>>> EventProcessingThread.java:48) >>>>>>>> >>>>>>>> >>>>>>>> It seems to be keeping us from seeing events in some of the >>>>>>>> GUIs. Any >>>>>>> ideas >>>>>>> what the problem is? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Kyle >>>>>>> >>>>>>> ######################################################################## >>>>>>> >>>>>>> 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 >>>>> >>>> ######################################################################## >>>> >>>> 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 > > ######################################################################## > 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