Fix pfp ordering when using SCE products#832
Conversation
|
Is there any documentation about the metadata/these functions? Just curious of other unrelated instances where this could be wrong. |
|
trigger build ci_ref=v10_10_03_01 LArSoft/lar*@LARSOFT_SUITE_v10_10_03 SBNSoftware/sbndaq_artdaq_core@v1_10_06 SBNSoftware/sbnd_data@v01_36_00 |
|
@nathanielerowe I have not seen any documentation related to this, but I believe the correct thing to do is to use .key(). The Self() method is something related to the internal that pandora makes and hence, is not necessarily related to the ordering of the art association. |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for SBND Failed at phase build SBND on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build SBND phase logs parent CI build details are available through the CI dashboard |
|
🚨 For more details about the warning phase, check the ci_tests SBND phase logs parent CI build details are available through the CI dashboard |
|
Approved |
This PR fixes a bug when using SCE products for running light propagation correction module.
When using
pfp_to_metadata.at(pfp->Self())with SCE products the wrong metadata vector is retrieved. Instead, the object has to be retrieved throughpfp_to_metadata.at(pfp.key()).Description
Please provide a detailed description of the changes this pull request introduces.
Checklist
Reviewers,AssigneesDevelopementRelevant PR links (optional)
Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?
Link(s) to docdb describing changes (optional)
Is there a docdb describing the issue this solves or the feature added?