The FEVTEventContent is made of RECO chunks, instead of the dedicated FEVT ones

[perrotta]

In Configuration/EventContent/python/EventContent_cff.py the AOD, RECO, etc. event contents are made of chunks of the corresponding AOD, RECO, etc. subpackages output commands. E.g.:

AODEventContent.outputCommands.extend(RecoLocalTrackerAOD.outputCommands)
AODEventContent.outputCommands.extend(RecoLocalMuonAOD.outputCommands)
AODEventContent.outputCommands.extend(RecoLocalCaloAOD.outputCommands)
AODEventContent.outputCommands.extend(RecoEcalAOD.outputCommands)
AODEventContent.outputCommands.extend(TrackingToolsAOD.outputCommands)
AODEventContent.outputCommands.extend(RecoTrackerAOD.outputCommands)
AODEventContent.outputCommands.extend(RecoJetsAOD.outputCommands)
AODEventContent.outputCommands.extend(RecoMETAOD.outputCommands)
AODEventContent.outputCommands.extend(RecoMuonAOD.outputCommands)
...

and the same for the RECOEventContent.

The same is not true for the FEVTEventContent, or FEVTSIMEventContent, e.g.:

...
FEVTEventContent.outputCommands.extend(RecoLocalTrackerRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoLocalMuonRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoLocalCaloRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoEcalRECO.outputCommands)
FEVTEventContent.outputCommands.extend(TrackingToolsRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoTrackerRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoJetsRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoMETRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoMuonRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoBTauRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoBTagRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoTauTagRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoVertexRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoEgammaRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoPixelVertexingRECO.outputCommands)
FEVTEventContent.outputCommands.extend(RecoParticleFlowRECO.outputCommands)
FEVTEventContent.outputCommands.extend(BeamSpotRECO.outputCommands)
FEVTEventContent.outputCommands.extend(L1TriggerRECO.outputCommands)
FEVTEventContent.outputCommands.extend(HLTriggerRECO.outputCommands)
FEVTEventContent.outputCommands.extend(MEtoEDMConverterRECO.outputCommands)
FEVTEventContent.outputCommands.extend(EvtScalersRECO.outputCommands)
...

The corresponding xxxFEVT.outputCommands PSet's of all those packages exist and are maintained.
To avoid confusion the FEVTEventContent should be correctly defined based on the package's FEVT contents. Or alternatively, if we wanto to stick on the package's RECO contents instead, the FEVT PSET's should be removed, together with the unnecessary maintenace of those unused stuffs.

[perrotta]

assign operations, reconstruction

[cmsbuild]

A new Issue was created by @perrotta .

@Dr15Jones, @silviodonato, @dpiparo, @smuzaffar, @makortel can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[cmsbuild]

New categories assigned: operations,reconstruction

@slava77,@fabiocos,@franzoni,@perrotta,@davidlange6,@silviodonato you have been requested to review this Pull request/Issue and eventually sign? Thanks

[slava77]

In https://github.com/cms-sw/cmssw/blame/master/Configuration/EventContent/python/EventContent_cff.py#L33
we have explicit definitions

#  FEVT (RAW+RECO), FEVTSIM (RAWSIM+RECOSIM), FEVTDEBUG (FEVTSIM+ALL_SIM_INFO), FEVTDEBUGHLT (FEVTDEBUG+HLTDEBUG)

this is how it was since 1c28d11 in 2008.

It sounds like the appropriate solution is to drop support for xxxFEVT in the subsystems.
Also, some refactoring of Configuration/EventContent/python/EventContent_cff.py based on the definition outlined there may be in order (e.g. to explicitly make FEVTEventContent to be a combination of RAWEventContent and RECOEventContent) to reduce the elaborate copy-pasting.