led#
LED in front of selected camera pixels, to test trigger definitions.
$ obdeect sources led --camera-file cam.dat --use "0 1 2" --photons 500 > led.pst
$ obdeect sources led --camera-file cam.dat --use-trg-all --list-only
Frame
camera(C). The LED sits at the pixel centre(x, y, 0)in the pixel-file coordinates, pointing(0, 0, -1). The photons already lie on the camera plane.Give exactly one of
--use,--use-trg-rand Nor--use-trg-all.--list-onlyprints the pixel combinations ((@)labels) and writes no photons.
Options#
Option |
Default |
Meaning |
|---|---|---|
|
required |
camera definition ( |
|
pixels: ids, |
|
|
N random trigger groups |
|
|
all trigger groups |
|
|
|
pixels per event |
|
N distinct random pixels per event (uses |
|
|
off |
also fire pre-sum slaves |
|
|
events per combination |
|
|
photons per pixel |
|
|
photons per bunch (at least 1) |
|
|
fiducial radius [cm] |
|
|
as in flasher |
|
|
run keys |
|
off |
print |
|
accepted; the program prints nothing else |
|
|
|
seed of the random choices and photons |
|
stdout |
output file |
Input rules#
Pixel lists accept ids,
+(required),[..](slaves) and%(comment).Trigger lists: the text after
ofis used;[..]is removed unless--slaves.--use-fileis not supported.A non-isotropic pixel outside the fiducial sphere is rejected (no camera-plane disc target).
Events: all listed pixels (no
--require),--randomdraws, or one event per combination of--requirepixels in increasing order. Required (+) pixels are always lit.