Differences between revisions 4 and 7 (spanning 3 versions)
Revision 4 as of 2009-05-06 10:04:49
Size: 854
Editor: AlexFinch
Comment:
Revision 7 as of 2009-05-06 10:12:02
Size: 1717
Editor: AlexFinch
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
attachment:eveDisp_simple1. attachment:eveDisp_simple1.jpg
Line 19: Line 20:
First with no cuts, the event looks a mess...
attachment:testbeameventnocuts.png
Line 20: Line 23:
Now apply a charge threshold cut at 10 using the "Palette" slider control: "Eve tab">Event>TripT>ED00

attachment:testbeameventchargethreshold.png

Still a mess because there are several overlapping events. Look at the timing hisrogram, the large spike at the left is from hits with
bad timing information.

attachment:testbeameventtimingnocuts.png


By selecting on the x axis, zoom in on the good timing information, now you can see the 23 buckets, and clearly see more activity in
some of them.

attachment:testbeameventtiminggoodony.png

Zoom in again on just one bin.

attachment:testbeameventtimingonebin.png

now apply this cut to the data: ND280 Event Control tab> (Timing Cuts) Apply

attachment:testbeameventchargethresholdandtimingcut.png

Some Event displays from beam running

Two easy events

First of all to get your eye in, the simplest of the simple: a paricle going straight through the centre. The way i have arranged things here has

Left upper panel
View from the side of the DsECal, (as you would see it from the counting room if the shield wasn't there)
Left lower panel
View from above the detector
Right panel
3D display, generally looking from the same side as the Left lower pannel

The beam goes from right to leftBR attachment:eveDisp_simple1.jpg

Here is a more complex example using timing cuts

I am looking at event 8 from dsecal_00010114_0000.daq.mid

First with no cuts, the event looks a mess... attachment:testbeameventnocuts.png

Now apply a charge threshold cut at 10 using the "Palette" slider control: "Eve tab">Event>TripT>ED00

attachment:testbeameventchargethreshold.png

Still a mess because there are several overlapping events. Look at the timing hisrogram, the large spike at the left is from hits with bad timing information.

attachment:testbeameventtimingnocuts.png

By selecting on the x axis, zoom in on the good timing information, now you can see the 23 buckets, and clearly see more activity in some of them.

attachment:testbeameventtiminggoodony.png

Zoom in again on just one bin.

attachment:testbeameventtimingonebin.png

now apply this cut to the data: ND280 Event Control tab> (Timing Cuts) Apply

attachment:testbeameventchargethresholdandtimingcut.png


["Calibration"]

Calibration/Testbeam/EventDisplays (last edited 2009-07-13 20:19:59 by localhost)