Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Workbook Home Introduction Account Setup QuickTour Packages Modules Unwrap page!
Event Information Tcl Commands Editing Compile and Link Run the Job Debugging
Check this page with the
W3C Validator
(More checks...)
Parameters Tcl Files Find Data Batch Analysis ROOT Tutorial

Quicktour help page

This Quicktour help page is intended to help you if you get stuck in the Quicktour. The Quicktour tutorial has been repeatedly tested, so all of the commands should work as indicated. But sometimes you might get an error message. These error messages are often confusing and not very helpful. The aim of this page is to decode these error messages and tell you what to do to fix the problem.

If you get stuck and can't find the solution to your problem on this page, you can send your problem to me, the Workbook editor. I will try to solve your problem and get back to you within a day or two. I might also add your problem and the solution to this page, to help other users.


Logging into SLAC from a remote machine

If you logged into yakut using ssh -l <username>, (or noric or tersk, similarly) and you have logged into yakut in the past, you may have had got a response like
    Someone could be eavesdropping on you right now (man-in-the-middle attack)!
    It is also possible that the host key has just been changed.
In this case it should be sufficient to note the number of the machine you are currently logged into: yakut0x, where x is a number, log out, then log in again with the command ssh -l <username> and the display should work ok.

Return to Quicktour

srtpath won't work

If you have a problem with the srtpath command, check that you have correctly performed the HEPiX part of Logging In.

Return to Quicktour

Shared libraries error

If you get an error message like:
bin/Linux24SL3_i386_gcc323/BetaMiniApp: error while loading shared libraries: cannot open shared object file: 
No such file or directory
it probably means that you have forgotten the "srtpath" command.

Return to Quicktour

No BOOT file

If you get an error message like:
No boot file has been set, either explicitly or using OO_FD_BOOT
it means that you have forgotten to set up the data path with the cond22boot command.

Return to Quicktour

"Could not find datafile" messages

If you get an error message like:

Could not find datafile "BetaPid/PidDRCLike.dat"
Could not find datafile "BetaPid/PidDRCLike.dat"
Could not find datafile "BetaPid/PidDRCLike.dat"
Could not find datafile "BetaPid/PidDRCLike.dat"
check that you are actually in workdir. (Running the job from other directories is a common error.)

Here you might occasionally (should only happen once) get an error message about BetaMiniApp being unknown. If that is the case, you should first make sure you are actually in workdir (a common error), and if that's not the problem, type

gmake setup
in workdir and this will reset the workdir configurations correctly (the symbolic links in workdir sometimes get mangled if you do a gmake clean from within workdir rather than in the release directory). Then you should be able to run the BetaMiniApp executable without problems.

Return to Quicktour

Federated Database Unavailable, waiting...

When you try to put in a collection with
   > mod talk KanEventInput
   KanEventInput> input add /store/SP/R18/001237/200309/18.6.0b/SP_001237_013238
if you see output of the form:
The Federated database [/afs/slac/g/babar-ro/objy/databases/boot/physics
/V7/ana/conditions/BaBar.BOOT] is currently unavailable - waiting...
and it's Monday 8:00 am to 4:00 pm or Thursday 4:00pm to midnight (SLAC time), you have tried to run your job during the time set aside for making data skims and general database maintenance. Do a CTRL-C to exit the job and try again later. If it isn't during these times, there is possibly a problem with the databases, give it a while to be fixed and look at hypernews to see if anyone is reporting a problem there.

Return to Quicktour

BbkDatasetTcl: "not available in bbkr18" message

If you get a message like:
BbkDatasetTcl: wrote SP-1237-Run4.tcl
Selected 209 collections, 23118000/23118000 events, ~0.0/pb, from bbkr18 at ral
****************** WARNING ******************
1027 collections (of 1236) are not available in bbkr18 at ral.
tcl file only lists local collections.
Specify BbkDatasetTcl --nolocal to include all collections.
****************** WARNING ******************
It means that BbkDatasetTcl has been configured to look for data at another host site (in this example, at RAL) instead of SLAC. To fix this, issue the following command:
/bin/rm -rf ~/.bbk
The next time you run BbkDatasetTcl, it should get set back to SLAC by default.

Return to Quicktour

Job failed

If your Quicktour job failed (either at the "gmake all" or "BetaMiniApp snippet.tcl" stage), please tell me where to find your all.log file. This will help both of us - you, because I will (try to) solve your problem, and me, because it will tell me what types of errors Workbook users are likely to encounter, and then I can fill this section with useful information.

Thanks for your help!

Back to Workbook Quicktour