Propagation of weights and weight names from event generation to DAOD/PHYS

As GIT metadata contact I started my position by looking into what the current status is for the weight and weight names metadata.

Overview of which group is responsible for what part in the chain

Legend:

• dashed rectangles indicate group responsibility
  • the group name is shown in the top left or top right corner
• large blue arrows indicate the propagation of information
• small blue arrows indicate what framework/software gets called in that step
  
  

Overview of how the propagation looks like at the moment

Legend:

• blue arrows indicate how the information gets propagated (in that sense the arrows for PMGTruthWeightTool and checkMetaSG.py are showing in the wrong direction, because they only read the information)
• black rectangles show the different file formats
• orange rectangles show objects supplied by the event generators
• red rectangles show persistent objects within EVNT, HITS, etc. stating the type and part of the name in parenthesis
• yellow rectangles show tools which are used to read out information

See these presentations for more information:

• latest presentation in DCC meeting of 03.04.2020
• presentation in GIT meeting of 20.03.2020

Issues to be worked on:

General

• AMI weight name storage
  • wished by:
  • worked on by: AMI
  • priority:
  • next steps:

• find out whether/how it is possible to add weights at AOD to DAOD step
  • wished by: Louie
  • worked on by:
  • priority:
  • next steps:

Missing sanity checks

• checks that all weights and weight names correctly propagated from step to step
  • details:
    • Check number of weights in each production step?
  • wished by: Louie, Marjorie
  • worked on by:
  • priority:
  • next steps:

• checks that all requested weights and weight names are included on EVNT and AOD level
  • wished by: Tim
  • worked on by:
  • priority: maybe nice to have? - not sure whether already there
  • next steps:

Duplicated information in the persistent objects

• weight names stored multiple times
  • details:
    • what to do with metadata names in xAOD format (GIT, ASG, Generators)
  • wished by:
  • worked on by: Tim
  • priority: High
  • next steps: check with ASG which formats can be dropped/what are they used for

• weights stored multiple times
  • details:
    • do we need two weight copies in two fromats: pileupevtinfo(mcEventInfo),EventInfoAuxDyn.mcEventWeights(ASG, DAOD)
  • wished by:
  • worked on by: Tim
  • priority: High
  • next steps: check with ASG which formats can be dropped/what are they used for

Code stability

• IOVMetaDataContainer is accessed in many different ways - unify them?
  • details:
    • accessed via AthFile in checkMetaSG.py
    • accessed via HepMCWeightSvc in Reco_tf
    • accessed via AsgMetadataTool in PMGTruthWeightTool
  • wished by: Tim
  • worked on by: Tim
  • priority: High
  • next steps: ask e.g. ASG who is responsible for what - check whether something can get unified
• Weights and weight names are stored differently in the different production steps - Really necessary? Possible to reduce?
  • details:
    • what to do with metadata names in xAOD format (GIT, ASG, Generators)
    • delete some empty containers at DAOD_PHYS?
  • wished by: Louie
  • worked on by: Tim
  • priority: High
  • next steps: check with ASG which formats can be dropped/what are they used for

• next issue
  • wished by: to be asked if more information on the aim are needed
  • worked on by: who works on it
  • priority: how important is it compared to other tasks on this page
  • next steps: what are the next concrete steps which need to be done