Hello Norman,

Thank you for looking into this.

From what I can tell, the method:  protected TrackState fillParticleVariables(EventHeader event, ReconstructedParticle particle, String prefix) in TupleDriver.java takes a track, and then adds the parameter tweaks to the track parameters of a copied BaseTrackState. It then rotates the vector with beamAxisRotation.setActiveEuler(Math.PI / 2, -0.0305, -Math.PI / 2);. After that, the routine gets the new track state at the Ecal face. The routine also gets the minNegativeIso and maxPositiveIso, which seem entirely independent from any tweaking, 

Would you know how to take these modified tracks and use them to write out a corrected LCIO file?

There are a few questions I have with this tweak:

  1. If this is a correction to the overall detector alignment, i.e. a rotation and perhaps minor shift of the entire detector, then it would only affect the track momenta and vertex position calculations.
    1. Would it be easier to get those as separate parameters, which can be applied to individual tracks in anyone’s code? 
    2. I.e. could Omar simply call a track tweak routine in his C++ code that does the same, and other people call it in Java, independent of the TupleDriver?

If that is possible, then it may present us with the quickest path towards getting these tweaked tracks available to everyone. 

Best,
Maurik

 
On Dec 2, 2016, at 12:18 PM, Holly Vance <[log in to unmask]> wrote:

Hi Norman,

The tweaks and affected variables are in the steering file:

/org/hps/steering/analysis/MakeTuples.lcsim

-Holly

On Dec 2, 2016, at 12:15 PM, Graf, Norman A. <[log in to unmask]> wrote:

Thanks Holly,

That's very useful. Accessing the data in this fashion obviously can be very efficient. I think the pitfalls inherent in also modifying the data at this step is clear to all, but it may be necessary at this stage in order to get timely results. It would be useful to have a list of those variables which are being modified by this code before being written out. That would provide an at-a-glance list of differences between analyses run directly off the lcio or dst files, and those run off tuples derived in this manner.

Norman

From: [log in to unmask] <[log in to unmask]> on behalf of Holly Vance <[log in to unmask]>
Sent: Friday, December 2, 2016 8:30 AM
To: hps-software
Subject: Tuple maker
 
Hi all,

If anyone was curious to see what is available in the tuple maker (or wanted to run it):

https://github.com/JeffersonLab/HPS-CODE/tree/master/ANALYSIS/tuple

-Holly

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