Add support for 'super' data-types and implement 2024 for pp
Closes #85 (closed)
The logic is all implemented in apply_stage_3
While looping over data-types
:
- Check if the data-type is in the available ones
- If it is, proceed as normal
- If not, check for sub-data-types
Sub-data-types are defined in lumi.get_sub_data_types
. Currently it understands "2024", "Run1", "Run2", "Run3". It looks in the dict LUMI_SPLIT
to find data-types that exist in data for a given collision-type.
Back in apply_stage_3
, the list of sub-data-types is filtered for ones supported by the Sim version.
If num-events is weighted by luminosity, this is done per-"super"-data-type, e.g. specifying the data-types ["2022", "2023", "2024"]
in the same entry under samples
will result in the same set of data-types but a different number of events per request compared to specifying "Run3"
. The resulting number of events per request is also rounded to the nearest 1000 (or up to 1000 if below).
TODOs
-
Weight num-events by luminosity -
Add real lumi numbers to LUMI_SPLIT
inlumi.py
-
Add tests