[d2n-analysis-talk] replay_det_BB.C: error messages and scalers
Diana Parno
dseymour at andrew.cmu.edu
Mon Mar 1 19:09:53 EST 2010
Hello all,
I've got some weird behavior when I try to run replay_det_BB(1521,-1) in
my analyzer. (Everything lives on /home/dseymour/d2n-replay/replay on the
d2n machine.)
When I first tried to run it today, I got the following error messages,
seemingly every event:
Warning in <THaBPM::"urb.BPMA"::Decode()>: Number of fired Channels out of range. Setting beam position to nominal values
Warning in <THaBPM::"urb.BPMB"::Decode()>: Number of fired Channels out of range. Setting beam position to nominal values
Warning in <THaRaster::"rb.Raster"::Decode()>: Number of fired Channels out of range. Setting beam position to nominal values
Warning in <THaADCHe3Spin::"he3.ladc1"::Decode>: Invalid Spin State Signal for he3.ladc1. @ event #19174
Spin Up ADC = 99999999999999997748809823456034029568.000000 ; Spin Down ADC = 99999999999999997748809823456034029568.000000
Warning in <THaADCHe3Spin::"he3.ladc2"::Decode>: Invalid Spin State Signal for he3.ladc2. @ event #19174
Spin Up ADC = 99999999999999997748809823456034029568.000000 ; Spin Down ADC = 99999999999999997748809823456034029568.000000
Error in <THaG0Helicity::"g0hel.L"::Decode>: Error decoding helicity data.
I thought this was odd, especially since the he3 block is not referenced
anywhere in my .odef file. However, the analysis seemed to work (at least,
the part I was interested in): my BBITE tree showed 301 events for the
scalers and they made sense.
I tried commenting out the rb.* and urb.* blocks in my .odef file, since
those seemed to be generating errors. When I reloaded the analyzer, the
replay ran with no error messages -- which I thought odd because I
couldn't see how the he3 and g0hel blocks could be affected by rb.* and
.urb*. However, when the replay finished, the BBITE tree was empty -- no
entries.
Then I tried reversing my latest change, uncommenting the rb.* and urb.*
blocks. Now I get one set of error messages at the beginning of the run:
THaOutput::Init: WARNING: Block urb.* does not match any variables.
There is probably a typo error...
THaOutput::Init: WARNING: Block rb.* does not match any variables.
There is probably a typo error...
... but there was no every-event error message like there was before, for
the wrong number of channels firing, etc etc. The scaler tree is still
empty.
So, I have a couple of questions:
- Did the central DB change in the last half hour or so?
- Is there any other reason this error-message behavior would change so
radically?
- Is there any reason the urb.* or rb.* blocks would affect the he3 spin
signal, and so forth?
- Does anyone have any idea where my BBITE entries might have gone? I'm
certainly still asking for them in the .odef file!
- Has anyone else seen behavior like this?
I'd really appreciate any advice any of you can offer.
Cheers,
Diana
More information about the d2n-analysis-talk
mailing list