Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add run3_miniAOD_12X era modifier #42740
add run3_miniAOD_12X era modifier #42740
Changes from all commits
1db74eb
48c8838
674e1ab
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need only MINI workflow, and MINI+Nano+DQM?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MINI + Validation + DQM:@miniAOD fails with an error of missing HGCal collections. I'm really puzzled by the error and do not have time to debug the DQM side at this stage. The MINI and NANO content are anyway as expected, therefore I think the issue with DQM can be dealt with later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I have that question too on DQM. Since you start from RECO, I am not sure DQM will work as you may miss some transient product which are produced during reconstruction. May I propose to drop the broken workflow for now, for example, you comment it. This will avoid broken in the long matrix test in IB, as workflow in the standard will run. Thx.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as they are right now both tests run ok, or do you mean that the IB expects a DQM output?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12984e/34739/runTheMatrixINPUT-results/140.201_RunJetMET2022D_reMINI/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, OK. I read it quick and confuse on DQM module.
The DQM of Mini should fail as they need transient output from RECO, but DQM of Nano does not need.
What I don't see the point is why we need both workflows as both produce the same MINI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was some concern (I just unjustified) that running MINI or MINI+NANO in the same job could lead to different results / issues. I agree with you that the MINI only workflow is not strictly needed. I will revise that with a follow up PR (we, xpog, want to revise some validation workflows anyway).