THIS PAGE DOCUMENTS COMMON WARNINGS AND ERROR MESSAGES SEEN IN THE OLD HIGHLAND. SOME OF THEM WILL BE COMMON TO HIGHLAND2 BUT SOME OTHERS PROBABLY NOT. THIS PAGE SHOULD BE REVIEWED ONCE WE HAVE MORE INFORMATION.

Each message is categorised according to the severity of the problem, and when the error occurs:

Compilation: Errors when trying to compile your analysis package
Runtime: Errors when running your analysis (RunXXXAnalysis.exe)
Analysis-time: Errors when analysing the highland output (using the DrawingTools, for example)

Major problems

Compilation: Undefined reference to vtable

Message:

#CMT---> building application
../amd64_linux26/RunNumuCCQEHighAngleAnalysis.exe
../amd64_linux26/RunNumuCCQEHighAngleAnalysis.o: In function `main':
RunNumuCCQEHighAngleAnalysis.cxx:(.text+0xb2): undefined reference to
`NumuCCQEHighAngleAnalysis::NumuCCQEHighAngleAnalysis(int, char**)'
../amd64_linux26/RunNumuCCQEHighAngleAnalysis.o: In function
`NumuCCQEHighAngleCuts::~NumuCCQEHighAngleCuts()':
RunNumuCCQEHighAngleAnalysis.cxx:(.text._ZN21NumuCCQEHighAngleCutsD1Ev[NumuCCQEHighAngleCuts::~NumuCCQEHighAngleCuts()]+0xf):
undefined reference to `vtable for NumuCCQEHighAngleCuts'
../amd64_linux26/RunNumuCCQEHighAngleAnalysis.o: In function
`NumuCCQEHighAngleAnalysis::~NumuCCQEHighAngleAnalysis()':
RunNumuCCQEHighAngleAnalysis.cxx:(.text._ZN25NumuCCQEHighAngleAnalysisD1Ev[NumuCCQEHighAngleAnalysis::~NumuCCQEHighAngleAnalysis()]+0xf):
undefined reference to `vtable for NumuCCQEHighAngleAnalysis'

Explanation: The most likely reason for this is that your requirements file in the cmt directory has some typos in it.

Action: Check that you have consistent captalisation when referring to your package (if your package is myPackageAnalysis, it should always be referred to as myPackageAnalysis or MYPACKAGEANALYSIS, depending on context - see the tutorial for an example). Carefully check your spelling and capitalisation!

Analysis-time: No header tree

Message:

Warning! "header" tree wasn't found - make sure you have loaded a configuration!

Explanation: This error means that your output file probably doesn't contain a header tree (you can verify this by opening the file in ROOT and typing ".ls"). The header tree is only written at the END of each analysis job, so this means that your job didn't complete successfully (either due to running out of memory, crashing, or taking too long on a batch queue).

Action: Check the output from your analysis job to see what the problem was.

Analysis-time: Invalid type

Message:

Error: Invalid type 'DataSample' in declaration of ...

Error: Invalid type 'DrawingTools' in declaration of ...

Explanation: This error occurs if you haven't sourced setup.sh in the cmt directory of your package

Action: Source $HIGHLEVELANALYSISROOT/cmt/setup.sh, then try running your macro again.

Minor problems

Runtime: No BSD

Message:

INFO: run ***, subrun ***, event *** has no beam summary data. Event will be ignored if you're using the event_quality cut.

Explanation: This message means that the event does not have any Beam Summary Data.

If you are looking at cosmic files, then this is expected
If you are using official files, then this is benign (unless you're an expert and are validating a new production!)
If you are using your own files, then this might be a problem.

Action: If you've produced your own beam spill files and these messages appear for every event, then you will not be able to check whether then beam quality was good. You should run the nd280-get-beam command in $OABEAMDATAROOT/src to download the BSD files (warning - they're quite big!). You will then need to regenerate your oaAnalysis files.

Runtime: No RooTracker information

Message:

!!!! NNVtx 0 NTruthVertices ***

truthvertex not match to rootracker vertex!!!!!

Explanation: This message is caused by Bug 925. The final event in a MC file may be empty, but in Production 5 oaAnalysis would fill the true vertices and true tracks using information from the previous event. Reconstructed information and RooTrackerVtx information was still empty (as it should be). This means that highland sees an AnaTrueVertex in the final event, but can't find the associated RooTrackerVtx.

Action: No action needs to be taken. You should be aware that the truth information in the final event of MC files may be a duplicate of the previous event. This happens for ~9% of files, so affects ~0.002% of events overall. No analyses using Production 5 files should be sensitive to this issue.

Benign warnings

Runtime: TTruthUtils

Message:

[ERROR][TTruthUtils] Trajectory was not found - it is not present in the oaAnalysis file

Explanation: This message is printed to screen a lot if you are using nd280AnalysisTools v0r7p1 or earlier. The message is benign, but very annoying and can hide other warnings in the large log file.

Action: Upgrade to a new version of nd280AnalysisTools, preferably v1r7 or higher. You will then need to re-compile.

Analysis-time: No dictionary for class

Message:

Warning in <TClass::TClass>: no dictionary for class ND::JNuBeamFlux is available
Warning in <TClass::TClass>: no dictionary for class ND::NRooTrackerVtx is available
Warning in <TClass::TClass>: no dictionary for class ND::RooTrackerVtxBase is available

Explanation: These three warnings are expected when opening your output file. We don't interact with these classes, so don't require the dictionaries. If you only get warnings about these classes, then there is no problem.

Action: If you get warnings for other classes, then you should source setup.sh in highland/highLevelAnalysis/vXrX/cmt and try again.

Analysis-time: Attempt to divide histograms with different bin limits

Message:

Warning in <TH1F::Divide>: Attempt to divide histograms with different bin limits

Explanation: In highland v0r17 and earlier, the efficiency and purity vs. cut plots did not satisfy all of ROOT's requirements for avoiding this warning (although enough requirements were satisfied that there wasn't really a problem - the warning was benign).

Action: If you're using highland v0r17 or earlier, you should really upgrade. If you're using a newer version and still see this warning when using the DrawingTools, please inform the highland developers.