1 / 6

PandoraPFA Development

PandoraPFA Development. J.S. Marshall University of Cambridge. Pandora Framework. Non-reusable e.g. detector specific . Runs registered content and performs book-keeping. External Content Libraries. Pandora Framework. Algorithm Manager. Register via APIs. Pandora Client Application.

eunice
Télécharger la présentation

PandoraPFA Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PandoraPFA Development J.S. Marshall University of Cambridge

  2. Pandora Framework • Non-reusable e.g. detector specific • Runs registered content and performs book-keeping External Content Libraries PandoraFramework • Algorithm Manager Register via APIs Pandora Client Application • CaloHit Manager • Cluster Manager • Isolates specific detector and software details, creating self-describing hits, tracks, etc. • Plugin Manager, etc. ILD/Marlin SiD/org.lcsim Pandora Content Libraries • Reusable, applicable to multiple detectors Structure allows for simultaneous development on multiple projects. • FineGranularity Content API • CoarseGranularity Content

  3. Pandora Development Energy correction tools Particle IDtools PandoraObjects: Hits, Tracks, Clusters, etc. Algorithms Shower profile tools Geometry and pseudolayer tools API Algorithms and Tools registered by client application and configured via PandoraSettingsfile. Algorithms implement reconstruction strategy Tools, used by multiple algorithms

  4. Required changes when ... Alter input reconstruction software Modify client application, which isolates Pandora from details of input software packages. ① Alter particle flow reconstruction strategy Add new algorithms (and alg tools, as required) to implement new approach. ② Alter particle identification Add/change particle id tools and review use of these tools by algorithms. ③ Alter detectorgeometry Modify client app. If sizeable calorimeter changes, check/modify pseudolayer tool, algs and alg config. ④ Alter cell energy response Alter calibration scheme in client app and check/modify energy correction tools. ⑤ Alter detector technology option As ④ and ⑤. E.g. For (S)DHCAL, set hit energies to constant(s), allowing cluster energy estimation. ⑥

  5. Development Procedure • Need to consider proposed change and identify whether modifications to PFA and/or particle identification are necessary. If still in doubt about required modifications, contact authors. • If there is proposed change to the detector, require simulated events, with reconstructed inner detector tracks and digitized calorimeter hits. These (almost certainly) need to be available before starting to develop with Pandora. • If proposed changes are for new algorithms or algorithm tools (e.g. particle id), can immediately start to develop alongside Pandora framework. Good idea to contact authors for advice about how the new content will interact with existing algorithms and tools. • Once development is (nominally) complete, validation procedures typically use single particle samples (initial tests or particle id validation), or Zs decaying at rest into light quarks (jet energy validation). The PandoraAnalysis package can prove useful at this stage.

  6. Example: ILD Tracking • As we have heard, ILD tracking software has changed recently. Pandora client application for ILD (MarlinPandora) must be updated to address this. • Application must pass reconstructed track properties and track states to Pandora. It must also identify track-track associations and perform track-quality checks: • Tracks must be tagged as “able to form a PFO” and/or “able to form a clusterless PFO”. • Requires detailed knowledge of reconstruction quality, issues and pathologies. • Hope to be able to identify split or fake tracks, etc. • There will be important differences compared to previous software.

More Related