Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #70 +/- ##
==========================================
- Coverage 63.05% 62.32% -0.74%
==========================================
Files 19 19
Lines 1394 1412 +18
==========================================
+ Hits 879 880 +1
- Misses 515 532 +17 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I can have a look at how much work is to do the correction on the times today. |
|
I do not think we should do it now, it isnt used for the main observables
…________________________________
From: Luigi Pertoldi ***@***.***>
Sent: Thursday, January 29, 2026 9:51 AM
To: legend-exp/legend-simflow ***@***.***>
Cc: Dixon, Toby ***@***.***>; Author ***@***.***>
Subject: Re: [legend-exp/legend-simflow] Forced trigger (PR #70)
⚠ Caution: External sender
[https://avatars.githubusercontent.com/u/20358192?s=20&v=4]gipert left a comment (legend-exp/legend-simflow#70)<#70 (comment)>
I can have a look at how much work is to do the correction on the times today.
—
Reply to this email directly, view it on GitHub<#70 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANSET46O7E3K4IMSWJLGJA34JHCYPAVCNFSM6AAAAACTHZP466VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMJWGMZDKMJRHE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
i think we should for each simulated event look for a sample of random coincident pulse times in the data (in a certain window, e.g. 6 us) and just save this as an additional field in the opt tier. i think this would be useful to develop time/pattern based veto classifiers |
|
Definitely useful but not a main priority, and I think rather specialised just for that application.
We should start with just summed pe and multiplicity, our main observable defining the lar veto cut.
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Luigi Pertoldi ***@***.***>
Sent: Sunday, February 1, 2026 6:42:00 PM
To: legend-exp/legend-simflow ***@***.***>
Cc: Toby Dixon ***@***.***>; Author ***@***.***>
Subject: Re: [legend-exp/legend-simflow] Forced trigger (PR #70)
⚠ Caution: External sender
[https://avatars.githubusercontent.com/u/20358192?s=20&v=4]gipert left a comment (legend-exp/legend-simflow#70)<#70 (comment)>
i think we should for each simulated event look for a sample of random coincident pulse times in the data (in a certain window, e.g. 6 us) and just save this as an additional field in the opt tier. i think this would be useful to develop time/pattern based veto classifiers
—
Reply to this email directly, view it on GitHub<#70 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANSET44MFXNXL7RHG353QQ34JY3GRAVCNFSM6AAAAACTHZP466VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMZRGUZTSOBQG4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
There was a problem hiding this comment.
Pull request overview
This PR implements a forced trigger library extraction function for SiPM photoelectron spectrum corrections. The implementation moves an existing utility function into the local codebase and adds new functionality to process forced trigger events.
Changes:
- Moved
get_remage_detector_uidsfrom reboost.utils to local reboost.py module - Added
get_forced_trigger_libraryfunction to extract and format forced trigger events for SiPM corrections - Updated type hints to use
HPGeScalarRZFieldinstead of deprecatedHPGeRZField
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| workflow/src/legendsimflow/scripts/tier/evt.py | Updated import to use local reboost_utils.get_remage_detector_uids instead of reboost.utils |
| workflow/src/legendsimflow/reboost.py | Added get_remage_detector_uids function, implemented get_forced_trigger_library, and updated HPGe type hints |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Well @rosannadeckert is already trying to use simulations to study the classifier. In any case my point is that you already have the machinery to read in the evt data, so it should be quite simple to just make store the pulse information, instead of computing a derived quantity. |
|
I think we should first do the simplest case to get our background model PDFs, then if @rosannadeckert needs the times, maybe she can contribute, since changes are then also needed in reboost |
|
sure, i can help! what kind of change is needed in reboost? |
|
let me have a look at what tobi wrote here so i can advise |
|
I think the change is rather minimal just append lists not sum |
2a7b196 to
e9f6802
Compare
|
@rosannadeckert do you want to work on this? |
|
yes |
|
Superseded by #93. |
|
We should not just start from scratch.. and correction should be in reboost
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Luigi Pertoldi ***@***.***>
Sent: Friday, February 6, 2026 4:25:01 PM
To: legend-exp/legend-simflow ***@***.***>
Cc: Toby Dixon ***@***.***>; Author ***@***.***>
Subject: Re: [legend-exp/legend-simflow] Forced trigger (PR #70)
⚠ Caution: External sender
Closed #70<#70>.
—
Reply to this email directly, view it on GitHub<#70 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANSET4ZZVKI2QCXXOMCSNPT4KS553AVCNFSM6AAAAACTHZP466VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRSGU4TGOJSGAZDGMA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
#93 includes the code from this PR. we can develop the routines here for convenience and move them to reboost later, as we still have to do for all the reboost.py module |
|
Ok but then it would have been better to start from my branch
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Luigi Pertoldi ***@***.***>
Sent: Friday, February 6, 2026 4:34:44 PM
To: legend-exp/legend-simflow ***@***.***>
Cc: Toby Dixon ***@***.***>; Author ***@***.***>
Subject: Re: [legend-exp/legend-simflow] Forced trigger (PR #70)
⚠ Caution: External sender
[https://avatars.githubusercontent.com/u/20358192?s=20&v=4]gipert left a comment (legend-exp/legend-simflow#70)<#70 (comment)>
#93<#93> includes the code from this PR. we can develop the routines here for convenience and move them to reboost later, as we still have to do for all the reboost.py module
—
Reply to this email directly, view it on GitHub<#70 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANSET46KLXSZJPMEGZMSNO34KS7CJAVCNFSM6AAAAACTHZP466VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNRRGM4DINZZGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
@rosannadeckert can't push to your branch |
|
I do not really understand why the function adding the corrections is needed here. reboost can already do it.
If you want to change small things its better making a PR there
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Toby Dixon ***@***.***>
Sent: Friday, February 6, 2026 4:35:30 PM
To: legend-exp/legend-simflow ***@***.***>; legend-exp/legend-simflow ***@***.***>
Cc: Author ***@***.***>
Subject: Re: [legend-exp/legend-simflow] Forced trigger (PR #70)
Ok but then it would have been better to start from my branch
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Luigi Pertoldi ***@***.***>
Sent: Friday, February 6, 2026 4:34:44 PM
To: legend-exp/legend-simflow ***@***.***>
Cc: Toby Dixon ***@***.***>; Author ***@***.***>
Subject: Re: [legend-exp/legend-simflow] Forced trigger (PR #70)
⚠ Caution: External sender
[https://avatars.githubusercontent.com/u/20358192?s=20&v=4]gipert left a comment (legend-exp/legend-simflow#70)<#70 (comment)>
#93<#93> includes the code from this PR. we can develop the routines here for convenience and move them to reboost later, as we still have to do for all the reboost.py module
—
Reply to this email directly, view it on GitHub<#70 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANSET46KLXSZJPMEGZMSNO34KS7CJAVCNFSM6AAAAACTHZP466VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNRRGM4DINZZGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
This gives the basic function to create the forced trigger library in a format that https://reboost.readthedocs.io/en/stable/api/reboost.spms.html#reboost.spms.pe.corrected_photoelectrons can use.
For now we have not performed a forced trigger correction that returns the photon times, rather just the summed pe per channel. I think this is ok to start with.
If we want to instead obtain the nested vector of pe times we need new functionality in reboost.