Skip to content

Conversation

@PetrilloAtWork
Copy link
Member

The job configuration stage1_run2_icarus.fcl featured a flash filtering which has been outfashioned by the presence of a trigger and will be obsoleted by filtering based on CRT/PMT matching.
The filter in that job is also misconfigured, using a very old time reference for its flash window specification which is now way out of the PMT readout range. That means that using that configuration will suppress all the input events.

This pull request:

  • removes the filter from Stage1 configurations (Run1 and Run2); effectively, stage1_run2_icarus.fcl is now equivalent to stage1_run2_nofilter_icarus.fcl;
  • updates the configuration in the Stage0 definition (which is not used anyway)
  • updates the configuration of the stand-alone filter job

I took the chance to also update the list of configurations that should be skipped by the FHiCL syntax test.

I will follow with a pull request for the production branch.

Suggested reviewer:

  • @SFBayLaser, workflow maintainer
  • Ivan Caro, production manager, if I could have tagged him on GitHub

@mmrosenberg
Copy link
Contributor

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_73_00

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c7: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
Collaborator

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

@mmrosenberg
Copy link
Contributor

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_73_00 SBNSoftware/sbncode@v09_73_00 SBNSoftware/sbndaq-artdaq-core@v1_06_00of0

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

⚠️ CI build for ICARUS Warning at phase ci_tests ICARUS on slf7 for c7:prof - ignored warnings for build -- 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 Warning at phase ci_tests ICARUS on slf7 for e20:prof - ignored warnings for build -- 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

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.

Is there a reason to not also delete the file "stage1_run2_nofilter_icarus.fcl" since it will be redundant? Or am I just not seeing that in the list?

Otherwise, thank you for addressing this as it was obvious this was quite out of date.

@PetrilloAtWork
Copy link
Member Author

No strong reason. I did not remove it because I thought it may have a role if the CRT/PMT matching-based filter is introduced, but then it will probably be at Stage0 anyway.

They are equivalent to the mainline configurations, by which they are now replaced.
@PetrilloAtWork
Copy link
Member Author

Adopted the reviewer suggestion of removing the configurations names nofilter, which indeed do not apply any filter but they are not special in that regard.
The twin PR #578 is a bit more tricky though, since one of the nofilter configurations is used in the production chain.
Specific discussion goes in that PR.

@mmrosenberg
Copy link
Contributor

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_73_00 SBNSoftware/sbncode@v09_73_00 SBNSoftware/sbndaq-artdaq-core@v1_06_00of0

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

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

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

parent CI build details are available through the CI dashboard

@FNALbuild
Copy link
Collaborator

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

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

parent CI build details are available through the CI dashboard

@PetrilloAtWork
Copy link
Member Author

The test is right, a fix is needed.

@PetrilloAtWork
Copy link
Member Author

Please run the test again: it should be fixed now.
At least it passes the test locally.

@mmrosenberg
Copy link
Contributor

trigger build

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

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

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

@mmrosenberg
Copy link
Contributor

trigger build

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

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

@FNALbuild
Copy link
Collaborator

⚠️ CI build for ICARUS Warning at phase ci_tests ICARUS on slf7 for e20:prof - ignored warnings for build -- 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 Warning at phase ci_tests ICARUS on slf7 for c7:prof - ignored warnings for build -- 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

@mmrosenberg mmrosenberg merged commit f07dd54 into SBNSoftware:develop Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants