Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alcareco ecal trg #14684

Merged
merged 1 commit into from
Jun 28, 2016
Merged

Alcareco ecal trg #14684

merged 1 commit into from
Jun 28, 2016

Conversation

shervin86
Copy link
Contributor

@shervin86 shervin86 commented May 30, 2016

A new ALCARECO for ECAL trigger studies.
PrimaryDataset: ZeroBias and DoubleEG

To be produced only for few runs on-demand.

@emanueledimarco @nancymarinelli are interested in this PR

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @shervin86 for CMSSW_8_1_X.

It involves the following packages:

Calibration/EcalAlCaRecoProducers
Configuration/AlCa
Configuration/EventContent
Configuration/PyReleaseValidation
Configuration/StandardSequences

@ghellwig, @franzoni, @cerminar, @fabozzi, @cmsbuild, @srimanob, @mmusich, @hengne, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @makortel, @GiacomoSguazzoni, @rovere, @argiro, @Martin-Grunewald, @tocheng, @VinInn, @dgulhan this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@mmusich
Copy link
Contributor

mmusich commented May 30, 2016

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 30, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/13256/console

@cmsbuild
Copy link
Contributor

-1

Tested at: 05999d6

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14684/13256/summary.html

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following worklfows:
25.0 step3

runTheMatrix-results/25.0_TTbar+TTbar+DIGI+RECOAlCaCalo+HARVEST+ALCATT/step3_TTbar+TTbar+DIGI+RECOAlCaCalo+HARVEST+ALCATT.log
1000.0 step2
runTheMatrix-results/1000.0_RunMinBias2011A+RunMinBias2011A+TIER0+SKIMD+HARVESTDfst2+ALCASPLIT/step2_RunMinBias2011A+RunMinBias2011A+TIER0+SKIMD+HARVESTDfst2+ALCASPLIT.log

SelectEvents = cms.vstring('pathALCARECOEcalTrg'),
),
outputCommands = cms.untracked.vstring(
'CaloTowersSorted_towerMaker_*',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shervin86 you need to include the keep and drop statements.

----- Begin Fatal Exception 30-May-2016 14:57:08 CEST-----------------------
An exception of category 'Configuration' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing module: class=PoolOutputModule label='ALCARECOStreamEcalTrg'
Exception Message:
Invalid statement in configuration file
In OutputModule parameter named 'outputCommands'
Rule must specify 'keep ' or 'drop ' and also supply a pattern.
This is the invalid output configuration rule:
    CaloTowersSorted_towerMaker_*
Exception thrown from ProductSelectorRules::Rule
----- End Fatal Exception -------------------------------------------------

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes.... just realized. I've fixed that and running the runTheMatrix to make sure now there are no other problems....

                        Shervin

On Mon, 30 May 2016, Marco Musich wrote:

Date: Mon, 30 May 2016 18:49:48 +0200
From: Marco Musich notifications@github.com
Reply-To: cms-sw/cmssw
<reply+0045c225ea74ca34bd4e55dd767cf9506c657639cb178a8f92cf000000011364312
c92a170ce03e13aca@reply.github.com>
To: cms-sw/cmssw cmssw@noreply.github.com
Cc: shervin86 shervin@cern.ch, Mention mention@noreply.github.com
Subject: Re: [cms-sw/cmssw] Alcareco ecal trg (#14684)

@@ -0,0 +1,96 @@
+import FWCore.ParameterSet.Config as cms
+
+OutALCARECOEcalTrg_noDrop = cms.PSet(

  • put this if you have a filter

  • SelectEvents = cms.untracked.PSet(
  •    SelectEvents = cms.vstring('pathALCARECOEcalTrg'),
    
  • ),
  • outputCommands = cms.untracked.vstring(
  •    'CaloTowersSorted_towerMaker_*',
    

@shervin86 you need to include the keep and drop statements.

----- Begin Fatal Exception 30-May-2016 14:57:08 CEST-----------------------
An exception of category 'Configuration' occurred while
  [0] Constructing the EventProcessor
  [1] Constructing module: class=PoolOutputModule label='ALCARECOStreamEcalTrg'
Exception Message:
Invalid statement in configuration file
In OutputModule parameter named 'outputCommands'
Rule must specify 'keep ' or 'drop ' and also supply a pattern.
This is the invalid output configuration rule:
   CaloTowersSorted_towerMaker_*
Exception thrown from ProductSelectorRules::Rule
----- End Fatal Exception -------------------------------------------------

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/cms-sw/cmssw/pull/14684/files/05999d6d54d5abf13199e6f5d8e362b14111654b#r65092298

@cmsbuild
Copy link
Contributor

Pull request #14684 was updated. @ghellwig, @franzoni, @cerminar, @fabozzi, @cmsbuild, @srimanob, @mmusich, @hengne, @davidlange6 can you please check and sign again.

@mmusich
Copy link
Contributor

mmusich commented May 31, 2016

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 31, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/13288/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@shervin86
Copy link
Contributor Author

urra'

@cmsbuild
Copy link
Contributor

@mmusich
Copy link
Contributor

mmusich commented Jun 27, 2016

+1

@fabozzi
Copy link
Contributor

fabozzi commented Jun 28, 2016

+1

@davidlange6 davidlange6 merged commit 35e1f91 into cms-sw:CMSSW_8_1_X Jun 28, 2016
@fabozzi
Copy link
Contributor

fabozzi commented Aug 5, 2016

Hello, we are experiencing failures due to this backport of EcalTrg to 80X.
The failures showed up in relval MC:
https://hypernews.cern.ch/HyperNews/CMS/get/relval/5632.html

and worst thing, in a re-reco wf on ZeroBias:
https://hypernews.cern.ch/HyperNews/CMS/get/dataopsrequests/14436/1.html

Unless you have better proposals, I think we should remove the EcalTrg path from autoAlca
and relvals.

@mmusich @shervin86 @davidlange6

@davidlange6
Copy link
Contributor

It seems so - but is it obvious why this wasn't seen in 81x relvals? (or was it just ignored there?)

@mmusich
Copy link
Contributor

mmusich commented Aug 5, 2016

no, simply the run number probed in the RelVals was covered by the correct AlCaRecoTriggerBit.

@fwyzard
Copy link
Contributor

fwyzard commented Aug 5, 2016

On 5 August 2016 at 10:23, David Lange notifications@github.com wrote:

It seems so - but is it obvious why this wasn't seen in 81x relvals? (or
was it just ignored there?)

Is the global tag the same for both releases ?

.A

@mmusich
Copy link
Contributor

mmusich commented Aug 5, 2016

@fabozzi for the specific use case of the re-reco which GT are you using?

@davidlange6
Copy link
Contributor

ok - so we just need a protection against the alca crashing just because its trigger bit doesn’t happen to be in the menu (and an update to the 81x relvals to cover the region we want to use in 80x (or vis versa..)

On Aug 5, 2016, at 10:27 AM, Marco Musich <notifications@github.commailto:notifications@github.com> wrote:

no, simply the run number probed in the RelVals was covered by the correct AlCaRecoTriggerBit.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com//pull/14684#issuecomment-237787288, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEzyw9pd-A6pS0X38s-oGA1v3rt1Q9Jtks5qcvPtgaJpZM4IpwUu.

@mmusich
Copy link
Contributor

mmusich commented Aug 5, 2016

@davidlange6 I agree

@fabozzi
Copy link
Contributor

fabozzi commented Aug 5, 2016

@mmusich
this was the rereco on 2015E, so we used the Prompt GT

@mmusich
Copy link
Contributor

mmusich commented Aug 5, 2016

@fabozzi this explains the failures, since it's not deployed in the standard alcareco matrix we deploy at tier0 the trigger bit is not set in the Prompt GT.
Backporting the IOV back in time to cover 2015E will require a different GT.

@mmusich
Copy link
Contributor

mmusich commented Aug 5, 2016

So, we just discussed with @fabozzi and we agreed the following:

  • the re-reco (that is urgent) can be resubmitted removing the AlCa producer from the matrix (N.B. this is needed only because the Prompt GT was used)
  • in both 80x and 81x I will update the Global Tags to cover the MC use-case
  • in both 80x and 81x the relval data Run2 is already covered by an IOV, and all future and past runs are OK ----> no action needed

@fwyzard
Copy link
Contributor

fwyzard commented Aug 5, 2016

ok - so we just need a protection against the alca crashing just because its trigger bit doesn’t happen to be in the menu (and an update to the 81x relvals to cover the region we want to use in 80x (or vis versa..)

process.ecalTrgHLT.throw = False

@mmusich
Copy link
Contributor

mmusich commented Aug 5, 2016

@fabozzi, the issue in 80X MC relvals is hopefully solved at
#15373

@shervin86 shervin86 deleted the ALCARECOEcalTrg branch November 25, 2016 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants