Skip to content

Conversation

@asanchezcastillo
Copy link
Contributor

@asanchezcastillo asanchezcastillo commented Sep 29, 2025

Remove CorrectedOpFlash attributes that can be found via slice-correctedopflash assns. It also changes the attributes to reflect each of the corrections separately.
Merging this PR solves #160

This PR is to be merged with
SBNSoftware/sbncode#584
SBNSoftware/sbnobj#147

Copy link
Contributor

@gputnam gputnam left a comment

Choose a reason for hiding this comment

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

My main comment -- can you explain why you are making this into a new object in the StandardRecord, as opposed to putting these in the existing SRFlash? It seems like an unecessary complication.


void SRCorrectedOpFlash::setDefault()
{
OpFlashT0 = -9999.;
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't OpFlashT0 still in another object in the CAF?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is another object in the CAF but is not currently accessible from the SRSlice, so there is no way of knowing the original T0 from the slice information unless it is contained in the SRCorrectedOpFlash

@kjplows kjplows moved this from Open pull requests to Partially reviewed in SBN software development Oct 2, 2025
@asanchezcastillo
Copy link
Contributor Author

Hi @gputnam. The main reason is that SRCorrectedOpFlashes are build using charge information to correct flash attributes. This requires using flash-matching tools, which implies that not every SRFlash gets an associated SRCorrectedFlash. In fact, from all the flashes in the event, we would ideally only correct the one that coincides with the beam spill time. If we added these attributes to the SRFlash they would be empty most of the times and we would also be forced to create an SRFlash-SRSlice assns which does not exist yet.

@kjplows
Copy link
Contributor

kjplows commented Oct 24, 2025

trigger build LArSoft/lar*@LARSOFT_SUITE_v10_11_01

@kjplows kjplows moved this from Partially reviewed to Testing in SBN software development Oct 24, 2025
@FNALbuild
Copy link

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

@FNALbuild
Copy link

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

@FNALbuild
Copy link

❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for e26:prof -- details available through the CI dashboard

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

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link

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

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

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link

❌ CI build for SBND Failed at phase build SBND on slf7 for e26: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

@FNALbuild
Copy link

❌ 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

@kjplows
Copy link
Contributor

kjplows commented Nov 4, 2025

trigger build LArSoft/lar*@LARSOFT_SUITE_v10_11_01 SBNSoftware/sbnobj#147 SBNSoftware/sbncode#584 SBNSoftware/sbndcode#834

@FNALbuild
Copy link

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

@FNALbuild
Copy link

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

@FNALbuild
Copy link

❌ 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

@FNALbuild
Copy link

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

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

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link

❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for e26:prof -- details available through the CI dashboard

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

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link

❌ CI build for SBND Failed at phase build SBND on slf7 for e26: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

@kjplows
Copy link
Contributor

kjplows commented Nov 4, 2025

Incrementing the ClassVersion to make CI build, @asanchezcastillo

@kjplows
Copy link
Contributor

kjplows commented Nov 4, 2025

trigger build LArSoft/lar*@LARSOFT_SUITE_v10_11_01 SBNSoftware/sbnobj#147 SBNSoftware/sbncode#584 SBNSoftware/sbndcode#834

@FNALbuild
Copy link

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

@FNALbuild
Copy link

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

@FNALbuild
Copy link

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

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

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link

❌ 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

@FNALbuild
Copy link

❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for e26:prof - 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

⚠️ CI build for SBND Warning at phase ci_tests SBND on slf7 for e26:prof - ignored warnings for build -- details 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

@kjplows kjplows moved this from Testing to To merge in SBN software development Nov 4, 2025
@kjplows kjplows merged commit 351a474 into develop Nov 5, 2025
@github-project-automation github-project-automation bot moved this from To merge to Done in SBN software development Nov 5, 2025
@kjplows kjplows moved this from Done to Recently done in SBN software development Nov 5, 2025
@kjplows kjplows moved this from Recently done to Done in SBN software development Nov 12, 2025
@kjplows kjplows moved this from Done to 2025 PRs in SBN software development Jan 16, 2026
@kjplows kjplows added this to the v10_12_02 milestone Jan 16, 2026
@github-project-automation github-project-automation bot moved this from Todo to Done in PR archaeology Jan 16, 2026
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

Status: Done
Status: 2025 PRs

Development

Successfully merging this pull request may close these issues.

Remove attributes for SRCorrectedOpFlash

6 participants