STAR Peripheral Collisions Datasets

Peripheral Collisions

Datasets from Summer, 2000 run

This is a list of datasets taken during the Summer, 2000 STAR Run. All are 60-bunch runs.

Run Number

Date, Start/Stop times (PST)

Trigger Used / (filename)

No. of Events L0/L3

Blue/Yellow intensity (10^6)

ZDC Rate (Hz) @ start/end of the run

Note

Note: click on the run number to find out more about location of the .daq and DST files for that run

1235029

Aug 22, 17:49/18:18

PC4t/ tpc_rich_pc4

10008 / NA

14360 / 8479

16 / 28

TPC, Rich

   

1237054

Aug 24, 17:13/17:23

PC4t/ tpc_rich_pc4

4199 / NA

10475 / 17574

47 / 47

L3 first try, error in run, tpc svt rich

1237057

Aug 24, 17:36/17:50

PC4t/ tpc_rich_pc4

??? / 378

10345/ 17341

47 / 45

Tpc svt rich, L3 used for triggering

   

1241042

Aug 28, 12:47/23:09

PC4t/ tpc_rich_pc4

???? / 662

11000 / 7000

8 / 3

Run stopped for SCSI failure

   

1242020

Aug 29, 12:35/12:58

PC4t/ tpc_rich_pc4

29186 / 1642

12591 / 21996

80 / 69

Error in run (no ENDRUN)

1242023

Aug 29, 13:19/13:53

PC4'/ tpc_pc4

38900 / 2092

12086 / 21250

60 / 41

TPC only, error in run

1242026

Aug 29, 14:07/15:19

PC4' / tpc_pc4

???? / 3981

10268 / 17800

35 / 25

TPC only

1242029

Aug 29, 15:29/16:02

PC4'/ tpc_pc4

33000 / 1603 , only 1200 good evts

10199 / 17454

23 / 20 (15:50/15:54-no ZDC trigs at all)

TPC only, TPC failed in last 5 min

1242030

Aug 29, 16:11/17:07

PC4'/ tpc_pc4

????? / 2601

9749 / 16453

20 / 20

TPC

1242032

Aug 29, 17:12/17:24

PC4'/ tpc_pc4

10309 / 528

9031 / 14752

20 / 16.7

TPC

   

1246022

Sep 02, 09:19/09:31

PC4' /tpc_rich_pc4

?? / 1459

14949 / 19853

50 / 47

TPC svt rich. Stop for trig. problems

1246036

Sep 02, 17:47/20:00

PC4' / tpc_rich_pc4

?? / 7139

15259 / 17928

49 / 33

Tpc, rich, svt

1246037

Sep 02, 20:03/21:17

PC4' / tpc_rich_pc4

?? / 3314

13309 / 13290

30 / 22

same

 

 

Click here to get information on the earlier runs



Trigger Conditions:

"pc4" trigger . This trigger was optimized to select 2-prong, back to back events, while rejecting as much background as possible. It was implemented by re-programming the lookup tables in the DSMs in Level 0 of the trigger. The CTB slat ADCs were the relevant inputs. The CTB slats were divided into 4 groups:

Quadrant

CTB Slats (z>0)

CTB slats (z<0)

Top Veto

51-60, 1-5

111-120 & 61-65

North Side

36-50

66-80

South Side

6-20

96-110

Bottom Veto

21-35

81-95

These lookup table values were summed by "coarse pixels." Each coarse pixel measures 90 degrees (in phi) by 1/2 unit of rapidity. The coarse pixel boundaries are the horizontal and vertical lines, with 4 groups labelled "top north", "bottom north", "top south" and "bottom south." The LUT outputs in each coarse pixel were summed, with the following results:

Coarse Pixel Sum

LUT Output (North Side)

LUT Output (South Side)

0-2

0

0

3-9

1

4

>10

17

17

These LUT outputs were then summed in the final summing DSM. Events with 4 < Sum < 11 were accepted. This required either 1+ north & 1+ south or 2+ north hits. This was as close as we could come to requiring 1+north vs. 1+ south hits.

"pc4t" trigger . This trigger is similar to pc4. The difference is that the discriminators on the CTB slats were used. The discriminators fired if the CTB signal crossed a threshold within the 60 nsec window during which signals were expected. Only slats with 'in-time' signals were used; the others were mapped to overflow. This was done to reject events that consisted of 'leftovers' from previous events.

"pc4t' " trigger This trigger is identical to pc4t, except that the 'accept' region of the CTB was widened, with a consequent reduction in the veto region. The mappings were:

Quadrant

CTB Slats (z>0)

CTB slats (z<0)

Top Veto

53-60, 1-3

113-120 & 61-63

North Side

34-52

64-82

South Side

4-22

94-112

Bottom Veto

23-33

83-93

This was done to increase the trigger acceptance for low mass final states.

Web Manager of this page: Spencer Klein .