You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 24, 2025. It is now read-only.
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.
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)
as it seems, people have been creative in merging the two concept, while they have separate meanings.
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 ,
cmsPdmV/mcm/json_layer/request.py
Line 3192 in 74b5157
cmsPdmV/mcm/json_layer/request.py
Line 3180 in 74b5157
where
_output_tiers_is actually_output_contents_.We have to look at this closely to choose wether we:
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)