Project

General

Profile

Feature #17177

Add backtracker (LarSoft service) information for the reconstruction-truth matching into GALLERY framework.

Added by Gianluca Petrillo about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Library
Target version:
Start date:
07/13/2017
Due date:
% Done:

90%

Estimated time:
40.00 h
Spent time:
Experiment:
MicroBooNE
Co-Assignees:
Duration:

Description

This request is ported from ServiceDesk ticket RITM0582943 by Raquel Castillo Fernandez:

Add backtracker (LarSoft service) information for the reconstruction-truth matching into GALLERY framework.
We would like to use the backtracker into GALLERY, which currently is a service in LArSoft and may help in order to speed up analysis using this framework


Related issues

Blocked by LArSoft - Feature #17099: Make standard geometry available in gallery environmentClosed2017-07-03

Blocked by LArSoft - Meeting #18283: Define a policy for LArSoft art-independent code and repositoriesClosed2017-11-15

History

#1 Updated by Gianluca Petrillo about 2 years ago

  • Description updated (diff)

#2 Updated by Gianluca Petrillo about 2 years ago

  • Estimated time set to 40.00 h

cheat::BackTracker relies on GeometryCore and DetectorClocks service providers.
These need to be made available in gallery first.

#3 Updated by Gianluca Petrillo about 2 years ago

  • Blocked by Feature #17099: Make standard geometry available in gallery environment added

#4 Updated by Gianluca Petrillo about 2 years ago

  • Blocked by Feature #17179: Make standard detector clocks available in gallery environment added

#5 Updated by Gianluca Petrillo about 2 years ago

Since the requester is in MicroBooNE, it should be noted that in order for MicroBooNE to be able to effectively use BackTracker, MicroBooNE must also make its geometry and its DetectorClocks implementation of choice be available in that context.

#6 Updated by Lynn Garren about 2 years ago

  • Status changed from New to Assigned
  • Target version set to 2017-4-quarter
  • Experiment MicroBooNE added
  • Experiment deleted (-)

Will backtracker changes as a result of Hans' work? Is this an opportunity to review the code? There is a dependency on nutools which needs to be understood.

#7 Updated by Katherine Lato almost 2 years ago

  • Assignee changed from Gianluca Petrillo to Jason Stock
  • Target version changed from 2017-4-quarter to 2018-1-quarter

Reassigned to Jason (who agreed with the caveat that while he's not opposed to taking on the issue, he doesn't have time in the short term. He hopes to get to it with the new calendar year.

#8 Updated by Jason Stock almost 2 years ago

Lynn, what work by Hans are you referring too? I would be interested in having a look at it.

Additionally, I am fairly comfortable with the NuTools/BackTracker dependencies, and would be able to elaborate with a more specific question.

Katherine, This issue has been assigned to me, what about the sub issues (The issues blocking this issue.) Will those also be delegated to me?

#9 Updated by Lynn Garren almost 2 years ago

Hans Wenzel is rewriting LArG4. To the best of my knowledge, none of that work is available yet. General outlines have been presented at various coordination meetings. It is possible that the work Hans is doing will make the nutools geant4 interface unnecessary. Please contact Hans directly.

#10 Updated by Gianluca Petrillo almost 2 years ago

Jason Stock wrote:

Katherine, This issue has been assigned to me, what about the sub issues (The issues blocking this issue.) Will those also be delegated to me?

(non-Katherine here)

Not necessary. LArSoft, owner of repository structure, should suggest where to put both the services in issue #17179 and this one (they may be two different places, too).
After that, the resolution of issue #17179 should be quick: differently from chet::BackTracker, detinfo::DetectorClocksStandard is already Gallery-ready.

#11 Updated by Jason Stock almost 2 years ago

So, this is now going to be related to the introduction of the ParticleInventoryService. The new ParticleInventory will be ready for Gallery, and the BackTracker/PhotonBacktracker will be rebuilt to use the ParticleInventory. At the same time I will try to make them Gallery ready.

#12 Updated by Jason Stock almost 2 years ago

Design decision time.

Functions have been added to the backtracker that take a trackID, and return all hits from the TrackID. While this is a potentially very useful function, it takes as an input a list of candidate hits that it is supposed to search for the Hits associated with TrackID X. I do not like this design for cases where the user wants to search all hits. Is there a serviceprovider or tool in LArSoft already to quickly access all hits in an event, or will I need to script one into the backtracker?

#13 Updated by Gianluca Petrillo almost 2 years ago

Are you asking whether LArSoft has a standard way to allow an experiment to specify which hit collection to use "by default"?
The current answer is no, and while there are vague talks of that changing, I believe this is not going to happen any time soon.
In case, that collection might even be a collection of art pointers rather than a collection of hits, to allow mixing different collections without data duplication and information loss.

#14 Updated by Jason Stock almost 2 years ago

Thank you Gianluca. I will go ahead and write a template in the backtracker to get all art::Ptr to recob::Hit objects out of the event. We can change that in the future to conform to whatever LArSoft decides to do later.

#15 Updated by Jason Stock almost 2 years ago

Many of the backtracker functions have been changed to optimize the work done, reduce memory usage, or try and build a self-consistent interface. These changes are still restricted to my feature branch for the backtracker. Before deployment, feature branches for all larsoft code will be needed to update calls to the backtracker.

#16 Updated by Jason Stock almost 2 years ago

  • % Done changed from 0 to 90

The feature branches feature/JStock_BackTrackerIntegratedUpdate are now available to allow the updated backtracker and particle inventory service to run in LArSoft.

I have finished updating dunetpc to allow the backtracker to run. I have not updated any of the other experiment specific code yet.

This marks completion of making the BackTracker art independent (gallery ready),
Most fhicl validation compliance is implemented. I would still like to go back and review the modules to make sure I didn't miss anything.
The Particle List and MCTruth management has been removed from the back tracker, and now lives in ParticleInventoryService.
Function names in the backtracker have been updated to reflect what they actually do (IDEs and IDs are no longer conflated in function names.)

#17 Updated by Jason Stock almost 2 years ago

I will mark this resolved with LArSoft v06_56_00. Both ParticleInventoryService and BackTrackerService have art independent service providers.

#18 Updated by Gianluca Petrillo almost 2 years ago

  • Blocked by Meeting #18283: Define a policy for LArSoft art-independent code and repositories added

#19 Updated by Jason Stock over 1 year ago

This didn't make larsoft v06_56_00, but it is now integrated in larsoft v06_58_00. I am marking this as resolved.

#20 Updated by Jason Stock over 1 year ago

  • Status changed from Assigned to Resolved

#21 Updated by Jason Stock over 1 year ago

  • Blocked by deleted (Feature #17179: Make standard detector clocks available in gallery environment)

#22 Updated by Jason Stock over 1 year ago

I don't appear to be able to close this ticket myself. It has been resolved for some months now with the adoption of the BackTracker/BackTrackerService.

#23 Updated by Lynn Garren over 1 year ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF