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

Mention run_range to apply trigger #50

Open
gsaha009 opened this issue Jun 19, 2024 · 1 comment
Open

Mention run_range to apply trigger #50

gsaha009 opened this issue Jun 19, 2024 · 1 comment

Comments

@gsaha009
Copy link

Hello cmsdb experts,

First of all this is more like a discussion rather than an issue. I was trying to apply one HLT which should be applied for the events after run e.g. 300ZZZ as recommended. So, is there any way to specify run numbers in cmsdb campaigns?
Thanks :)

Gourab

@mafrahm
Copy link
Contributor

mafrahm commented Jun 23, 2024

Hi @gsaha009, you can always add auxiliary information to your order objects yourself, e.g. via

# add run ranges to the campaign
config_inst.campaign.x.run_ranges = {"B": (first_run, last_run), ...}

# when needed, combine dataset info with run ranges from campaign
if dataset_inst.is_data and dataset_inst.has_aux("era"):
    run_range = config_inst.campaign.x.run_ranges[dataset_inst.x.era]

If this is useful to a general audience, this information could of course be added to the campaigns directly in the cmsdb.

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

No branches or pull requests

2 participants