Repository navigation
Light and overlay fixes [develop] [4/4] - #922
PetrilloAtWork wants to merge 170 commits into
Conversation
…plate It used to end when the template SPR goes under 1e-4 ADC#. Now it needs to stay within +/- 1w-4 ADC# for 20 nanoseconds. This should make it possible to include undershootings. All these parameters are currently hard-coded.
…icles that might cross cathode
Good catches on names and strings. Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
❌ 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 |
|
❌ 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 |
|
❌ 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 |
|
❌ 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 |
|
trigger build LArSoft/larsoft@v10_26_00 LArSoft/lar*@LARSOFT_SUITE_v10_26_00 SBNSoftware/sbncode@v10_26_00 SBNSoftware/sbn*@SBN_SUITE_v10_26_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06_01 |
|
✔️ 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 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 |
|
❌ 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 |
|
trigger build LArSoft/larsoft@v10_26_00 LArSoft/lar*@LARSOFT_SUITE_v10_26_00 SBNSoftware/sbncode@v10_26_00 SBNSoftware/sbnalg@v10_26_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06_01 SBNSoftware/sbnobj@v10_23_00 SBNSoftware/sbnanaobj@v10_26_00 |
|
✔️ 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 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 |
|
❌ 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 |
|
@PetrilloAtWork and @mvicenzi, There are some build errors from CI build 15462 that need resolving. I'm attaching the build log from the CI build here: |
|
@jas1005 This PR needs SBNSoftware/sbncode#671, which was included only in sbncode v10_27_00, not in v10_26_00. Can you try bumbing the sbncode version? |
|
trigger build LArSoft/larsoft@v10_27_00 LArSoft/lar*@LARSOFT_SUITE_v10_27_00 SBNSoftware/sbncode@v10_27_00 SBNSoftware/sbnalg@v10_27_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06_01 SBNSoftware/sbnobj@v10_27_00 SBNSoftware/sbnanaobj@v10_27_00 |
|
✔️ 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 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 |
|
❌ 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 |
Required separate from merge for testing via CI system.
|
trigger build LArSoft/larsoft@v10_27_00 LArSoft/lar*@LARSOFT_SUITE_v10_27_00 SBNSoftware/sbncode@v10_27_00 SBNSoftware/sbnalg@v10_27_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06_01 SBNSoftware/sbnobj@v10_27_00 SBNSoftware/sbnanaobj@v10_27_00 SBNSoftware/icaruscode@v10_25_00 SBNSoftware/icarusalg#102 SBNSoftware/icarusutil@v10_24_00 SBNSoftware/icarus_signal_processing@v10_25_00 |
|
✔️ 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 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 |
|
❌ 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 |
|
@mvicenzi and @PetrilloAtWork, I'm moving discussion to this ICARUSCode PR since SBNSoftware/icarusalg#102 is giving build issues. Whatever dependency mismatch issues that cause the ICARUSAlg PR not to build are not present here. Since the PRs are co-dependent, I think it's safe to just work through issues we have with this PR (see the above Building succeeds here, but there are some failing CI tests. Output from one such test (intimecosmic_reco0_quick_test_icaruscode) of build 15512 is below: We do not see these errors in other PRs I'm actively merging into the v10_27_00 release of ICARUSCode. So I'm inclined to think this is something with the detsim input. Can this PR use input generated by a previous code release? |
|
@jas1005 Unfortunately, this PR can't read input from older releases by default. This is due to a breaking change in the trigger modules (e994d97), and they now require a new data product produced by the |
This is the mirror set of pull requests as #917 and #892 (and all dependent ones).
The approval of the content of this PR is in principle the same as for those, but because this branch was obtained by cherry-picking, some additional scrutiny may be justified.
Additional PR are required before/together with this one:
develop] [1/4] sbnalg#10develop] [2/4] sbncode#671develop] [3/4] icarusalg#102develop] [4/4] #922 (for listing completeness)Reviewers: