rename jettoolbox_cfg.py to testJettools_cfg.py to avoid confusion

[alefisico]

New version is a stand-alone package here: https://github.com/cms-jet/JetToolbox

[cmsbuild]

A new Pull Request was created by @alefisico (Alejandro Gomez Espinosa) for CMSSW_7_5_X.

removing jettoolbox from CMSSW

It involves the following packages:

RecoJets/JetProducers

@cmsbuild, @cvuosalo, @nclopezo, @slava77 can you please review it and eventually sign? Thanks.
@rappoccio, @jdolen, @ahinzmann, @TaiSakuma, @yslai, @nhanvtran, @schoef, @mariadalfonso 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.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[slava77]

this was a good test file to check jet-related algorithms not included in standard workflows.
What can we use now during integration?

[ahinzmann]

The motivation to remove it from the release it is that it is outdated and causes confusion, while a better version is in the works.
It is indeed useful for tests. How about just renaming it to testJetTools_cfg.py

[slava77]

What prevents you from having this file more up to date with the release?
Unless the file goes out of date on a 1-week time scale all the time, the release schedule is typically frequent enough to be up-to-date.

[ahinzmann]

It is up-to-date in terms of algorithms and code in CMSSW and we should be keep it like this for test.
However, the user interface (using python functions rather than a simple config) develops.

[slava77]

OK, so this PR should be updated then, renaming the file to testJetTools_cfg.py, right?

[slava77]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.

[cmsbuild]

Pull request #9291 was updated. @cmsbuild, @cvuosalo, @nclopezo, @slava77 can you please check and sign again.

[cmsbuild]

+1
Tested at: ee51c17
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9291/5063/summary.html

[cvuosalo]

+1

For #9291 05acff6

Renaming file to reflect that its package has become stand-alone. No changes to standard workflows should occur.

Jenkins tests against baseline CMSSW_7_5_X_2015-05-26-2300 show no significant differences, as expected.

[cvuosalo]

@alefisico: Please revise the title of this PR to reflect the fact that the file is being renamed, not removed.

[cmsbuild]

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

[davidlange6]

+1