TWiki> CMSPublic Web>SWGuideUsersFAQ (revision 20)EditAttachPDF

Questions and answers

User Support Questions&Answers sessions can be held on Tuesdays at 9:30 am. in 40-RA-10. The next session will be held when need arises. You can use this page to submit your questions: add your question here using the following format (you can edit this page by clicking on the Edit button top right) and send me a short mail with your subject just to notify. The answers will be given in the User Support session and they will appear in this page. If you are not at CERN, and cannot attend the sessions, you can still add your questions here (indicate that you will not attend the session). Please check the existing documentation, especially the CMSWorkbook before adding your question.

Some questions (and answers) concerning common problems have been included here from the Hypernews forums.

Subject

Your name and date

Detailed description after the empty line, you can use this font for the code and file names. Add your question here (you can edit this page by clicking on the Edit button top right).

Can't compile an EDAnalyzer created with mkedanlzr

hn-cms-swDevelopment, Benedict Huckvale, 10 Oct 2006

I've done nothing more than

> eval ...
> mkedanlzr WGAnalyser
> rm -r interface/ test/ doc/
But when I try to build I get this:
benedict@lxplus061:~/w0/cmssw/CMSSW_1_0_1/src/WGAnalyser > scramv1 b -r
Resetting caches
Parsing BuildFiles
..
 /afs/cern.ch/user/b/benedict/w0/cmssw/CMSSW_1_0_1/tmp/slc3_ia32_gcc323/Makefile:536: *** target file
`src_clean' has both : and :: entries.  Stop.

Answer:

You need to put the generated package into a subsystem (i.e. NOT under /src/myAnalyzer but /src/subsys/myAnalyzer. (Shaun Ashby)
Unfortunately you might also find you need to check out an entirely new CMSSW project area. Try not to build a wrongly placed package by accident in future! (Benedict Huckvale)

Problems when removing RECO.cff from a config file

hn-cms-swDevelopment Taylan Yetkin, Sep 23,

I would like to remove reconstruction part from the others. When I remove include "Configuration/Examples/data/RECO.cff" and reconstruction from path path p = {smear_and_geant,digitization, reconstruction} which are in the exampleRunAll.cfg my naive guess is that it should work. However it does not.

Answer:

I have found what in RECO.cff depends on the ParticleDataTable: it is the HepMCCandidateProducer which is then used by different Jet and Met algorithms to do their work on the mc particles instead of the reconstructed quantities. So I guess RECO.cff is not a completely accurate name, it probably should be called MCRECO.cff since it is designed to work with MC and not actual data. To solve your problem, I suggest adding

include "SimGeneral/HepPDTESSource/data/pdt.cfi"

to your config file. (Chris Jones)

Problems accessing more than one file

hn-cms-swDevelopment, Christian Veelken, Wed, 13 Sep 2006

I have two Monte Carlo files that were produced independently and each contain 500 events. I have written a class derived from EDAnalyzer to make plots of the file content. When I run over one of the two files at a time, everything is fine, no problem. But when I run over both MC files in the same cmsRun job, cmsRun crashes when processing the first event in the second file.

Answer:

My guess is the program crashes in your EDAnalyzer. Are you by chance filling your own ROOT file from within the EDAnalyzer? If so, then other have found that when the PoolSource goes from one input ROOT file to another one their code crashes. What was determined is unless you've explicitly openned your own ROOT file and tied your histogram, ntuples, etc. to your file, then ROOT will tie those things to the first 'input' file and when that input file goes away the pointers to your histograms, ntuples, etc. then point to object that no longer exist (since ROOT deleted them when the file closed). So it look like you need to modify the ROOT calls you are making in your EDAnalyzer. (Chris Jones)

If Chris' diagnosis is correct (very likely), you can have a look at RecoEcal/EgammaClusterProducers/src/EgammaSimpleAnalyzer.cc where I had a similar problem and is now solved by correctly binding the histos and trees to my root file w/o interfering with PoolSource. (Shahram Rahatlou)

Where can I find the data?

How do I know what data is available (real data from MTCC or simulation data) and how can I access it?

Answer:

See the Workbook page on data access.

For the MTCC data (cosmic muons at CMS) see the instructions in the IGUANA web page, and in particular the data file location.

The CSA06 samples can be found using DBS tool.

For each release of the CMSSW packages, a set of of small event samples are produced which are mainly used to validate the release. Find the instructions how to access this data in the release validation samples page.

How to save cross section in the root file?

Sami Lehti, 21 Jul 2006

In an analysis containing several channels (signal+backgr), it is very helpful if some normalization constants, like cross section and preselection efficiency, can be stored in the root file. How is this done in practise (a working example would be nice)? How is the cross section read from the root file? Can the stored cross section be changed by hand afterwards? For example if i have 1M events in root file(s), and i get a new cross section from theorists, do i have to rerun the 1M events, or can i change the cross section value in the root file(s)? If yes, how?

Answer:

The mechanism to add a cross-section to the run or job (i.e. one number per run) is not yet ready, it is planned but not yet there (it is foreseen by the end of August, at the earliest)

Meanwhile, you can try the following solution which writes a number to each event.

-- KatiLassilaPerini - 13 Jul 2006

Edit | Attach | Watch | Print version | History: r54 | r22 < r21 < r20 < r19 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r20 - 2006-10-17 - KatiLassilaPerini



 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback