Okay, thanks.
Is there some preference which to use based on this threshold value?
If we want to include the various SVT "livetime" measurements in the calculations, then it would probably be best to assign this to the LCIO recon files in the datacat rather than the EVIO. All of the logic for checking the SVT status is within the event building classes and then is subsequently available in the LCIO files via the event header, but none of this information is easily available when crawling the EVIO files, without running the event builder, which I don't think I want to do.
Do you still think it would be useful to assign a rough charge calculation to the EVIO files as well? I could see it being used for searching but I agree it is not enough for analysis.
-----Original Message-----
From: Nathan Baltzell [mailto:[log in to unmask]]
Sent: Monday, November 09, 2015 7:31 PM
To: McCormick, Jeremy I.
Cc: hps-software; [log in to unmask]
Subject: Re: FCup calculation
Those two differ only by threshold and are basically equivalent.
But neither account for SVT bias/position dead time, so are not directly useful without corrections.
On Nov 9, 2015, at 10:14 PM, "McCormick, Jeremy I." <[log in to unmask]> wrote:
> Hi,
>
> Which livetime measurement should be used for FCup calculations of integrated charge?
>
> I guess the options are TDC or TRG but I wasn't sure which to use.
>
> 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
|