Improve ScoutingNano integration with autoNano #46516
Draft
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.
(This is currently a draft PR to help facilitate initial code review. If this gets green light, we will remove this line and change to actual PR)
PR description:
This PR improves ScoutingNano integration with autoNano. This mainly concerns using ScoutingNano flavour in combination with other nano flavours. The primary use case is in scouting vs offline object comparison studies using ScoutingPFMonitor datasets. Currently, ScoutingNano configuration replaces
nanoSequence
which is also used in standard nano, making combining ScoutingNano with standard NanoAOD unclear and difficult. While there exist recipes to compose scouting+standard, they are not intuitive and do not use the autoNano functionalities. Hence, this PR implements changes to allow combining scouting+standard with autoNano. This is achieved by creating newscoutingNanoSequence
in the configuration file and not altering standardnanoSequence
. For combining scouting+standard, bothscoutingNanoSequence
andnanoSequence
will be scheduled on different paths to run. Additionally, in principle, ScoutingNano will be able to combine with other nano flavours in autoNano as well.The changes also aims to better integrate with T0 processing workflow to prepare for scouting+standard NanoAOD production for ScoutingPFMonitor dataset in the future.
In addition, we use this opportunity to also
cmsDriver.py --customise
:An accompanying documentation for this change is also available [1]. Examples using autoNano are provided and checked.
PR validation:
Pass all tests from
scram b runtests use-ibeos
Pass all tests from
runTheMatrix.py -l limited -i all --ibeos
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
This is not a backport and there is currently no plan for a backport.
[1] https://codimd.web.cern.ch/s/_sVpKamo5