SM: Got sigma of 2.7 GeV at the Zpole after tuning up pflow algo.
(slides)
Photons from hmatrix.
Neutrals are leftovers.
Distribution is symmetric. (usually not) Fit with double gaussian.
Photon finder was not picking up the tail of the photons. Wanted to modify fixed cone to use instead.
To find photons, just allow NN to skip some layers.
MC: Not really an 80/20% split on the 2 gaussians.
RC: What were parameters for finding photons using NN?
SM: Looking...
MC: Which detector?
SM: cdcaug05, because RPCs are difficult to work with for this application.
SM: Distance 2 & 2 in transverse dimension. ~Moliere radius. Number of layers = 5.
No hits in tail, because missing hits a few layers away.
Min # cells = 8.
10 cell clusters into hmatrix and used for photons.
Ratio of E_cluster/E_actual. Apply 1.04 E correction.
RC: For neutrals, did do clustering, not just take all the hits and use their energy?
SM: Yes, use the cluster energy. Calculate the energy by using a different sampling fraction in the ecal. Similar to hits vs. energy as done by RC. Number of hits sampling fractions for ecal hits, e.g. GeV/hit.
Allow to go across ~20% of hcal to find clusters.
For ecal, use 7 layers for the hadrons. Reclustered with different parameters after removing photon clusters and MIP hits.
NG: Work on cheater from MR?
MR: Amazed at SM's results with Z jets.
Developing cheater using tracking and cluster cheater for perfect event reconstruction.
Switches to allow mixin of reconstructed particles with MCParticles.
Reconstruction for W's at 500 GeV with mass resolution ~3.7 GeV. Worse than SM's results with actual clusters.
NG: What jet finding?
MR: JadeE.
NG: Floating kT to get cuts? (???)
MR: Yes.
Useful for reconstructing jets.
Few options for energy measures. In hcal, parameterized or digital/analog calorimeter.
Confluence page.
Maybe compare with results SM is getting.
SM: "Cheating" means cheating everything?
MR: Yes.
SM: This is the blue curve in the plot.
Cheating on tracks.
Makes reconstructed particles -> jets.
Needs to be tuned.
NG: Updates from RC?
RC: No writeup, yet.
Compare clusterers and show "how you're doing". Close to a general package.
Hopefully, next week will have a writeup.
SM has parameters for NN clusterer. Would like to see if get these results.
Compare with fixed cone for energy and # of hits. (purity and efficiency)
SM: Can help decide which clusterers to use for which applications.
RC: Efficiency and purtiy -> it is always a tradeoff.
NG: Update from MC?
MC: Porting pflow code from hep.lcd. Now have most of it ported. Keeping in the contrib area, because it is not yet complete/finalized.
Added some "quick and dirty" code to get some of the geometrical information.
NG: What geo information is needed?
MC: What geometric element is a SpacePoint inside?
Solveable if subdetectors are cylindrical.
Haven't been able how to get a specific cell.
Discussing with Niels about missing features. EM not treated properly. How to combine EM and HAD code from myself and Niels.
RC: Niels stuff is not in?
MC: MST and MIP finder are more-or-less stable but not in main repository, yet.
RC: Could use MST from contrib area for benchmarking?
MC: Yes.
NG: AFA photons, might want to look at NN and fixed cone?
Probably going to be the optimal photon finder.
MC: Would like to be able to swap in one algorithm or another.
NG: Updates from NS?
NS: Working on fitter. Construction of the error matrix for the track, every point on the track f/ multiple scattering. Reading in thicknesses and radiation lengths to construct error matrix for the entire track -> weight matrix.
In the process, found a few problems with the helical swimmer, which should be resolved by TJ and JS.
JS did not count on negative radius for the helix. Bug with negative tan(lambda).
Helix for negative tracks?
Convention for negative tracks, omega = negative. Set the track for a helical swimmer from the track parameters. Pass the radius to the helix. In the helix constructor, there is no omega, just radius. But need to keep this information.
Trying to derive track parameters from any point on the track. In the swimmer, track doesn't have to be on POCA. From any point, momentum and point coordinates -> helix. Track parameters are POCA to reference point or (0,0,0). I was using MCParticles which don't necessarily originate close to IP. Putting MCParticle in helix swimmer -> swim back to original point.
Need a few more functions from swimmer.
Obtain a trajectory from the swimmer. Access the trajectory functions. Helix and Line are public interfaces or should allow people to use them.
TJ: Helix says signed radius of curvature.
NS: Think I solved these problems. Didn't put in the CVS.