[Halld-offline] track timing parameters

[Richard Jones]

Paul and all,

I have incorporarted the suggested additions from Paul, and added the missing Eerr parameter pointed out by David during the meeting.  The revised template has all of the required elements that I know of so far.

http://zeus.phys.uconn.edu/halld/datamodel/rest.xml

-Richard J.

On 6/27/2012 7:12 PM, Paul Mattione wrote:
> Hey Richard, here's what I think we should have/change about track timing parameters in the data format:
>
> t0 = DChargedTrackHypothesis::dProjectedStartTime
> t0err = DChargedTrackHypothesis::dProjectedStartTimeUncertainty
> flightTime = DChargedTrackHypothesis::t1() - DChargedTrackHypothesis::dProjectedStartTime
> SCt0 = DChargedTrackHypothesis::t0() //this is the SC time projected back to the beamline //allows user to re-determine the RF bunch later, or perhaps compare this to their "t0" to make judgments on PID
> SCt0err = 0.3 //until determined
>
> And an event-scope parameter (unless this is already in there and I missed it):
> RFTime = 0.0 //Unless things change, other RF bunches are just in increments of 2.004 ns from whatever the reconstruction chooses here
>
>
>   - Paul



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2770 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://mailman.jlab.org/pipermail/halld-offline/attachments/20120627/a4621ac8/attachment.p7s>