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

Dataset order not applied to signal #25

Open
eshwen opened this issue Jan 30, 2020 · 0 comments
Open

Dataset order not applied to signal #25

eshwen opened this issue Jan 30, 2020 · 0 comments

Comments

@eshwen
Copy link
Contributor

eshwen commented Jan 30, 2020

When specifying certain datasets as signal in a config, i.e.,

signal: '.*SVJ*.'

and a dataset order is specified for them, i.e.,

dataset_order:
    - SVJ_3000_20_0.9_peak (Pythia)
    - 'SVJ_3000_20_0.9_peak (MadGraph)'
    - SVJ_3000_20_0.1_peak (Pythia)
    - 'SVJ_3000_20_0.1_peak (MadGraph)'
    - SVJ_1000_20_0.3_peak (Pythia)
    - 'SVJ_1000_20_0.3_peak (MadGraph)'

the order in which the datasets are plotted is not the same. Presumably, they are just ordered by yield, as can be demonstrated with the following plots produced even with the above config fragments applied.

plot_dataset dijet_mt--dijet_mt_df--weight_nominal--project_dijet_mt-yscale_log
plot_dataset ht--HT_df--weight_nominal--project_ht-yscale_log

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

1 participant