 |
 |
Hello Matt, There were two basic changes to MaterialManager which were introduced to define or transform "x planes." These have been wrapped with a boolean which is set by default for collider usage and is overridden for HPS in TrackerReconDriver. There was also a modification to the logic of how to set up the readout drivers in StripDigiSetupDriver. I'm not yet sure which version of that is correct, but wanted to revert to the status quo ante before figuring that out. Norman -----Original Message----- From: Graham, Mathew Thomas Sent: Thursday, May 16, 2013 1:36 PM To: Graf, Norman A. Cc: hps-software Subject: Re: track reconstruction modifications in lcsim and hps-java Do you know which changes in particular made things worse? On May 16, 2013, at 1:33 PM, "Graf, Norman A." <[log in to unmask]> wrote: > Hello All, > Recent modifications to tracking code in lcsim resulted in a > degradation of track parameter resolutions for collider simulations. > Jeremy and I wrapped these modifications to lcsim which were > introduced by HPS and we updated the hps-java to implement the > HPS-specific changes. I believe these now revert the tracking to what > we had previously. Please check out the head versions of lcsim and > hps-java and let me know if you can confirm this. I have run the > tests, but I am not confident that the tests are rigorous enough to > catch such effects (although they should). > Please let me know if you have any questions or need any additional > information. > Thanks, > Norman > > ######################################################################## 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