Skip to content
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

options to the produceSkeletons script to enable V11 #87

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

franzoni
Copy link

@franzoni franzoni commented Nov 1, 2019

This PR is a minimal approach towards enabling the usage of the V11 geometry for HGCAL MC.

Taking into account @clelange and @rovere 's comments here, in this PR I add to produceSkeletons_D41_NoSmear_PU_AVE_200_BX_25ns_aged.sh and produceSkeletons_D41_NoSmear_noPU.sh command line options which allow to specify geometry, custom and global tag.

This is a minimal approach which, together with instructions, will address strictly

V11 is not yet fully validated and understood. I'd keep V10 for production with the option to switch to V11 once we are confident.

and can be extended to all produceSkeletons*.sh if desired.

If we want to add specific scripts like: produceSkeletons_D46_NoSmear_PU_AVE_200_BX_25ns.sh
, where the actual values of geometry, custom and global tag are specified, it can be done as well, following the statement:

Thanks - it would just mean adding corresponding shell scripts such as the ones for D41

  • in which case we would need to decide which if the produceSkeletons*.sh would need be duplicated.

@pfs @rovere @clelange

Giovanni Franzoni added 5 commits November 1, 2019 10:46
…itions as parameters: a way of enabling the usage of V11 HGCAL geometry
…ns as a parameter: a way of enabling the usage of V11 HGCAL geometry (ops for geometry and custom were alrady there)
@clelange clelange mentioned this pull request Nov 5, 2019
@clelange
Copy link
Contributor

clelange commented Nov 5, 2019

Hi @franzoni - thank you, this looks very neat! Given the addition of HFNose options (see CMS-HGCAL/reco-ntuples#81 and #86) this seems the best way to go, since otherwise we'd end up with lots of shell scripts that duplicate a lot of lines.

With the additional options, the README would have to be updated accordingly so that recommended/available options are clear to everyone. What do you think about the suggestion I made in #86 (comment) regarding the ntupliser config replacement?

I would suggest we first merge #86, and then move ahead with this PR, updating the README and shell scripts. This PR would probably have to be rebased then. Do you agree, @franzoni ?

@franzoni
Copy link
Author

franzoni commented Nov 5, 2019

agree, sure.
Let me know when 86 is in and I'll go about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants