next up previous
Next: Known Limitations Up: one_event_display Previous: Getting the Event Display

Troubleshooting

A. ``I started the engine, and then the display, and after I chose the spectrometer I got this:

ERROR: evdisplay:clnt_create ABORTed for RPC program ID#

(739094520, 1)

[0x2C0DAFF8,0x 1] on machine cdaq1 What gives?''

You told it your replay was running on cdaq1 when it wasn't.

B. ``I'm sure it's looking for the analyzer correctly, but after I chose the spectrometer it crashed with a ``bus error''. Now what's wrong?''

Your engine and event display are ``out of synch''. You need to remake both so that they are both looking at the same common blocks. The easiest way to do this is to go to your replay/SRC directory and type ``make all''.

C. ``I got the dreaded Chris Bochna bug where it only displays one event (and then crashes). I realize it's a ``one event display,'' but this is ridiculous.''

You're right. All I can suggest is to try the remedy of step 2. This is the basic cure all.

D. ``I accidentally typed sntracks_fp>100 which is a valid condition, but will never be true. Do I have to start the engine and display over again?''

Nope. See the end of part 4 where it discusses how to set the timeout feature.

E. ``I'm looking at events with 2 or more tracks, and I don't see the red, or ``good'' track descrbied in part 4. I thought the code always picked a ``good'' track?''

It does. GEANT, with its world-class renddering algorithm, has drawn a very similar blue track over the red one. It's there; it's just hiding.


next up previous
Next: Known Limitations Up: one_event_display Previous: Getting the Event Display
Ioana Niculescu 2001-11-19