Print

Print


Hi, Maurik.

Thanks for the info.

As long as these scalar events are tagged with the right type indicator, there shouldn't be a problem picking them out of the event stream.  Basically there is a processing chain of EtEvent -> EvioEvent -> LcioEvent which is executed for physics events.  Other events are handled differently, depending on their type.  Right now, for the 'prestart' and 'go' events there is just some information logged into the GUI like starting time.  Otherwise, not much is done with them.  I'm not sure what should happen with the scalars though.  Is the monitoring app supposed to do something special with them?  I'm supposing this is mostly various types of conditions data, in which case it should probably be extracted later from the EVIO files on disk in an offline process.

Or if there are scalars used to indicate some serious problem ("Tracker is on fire!") then it seems like maybe the monitoring app should make the user aware of this status. 

--Jeremy

-----Original Message-----
From: Maurik Holtrop [mailto:[log in to unmask]] 
Sent: Thursday, October 24, 2013 12:57 PM
To: McCormick, Jeremy I.
Cc: Serguei Boiarinov; hps-software
Subject: Re: null EVIO events in test run data

Hi Jeremy,

For the online data, there are probably going to be other event types as well, probably something like "scalar" events. Serguei may be able to tell us if there are any others, especially if there are other event types that the monitoring app needs to be aware of.

Best,
	Maurik

On Oct 24, 2013, at 3:49 PM, "McCormick, Jeremy I." <[log in to unmask]> wrote:

> Hi, Serguei.
> 
> Yes, I think that's true.  I rearranged some of the code for reading different events types in the monitoring application (not checked in yet), as what was there didn't make much sense.  That seemed to make this problem go away, and I can see the prestart and go events being handled correctly now.  I think maybe these non-physics events were being treated as physics events before.  I'll let you know if the problem crops up again.  
> Thanks!
> 
> --Jeremy
> 
> -----Original Message-----
> From: Serguei Boiarinov [mailto:[log in to unmask]] 
> Sent: Thursday, October 24, 2013 5:42 AM
> To: McCormick, Jeremy I.
> Cc: hps-software; Serguei Boiarinov
> Subject: Re: null EVIO events in test run data
> 
> Is it 'prestart' and 'go' events ?
> 
> ----- Original Message -----
> From: Jeremy I. McCormick <[log in to unmask]>
> To: hps-software <[log in to unmask]>
> Sent: Thu, 24 Oct 2013 04:38:44 -0400 (EDT)
> Subject: null EVIO events in test run data
> 
> Hi,
> 
> I'm back to doing some work on the monitoring app, and I'm seeing something strange...  
> 
> I have noticed that in the EVIO files for the test run, there are always a few events in the beginning of the run for which the EvioReader returns a null EvioEvent without throwing any kind of error.  Since this class is a complete black box to me, I wonder if anyone can tell me why this might be happening?  Does the problem sound familiar?
> 
> It seems I can simply skip over these problematic events without any adverse effects, but ideally this situation should result in an exception being thrown.  I would like to be able to pre-check events for characteristics that will cause this problem and discard them if this is going to happen, but right now I can't tell what exactly is going wrong.  
> 
> For now, I'll just have the app print a message to the log table.
> 
> Thanks.
> 
> -Jeremy
> ########################################################################
> 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