star-fst-l AT lists.bnl.gov
Subject: Star-fst-l mailing list
List archive
- From: Carl Gagliardi <c-gagliardi AT tamu.edu>
- To: "'Aschenauer Elke-Caroline'" <elke AT bnl.gov>, "'STAR sTGC upgrade'" <star-stgc-l AT lists.bnl.gov>, "'Star-fst L'" <star-fst-l AT lists.bnl.gov>, "'Carl Gagliardi'" <c-gagliardi AT tamu.edu>, "'Flemming Videbaek'" <videbaek AT bnl.gov>, "'Van Buren, Gene'" <gene AT bnl.gov>
- Subject: Re: [Star-fst-l] low luminosity running
- Date: Mon, 17 Jan 2022 13:50:16 -0600
Hi Elke—
As I said during the call, I hadn’t expected that C-AD could take the per bunch current down as low as 1 x 10^{10} per bunch without running into machine instabilities. So I wanted to check how many bunches would be needed. Here’s my arithmetic:
1 x 10^{10}/bunch is 1/20 of nominal. I presume this translates into reducing the collision rate by a factor of 1/400. For a nominal 4+/- MHz NSD collision rate, that corresponds to 10 kHz. For a nominal 400+/- kHz ZDC rate, that corresponds to 1 kHz. These are the total rates I proposed, but spread over 100 active bunches, instead of 6. Thus, the number of collisions per bunch crossing would be ~0.1%, which is smaller than it needs to be. (Other systematics will be much bigger than that.)
Having a modest gap between the active bunches can be useful when looking at the scaler rates. Thus, I think a good “compromise” would be:
2 x 10^{10}/ bunch with a 28 bunch fill. This should give four times as many collisions per bunch (but still only ~0.5%/bunch) with 1/4 as many bunches. The total rates should be as above, and should be plenty to saturate the DAQ system bandwidth without producing undo pile up. Overall, this would be a better optimization than a 6 bunch fill with higher currents per bunch.
Hope this is clear! Carl
From: Aschenauer Elke-Caroline <elke AT bnl.gov>
Based on the input I received I complied the following slides to be discussed today in the trigger-board meeting. Sent me comments by 12:45 pm Thanks elke ZjQcmQRYFpfptBannerStart
ZjQcmQRYFpfptBannerEnd Based on the input I received I complied the following slides to be discussed today in the trigger-board meeting. Sent me comments by 12:45 pm
Thanks elke
|
-
[Star-fst-l] low luminosity running,
Aschenauer Elke-Caroline, 01/13/2022
-
Re: [Star-fst-l] low luminosity running,
Carl Gagliardi, 01/14/2022
-
Re: [Star-fst-l] low luminosity running,
Carl Gagliardi, 01/14/2022
-
Re: [Star-fst-l] low luminosity running,
videbaek, 01/14/2022
-
Re: [Star-fst-l] low luminosity running,
Ye, Zhenyu, 01/14/2022
- Re: [Star-fst-l] low luminosity running, videbaek, 01/14/2022
-
Re: [Star-fst-l] low luminosity running,
Ye, Zhenyu, 01/14/2022
-
Re: [Star-fst-l] low luminosity running,
videbaek, 01/14/2022
-
Re: [Star-fst-l] low luminosity running,
Carl Gagliardi, 01/14/2022
-
Re: [Star-fst-l] low luminosity running,
Aschenauer Elke-Caroline, 01/17/2022
-
Re: [Star-fst-l] low luminosity running,
Carl Gagliardi, 01/17/2022
- Re: [Star-fst-l] low luminosity running, Aschenauer Elke-Caroline, 01/17/2022
- Re: [Star-fst-l] low luminosity running, Carl Gagliardi, 01/17/2022
-
Re: [Star-fst-l] low luminosity running,
Carl Gagliardi, 01/17/2022
-
Re: [Star-fst-l] low luminosity running,
Carl Gagliardi, 01/14/2022
Archive powered by MHonArc 2.6.24.