A list of items to discuss:
- Implementation of using "single tag” containers for
derivations (and specifically the corresponding output
container):
- In detail: rolling out the new AMI tag convention to the
DAODs in general? Currently only the top group get four
tag (e, s/a, r, p) container names, with the rest reverting
to the multi-tag nomenclature.
- Some technical items:
- Lost provenance for some new "single tag” containers
in AMI
- Awkward “recon.AOD" naming for current “single tag”
containers (not ideal to use a “working container” as
the final storage)
- Lost AMI metadata from merge moving back into
unmerged
EVNT (https://its.cern.ch/jira/browse/ATLASAMI-142)
- Inconsistent sub campaign treatment
(https://its.cern.ch/jira/browse/ATLASAMI-145)
- What to do with NTUP_PILEUP?
- Example:
Currently, we have for the AODs e.g:
mc16_13TeV.364452.Herwig7EvtGen_H7UE_NNPDF30nlo_jetjet_JZ9.recon.AOD.e5989_s3126_r10201
but then the corresponding NTUP_PILEUP container is:
mc16_13TeV.364452.Herwig7EvtGen_H7UE_NNPDF30nlo_jetjet_JZ9.merge.NTUP_PILEUP.e5989_e5984_s3126_r10201_r10210_p3384_p3385
whereas, in principle, we could have:
mc16_13TeV.364452.Herwig7EvtGen_H7UE_NNPDF30nlo_jetjet_JZ9.deriv.NTUP_PILEUP.e5989_s3126_r10201_p3384
in parallel to what is done for the DAODs.