Skip to content
This repository was archived by the owner on Jul 24, 2025. It is now read-only.
This repository was archived by the owner on Jul 24, 2025. It is now read-only.

Confusion of DataTier and EventContent #1244

@vlimant

Description

@vlimant

as it seems, people have been creative in merging the two concept, while they have separate meanings.

  • datatier is an ornament in dbs for the dataset name
  • eventcontent is the actual list of collections that go in the output files

while people have been thinking that there's a one-to-one matching between the two. by legacy it is not. i.e. two different event content could make up datasets with the same data tier.

this crops up in https://cms-pdmv-prod.web.cern.ch/mcm/settings?prepid=datatier_input ,

task_dict['_output_tiers_'] = sequences[sequence_index]["eventcontent"]
and
tModule, tName = request.do_datatier_selection(__DT_prio[__curr_first_step], __prev_tiers)

where _output_tiers_ is actually _output_contents_.

We have to look at this closely to choose wether we:

  • properly rename output_tiers and modify datatier_input content and description.
  • leave output_tiers but fix it's assigned value, using

given #1187 the first option might be best as it also does not risk to break any current request. However, the second option gives more flexibility (the flexibility that was intended in the first place)

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