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

GlobalTag: question #488

Open
mcepeda opened this issue Jan 28, 2016 · 2 comments
Open

GlobalTag: question #488

mcepeda opened this issue Jan 28, 2016 · 2 comments

Comments

@mcepeda
Copy link

mcepeda commented Jan 28, 2016

Hi everybody,

Are the GlobalTags used centralized currently? (They used to be in the environment.sh, but I do not see them now).

If they arent, I think we should add them and monitor them centrally.

(In https://github.com/uwcms/FinalStateAnalysis/blob/miniAOD_dev_76X/NtupleTools/test/make_ntuples_cfg.py#L241 , we pick them by default right?)

Right now it does not matter too much, but it will next week when the new JEC corrections arrive.

Best,

Maria

@dntaylor
Copy link

Yes, autocond lets the file tell you what to use. You can always manually change it with the --globalTag option. We took out the environment.sh globaltags back when 50ns and 25ns required different globalTags.

@mcepeda
Copy link
Author

mcepeda commented Jan 28, 2016

I see that the --globalTag can be set by the user, but I think it would be nice to do this so that it is centralized using the JETMET latest recomendations. for 76X 25ns at least. I see chaos in the future otherwise :).
But OK, we can handle it on the HTauMu side internally.
Maria

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

2 participants