Skip to Content.
Sympa Menu

star-fcv-l - Re: [Star-fcv-l] 3 GeV p/d/t Embedding Request

star-fcv-l AT lists.bnl.gov

Subject: STAR Flow, Chirality and Vorticity PWG

List archive

Chronological Thread  
  • From: Cameron Racz <cracz001 AT ucr.edu>
  • To: Daniel Cebra <cebra AT physics.ucdavis.edu>
  • Cc: "STAR Flow, Chirality and Vorticity PWG" <star-fcv-l AT lists.bnl.gov>
  • Subject: Re: [Star-fcv-l] 3 GeV p/d/t Embedding Request
  • Date: Wed, 28 Dec 2022 10:37:54 -0600

Hi Daniel,

Yeah that makes sense! I’ll figure out the max pT and rapidity that is actually necessary and get it updated.

On Tue, Dec 27, 2022 at 7:51 PM Daniel Cebra <cebra AT physics.ucdavis.edu> wrote:
Hello Cameron,
   For protons, please look at embedding request 20202801. This goes to pT = 0 and covers the rapidity and phi range, and bad run list that you need.

   For the deuterons and tritons, 3He and 4He, if you are really interested in the pT region below 0.6 GeV, your embedding request is from 0 to 6 GeV, so only ten percent of the embedding added new information. You should probably check the rapidity limits for the light nuclei, as you are unlikely to get much additional acceptance beyond the previous embedding. You can probably make a much more efficient ask.

Regards, Daniel

On Tue, Dec 27, 2022 at 5:02 PM Cameron Racz <cracz001 AT ucr.edu> wrote:
Hi Daniel,

This embedding is actually to extend into lower pT rather than higher. The old embedding tracks had a minimum pT of 0.6 and we’d like to go lower because that’s where our region of interest is likely going to be for these particles. Also the rapidity region was a bit too small as well, but this request is mostly so we can get efficiency values at low pT.

On Tue, Dec 27, 2022 at 6:46 PM Daniel Cebra <cebra AT physics.ucdavis.edu> wrote:
Hello Cameron,
   I am not sure why we would need embedding just to extend the pT range. The TPC tracking efficiency does not change once the tracks are a certain degree of straight. The inefficiencies come from the sector and pad geometries, and for high pT tracks the efficiency does not change. The inefficiencies at high pT come from the sector boundaries.

Regards, Daniel

On Mon, Dec 19, 2022 at 12:42 PM Cameron Racz via Star-fcv-l <star-fcv-l AT lists.bnl.gov> wrote:
Hi convenors,

I would like to make an amendment to this embedding request and just add He3 and He4 to it with the same pT, rapidity, and phi specifications as the other particles in the first email. 

Thank you,

Cameron Racz
Ph.D. Candidate 
Heavy-ion Physics Group
University of California, Riverside






On Dec 9, 2022, at 5:52 PM, Cameron Racz <cracz001 AT ucr.edu> wrote:

Hello convenors,

I would like to request an embedding for protons, deuterons, and tritons at sqrt{s_{NN}} = 3.0 GeV FXT. The details are very similar to a previous embedding (ID 20202802) but this time I would like the pT and rapidity to be extended for these particles, and the bad run list will be included as well. Below are the details:


Request type: Standard Embedding request (particle in real events)

Beam: Au+Au 3GeV FXT Run 18
TriggerSetup: production_3p85GeV_fixedTarget_2018
Library: SL20d
Production: P19ie
Run Numbers: 19151029 - 19155022
Triggers: bbce_tofmult1 (620052)

10% of Multiplicity
500K events each
Particles: proton, deuteron, triton
Flat in 0 < pT < 6 GeV
Flat in -2 < rapidity < 0 (LAB rapidity)
Flat in 0 < phi < 2 pi
Z vertex: 198 < vZ < 202 cm

Bad Run List:

badRunList[24]={19151029,19151045,19152001,19152078,19153023, 19153032,19153065,19154012,19154013,19154014,

19154015,19154016,19154017,19154018,19154019,19154020,19154021,19154022,19154023,19154024,19154026,19154046,19154051,19154056}


Please let me know if any more info is necessary.

Thanks,

Cameron Racz
Ph.D. Candidate 
Heavy-ion Physics Group
University of California, Riverside







_______________________________________________
Star-fcv-l mailing list
Star-fcv-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-fcv-l
--
Cameron Racz
--
Cameron Racz



Archive powered by MHonArc 2.6.24.

Top of Page