Print

---

Hi, it would be a good idea to make it so that Processors could throw
something like an AbortEvent exception to cause analysis to continue
with the next event, but we didnt do that yet.

Meanwhile you could override the process method in your JetFinderTestV5
as follows

   public void process(LCDEvent e)
   {
       // only continue with normal processing if EventSelection returns
true
       if (doEventSelection(e))
       {
          super.process(e); // Calls the super classes process method
       }
   }
   boolean doEventSelection(LCDEvent e)
   {
	// Perform some tests and return true or false
   }

> -----Original Message-----
> From: Eugene Guillian [mailto:[log in to unmask]]
> Sent: Wednesday, April 21, 1999 7:21 AM
> To: 
> Cc: [log in to unmask]
> Subject: Skipping events in JAS
> 
> 
> Hi,
> 
> I have a question about skipping events in JAS.
> 
> I'm analyzing reconstructed tracks, and I implement the analysis as
> follows:
> 
> 
> public final class JetFinderTestV5 extends Driver {
> 
>     public JetFinderTestV5() {
>         add(new TrackReco()); 
>         add(new TrackJetAna());
>     }
> }
> 
> 
> TrackJetAna is an analysis routine I run after tracks are found.  One
> problem with this is that I'm only intrested in a subset of events
> satisfying some conditions (namely, that the ttbar event 
> decays into the
> "Lepton + Jets" decay channel).  So in events that don't satisfy these
> conditions, the CPU time spent on track reconstruction is wasted.  Is
> there a way to add a filtering process before track 
> reconstruction that
> tells JAS to skip to the next event?
> 
> Gene
>