Print

Print


At the moment, we have two readers (ECalEvioReader and SVTEvioReader) which
are used in the conversion of EVIO data to LCIO.  Those two classes are
currently configured to read only test run data.  The plan is to make those
classes abstract and then to create subclasses for the test run and
engineering run.  Which converters are used will then only depend on which
version of *EvioToLcio is used to process events.

--Omar Moreno

On Fri, Oct 10, 2014 at 12:21 PM, Serguei Boiarinov <[log in to unmask]>
wrote:

> When we'll start to record data files we want to keep, we should probably
> start from run number bigger then biggest in test run, that way software
> can
> reconfigure itself based on run number, we did it in CLAS.
>
> ----- Original Message -----
> From: Andrea Celentano <[log in to unmask]>
> To: Jeremy I. McCormick <[log in to unmask]>
> Cc: [log in to unmask]
> Sent: Fri, 10 Oct 2014 15:16:23 -0400 (EDT)
> Subject: Re: EventConstants file
>
> Hi,
> You mean that there will be separate LcSimEventBuilder / EventConstant /
> ECalEvioReader / SVTEvioReader / others.. for the test run and for the
> engeneering run?
>
> I am not familiar with svn trunk, I would prefer you (or someone more
> expert than me) to configure the software structure to be compatible
> with both the TestRun and the engeneering run, and then I can modifiy
> the latter.
>
> Bests,
> Andrea
>
> On 10/10/2014 03:10 PM, McCormick, Jeremy I. wrote:
> > Yeah we need to sort that out.  There will have to be seperate event
> builders.
> >
> > Do you want me to make a branch of HPS trunk so that you feel free to
> make these changes in it?
> >
> >> On Oct 10, 2014, at 10:18 AM, Andrea Celentano <
> [log in to unmask]> wrote:
> >>
> >> Hi Jeremy,
> >> things are moving here.. We were able to run the DAQ, write evio file
> on tape, read it with evio2xml and see it is fine.
> >> Then, I try to open it with the monitoring application (the direct
> connection with the ET ring does not work yet, waiting for ET14 next week).
> I see that, in
> >>
> >> org.hps.evio.EventConstant
> >>
> >> you define
> >> public static final int ECAL_TOP_BANK_TAG = 0x1;
> >>     public static final int ECAL_BOTTOM_BANK_TAG = 0x2;
> >>     public static final int SVT_BANK_TAG = 0x3;
> >>
> >> This was true for the test run. For the engineering run, it is (now):
> >>
> >>     public static final int ECAL_TOP_BANK_TAG = 0x25;
> >>     public static final int ECAL_BOTTOM_BANK_TAG = 0x27;
> >>     public static final int SVT_BANK_TAG =  ????
> >>
> >> I am changing this in my local copy, but not commit anything: you may
> want to differentiate between the test run and the engineering run
> (otherwise, if I commit it, someone else still working on old evio data
> will not be able to run!).
> >>
> >>
> >> Andrea
>
> ########################################################################
> 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