On Aug 2, 2015, at 12:00 PM, Graham, Mathew Thomas <[log in to unmask]> wrote:Thanks for this…very interesting!
…what sort of events did you use to create the profile?
The tracking is only ~50% of the job while I expected more (I’ve seen more, but that is without SVT & ECAL pulse fitting)…and all of the time in tracking in the MS code checking if the helix intersected the sensor! Not that this is slow but there are lots and lots and lots of calls to org.hps.recon.tracking.MultipleScattering.getHelixIntersection and stuff it calls (checking whether the helix intersects any of the faces of the polygonal sensor).
Considering we will (eventually, soon!) use GBL to get the fit parameters of the final tracks and we’ll just use SeedTracker for track finding, we probably don’t need to be so careful here.
On Aug 1, 2015, at 8:07 PM, Maurik Holtrop <[log in to unmask]> wrote:
I have created two new pages that will be helpful if you are trying to figure out what is going on in the HPS code during reconstruction. These pages show all the methods that are called, in a tree like fashion, and indicates the number of times each method is called, and the amount of time spend executing the method. Clicking on the method name will jump you to the Java Doc for that method.
These pages were not compatible with Confluence, so I put them here: http://nuclear.unh.edu/HPS/Profiles/Call_Tree_EvioToLcio.xml and http://nuclear.unh.edu/HPS/Profiles/Call_Tree_doProcess.xmlYou can find the links to these pages in the Confluence “Code Documentation” section ( https://confluence.slac.stanford.edu/display/hpsg/Code+Documentation )
Use REPLY-ALL to reply to list
To unsubscribe from the HPS-SOFTWARE list, click the following link: