Skip to content

Dataset order not applied to signal #25

@eshwen

Description

@eshwen

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions