Revisit L1SCOUT and HLTSCOUT event contents for MC and derived dataset use cases

[haozturk]

We're introducing two new data tiers to be able clearly identify scouting data in operations [1]. In the review of the PR, it's asked not to enforce event contents of these data tiers in the repack process. [2]. We're opening up this issue not to forget to revisit the event contents for MC and derived dataset use cases

@drkovalskyi @germanfgv @davidlange6 FYI

[1] https://github.com/cms-sw/cmssw/pull/44381 [2] https://github.com/cms-sw/cmssw/pull/44381#discussion_r1524552226

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @haozturk.

@sextonkennedy, @rappoccio, @makortel, @smuzaffar, @antoniovilela, @Dr15Jones can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[makortel]

assign l1, hlt, operations

[cmsbuild]

New categories assigned: l1,hlt,operations

@Martin-Grunewald,@mmusich,@davidlange6,@rappoccio,@antoniovilela,@epalencia,@aloeliger,@fabiocos you have been requested to review this Pull request/Issue and eventually sign? Thanks

[mmusich]

We're opening up this issue not to forget to revisit the event contents for MC and derived dataset use cases

in view of https://github.com/cms-sw/cmssw/pull/44381#discussion_r1524607872 for HLT it's not clear what needs to be done. Please elaborate.

[drkovalskyi]

I think we mostly need to fix L1SCOUT. It's completely wrong as far as I understand and it needs to be updated/expanded.