~testbeam/svx/svx_monitor
svx_monitor : - takes data from the stream svx_monitor <file name> - takes data from the fileThe recommended number of events is 5000.
When the task is finished, enter paw and give the command
exec beamto look at the histograms. The detector number and the measured projection are indicated for each plane. You can compare your plots with some reference histograms (5000 beam triggers). The spikes you can see for some of the detectors are just a feature of our readout electronics, the SVX-H chips.
svx_trigger.ffr
trigmask 768
beamtrig 64
acttrig 0
pedtrig 0
noisetrig 768
Start the task with the command:
svx_monitor : or
svx_monitor <file name>The recommended number of events is 1000.
When the task is finished, enter paw and give the command
exec noiseto look at the histograms. You can compare your plots with some reference histograms (1000 noise triggers) The second star is not in its best shape, and the absence of about half of detector 10 is known.
If you notice discrepancies between your distributions and the reference ones, please inform one of the silicon experts. If the discrepancy is very large (e.g. the noise distributions present large groups of channels constantly firing, or the beam profiles are highly distorted by noise) call one of the experts. Otherwise just send us a mail and we will recalibrate the detectors as soon as possible! Night calls should be limited to real emergencies.
Troubleshooting:
Most of the problems of the silicon are cured by stoping and starting the
run.
COMPASS home
|
test
beam |
general
|
schedule
|
activities
|
contact
|
documentation