Print

Print


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