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

Making the tree content more flexible #40

Open
tomcornelis opened this issue Mar 8, 2019 · 0 comments
Open

Making the tree content more flexible #40

tomcornelis opened this issue Mar 8, 2019 · 0 comments

Comments

@tomcornelis
Copy link
Collaborator

There is apparently the need to make the tree content more flexible, i.e. there are too many variables in the tree which are only relevant for specific analyses. This is for example the case in the displaced branches, where it is currently preferred to simply delete stuff which is unneeded (or for which the use is not clear right now), as disk space seems to be a problem.

This will probably again lead to a situation where branches become unmergeable and new features/recommendations/fixes are not shared anymore among branches. It could also again lead to issues like the same variable names being used for different things in different branches, or the reintroduction of duplicated variables.

In order to avoid this, we need to put more switches in the code like this:

storeLheParticles = cms.untracked.bool('storeLheParticles' in extraContent),

The less-frequently used (very analysis specific) content should be switched on using
extraContent = ''

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

No branches or pull requests

1 participant