Transient vector bugfix

[andrewj314]

Bugfix: Added ioread rules to clear transient vectors in DataFormats/TauReco/src/classes_def_2.xml

Hypernews: https://hypernews.cern.ch/HyperNews/CMS/get/physTools/3315/1/1.html

[cmsbuild]

A new Pull Request was created by @andrewj314 (AJ Johnson) for CMSSW_7_4_X.

Transient vector bugfix

It involves the following packages:

DataFormats/TauReco

@cmsbuild, @cvuosalo, @nclopezo, @slava77 can you please review it and eventually sign? Thanks.
@jpavel this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[cvuosalo]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.

[cmsbuild]

+1
Tested at: ea1c44d
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8061/3102/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @ktf, @smuzaffar

[jpavel]

Hi @slava77 , can we backport this PR also to 72x ? (it is being used for Phys14 studies and it is there where the problem originally appeared)

[slava77]

I guess you'd want this to be in 73X as well.

Please clarify where the issue appears.
Is it affecting miniAOD workflows (the standard workflow now), or does it show up in more specific analysis tests?

I suggest to make PRs, we can sign off depending on implications.

[jpavel]

It affects the analysis workflows (only when one uses fwlite to run analysis on miniAODs). Actually, for this particular analysis it is a blocker as it prevents usage of fwlite to analyze tau strips, so analysts must write c++ code. The other problem is that the problem does not signalize itself at all and only after careful inspection we found that there are actually buggy results. So the motivation would be to prevent such a buggy results for other unaware users.

@andrewj314 Can you prepare PR's for 72x and 73x ?

[andrewj314]

You bet! I'm on it.

On Thu, Mar 5, 2015 at 2:52 PM, Pavel Jez notifications@github.com wrote:

It affects the analysis workflows (only when one uses fwlite to run
analysis on miniAODs). Actually, for this particular analysis it is a
blocker as it prevents usage of fwlite to analyze tau strips, so analysts
must write c++ code. The other problem is that the problem does not
signalize itself at all and only after careful inspection we found that
there are actually buggy results. So the motivation would be to prevent
such a buggy results for other unaware users.

@andrewj314 https://github.com/andrewj314 Can you prepare PR's for 72x
and 73x ?

Reply to this email directly or view it on GitHub
#8061 (comment).

[slava77]

ok, changes with effects on cases only downstream should be easier to propagate

[davidlange6]

+1