Skip to content

Conversation

@JackSmedley
Copy link
Contributor

@JackSmedley JackSmedley commented Oct 27, 2023

icaruscode updates - Add barycenter flash match producer, a configurations fcl, and fcls to run on data and Monte Carlo

Associated Pull Requests ---
sbnobj PR- SBNSoftware/sbnobj#99
sbnanaobj PR- SBNSoftware/sbnanaobj#111
sbncode PR- SBNSoftware/sbncode#392
icaruscode PR- #641

Copy link
Member

@PetrilloAtWork PetrilloAtWork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First of all, despite the (usual) amount of comments, I congratulate for the job.
Here a few things that I would like you to consider before moving on:

  • the trigger flash: I would prefer fNominalTrigger to be called something like fTriggerDelay or equivalent (note that this definition involves a change of sign).
  • also for the trigger flash, consider if the definition as "the last flash to meet the criteria" is satisfactory.
  • and again about trigger flash: I think the distance to the slice should be expressed by radius, in the same fashion as the one used for picking the best flash. Note that this would imply a change or addition to more or less all the other branches.
  • documentation: I have added the documentation of the module. Missing is the explanation of the data members of the matching information. In principle the definition of the data member should go in the data product (as it is), and here some details of how that value is put together is due (for example, the centroid of the slice is defined as a representation of the position of the slice, in 3D, centimetres and in world coordinates, and this is in the data product; but here we are using a charge-weighted space point position rather than, let's say, the reconstructed primary vertex.

bool triggeredEvt = false;
if ( triggerHandle.isValid() && triggerHandle->size() == 1 ) {
trigger = (*triggerHandle).at(0);
if ( trigger.TriggerTime() >= 0 ) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

    if ( trigger.TriggerTime() >= 0 ) {

Have you met a case where a trigger time is stored negative? is that a MC thing?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is negative for simulated events that do not pass the trigger emulation.

JackSmedley and others added 17 commits November 17, 2023 13:07
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
Jack Smedley and others added 4 commits November 17, 2023 16:38
Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
…ndex

Co-authored-by: Gianluca Petrillo <petrillo.at.work@gmail.com>
@JackSmedley JackSmedley force-pushed the feature/jsmedley_Barycenter_develop branch 3 times, most recently from d333143 to 7ace536 Compare November 17, 2023 23:20
Copy link
Member

@PetrilloAtWork PetrilloAtWork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with my keyboard.

@mmrosenberg
Copy link
Contributor

@FNALbuild
Copy link
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Collaborator

❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for e26:prof - ignored failure for unit_test - ignored warnings for build -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests ICARUS phase logs

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link
Collaborator

❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for c14:prof - ignored failure for unit_test - ignored warnings for build -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests ICARUS phase logs

parent CI build details are available through the CI dashboard

@mmrosenberg
Copy link
Contributor

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_79_00 SBNSoftware/sbndaq-artdaq-core@v1_08_00of1 SBNSoftware/sbnobj#99 SBNSoftware/sbnanaobj#111 SBNSoftware/sbncode#392

@FNALbuild
Copy link
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Collaborator

⚠️ CI build for ICARUS Warning at phase ci_tests ICARUS on slf7 for e26:prof - ignored failure for unit_test -- details available through the CI dashboard

🚨 For more details about the warning phase, check the ci_tests ICARUS phase logs

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link
Collaborator

❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for c14:prof - ignored failure for unit_test -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests ICARUS phase logs

parent CI build details are available through the CI dashboard

Copy link
Contributor

@SFBayLaser SFBayLaser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Barring understanding the CI build failure I will approve to not hold this up

Copy link
Contributor

@aheggest aheggest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All looks good to me

@mmrosenberg mmrosenberg merged commit 2ea582c into SBNSoftware:develop Dec 18, 2023
@SFBayLaser SFBayLaser added the enhancement New feature or request label Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants