STAR HardProbes PWG

["Ahmed M. Hamed" <ahmed.hamed2008 AT gmail.com>]

Dear Nihar;

I think I failed in making my questions/concerns clear, so let me try again:

1) For the old version of L2gamma trigger (07,08,10,11,12); we don't mix it with the trigger patch, indeed as you stated the highest tower was triggered at 5.76 GeV and the next to highest tower out of the 3x3 tower patch was set to 7.44 GeV. Just the sum of two towers (highest + next-to-highest). The offline clustering algo. doesn't work for the asymmetric decay modes of pi0. This will make a significant difference in the environment of high background AuAu..Surely there was a reason to add the BHT3+L2gamma for run 14 which I don't know

2) Are those percentages 0.006 and 0.002 the ones of gamma-rich which passed all offline cuts per minbias? If so; then I think the more meaningful ones would be the percentage per triggered event in each luminosity; as those are the ones needed for the projected reduction in the statistical errs.The trigger rates can be controlled easily during the run; tuning the threshold. 

3) If it is an option to run either over pico or mudst root files; then why do we need to request the mudst? Again; I don't know what was thrown away for the BSMD in the pico format. Any feedback?!

Best Regards

On Sat, Apr 1, 2023 at 2:47 PM Nihar Sahoo <nihar AT rcf.rhic.bnl.gov> wrote:

Dear James and Ahmend,

Thank you for your input and comments.
Please find my replies inline.

On 2023-04-01 05:05, James Dunlop wrote:
> Ahmed, Nihar,
>   The real question is what threshold you need.
> BHT1, 2, 3 is just 3 different thresholds in Et for a single High
> Tower,
> which you can choose/negotiate with other PWG's.  e.g. Upsilon
> tends to want a specific Et cut to avoid cutting too hard into the
> invariant
> mass distribution beyond, say, 9 GeV in M (and so 4.5 GeV in Et, try
> to keep it more like 4 so
> you can understand the combinatoric background),
>  and UPC J/Psi wants their Et cut very low.
>
Thank you for pointing this. I was thinking on this direction either we
should increase or lower (BHT3 is 5.76 and 3x3 patch 7.44 thresholds)
for L2gmma trigger thresholds.
As we use 6 GeV cutoff to high tower trigger energy for our offline
anlysis, probably it might be Ok to keep the above thresholds for Run23.
and  could that be decided during run time if it is needed?
But I welcome your suggestion and we can further discuss at trigger
board meeting.

> L2 is somewhat useful to moderate a strict high tower
> into something that incorporates information from other
> towers, but it can be problematic in the high Underlying Event
> condition of Au+Au collisions.
>
> --J
>
>> On Mar 31, 2023, at 6:45 PM, Ahmed M. Hamed via Star-hp-l
>> <star-hp-l AT lists.bnl.gov> wrote:
>>
>> Dear Nihar;
>> Thanks a lot for the slides.
>> Two comments and one question:
>> 1) I don't understand why not L2gamma and not BHT3+L2gamma; I really
>> don't know what BHT3 adds to the trigger components?

As James mentioned BHT1,2,3 are different threshold used during Run14
and 16.
"BHT3+L2gamma" label used for above last runs with  high tower threshold
is 5.76 GeV and 3x3 patch threshold is 7.44 GeV. Again as James pointed
out We may need to think on these thresholds for Run23 (and also Run25
very high lumi) which depend upon the low and high lumi.
I will discuss this topic at trigger borad meeting to come up with these
thresholds (either we can set these numbers now or during the run time,
I need suggestion in this direction)


>> 2) I think what you need to quote here (slide # 6) are the numbers
>> of events as a percentage from the number of triggered events per
>> luminosity, and not all events.
I quickly calculated the following numbers from Run14 runlog the
triggered event fractions (L2gamma trigger events/MB events)
~0.006 for high
~0.002 for low
>> Question: Migrating from the mudst to picodst what information has
>> been thrown away? e.g. Whether running the cluster algorithm (BSMD)
>> for the transverse shower profile over the picodst is still an
>> option; or one must run over the mudst files in order to find all
>> information required by the cluster algo.; i.e. the energy and adc
>> per strip.
As L2gamma trigger events will be very small is size even for upcoming
runs. we may ask for Mudst production only. But picodst production is
also possible and both energy and adc information are there inside pico.

Thank you
Nihar



>> Best Regards
>>
>> On Fri, Mar 31, 2023 at 2:23 PM Nihar Sahoo via Star-hp-l
>> <star-hp-l AT lists.bnl.gov> wrote:
>>
>>> Hello All,
>>>
>>> The proposed triggers for gamma+jet and HF physics have been
>>> updated as
>>> Rongrong suggested.
>>> (Slide#4)
>>>
>>>
>> https://drupal.star.bnl.gov/STAR/blog/nihar/HP-pwg-Run23-discussion
>>>
>>> Thank you
>>> Nihar
>>>
>>> On 2023-03-31 12:17, Ma, Rongrong wrote:
>>>> Hello Nihar
>>>>
>>>> Thanks for the slides. I think it will be nice if we can list
>>>> explicitly the triggers we want.
>>>>
>>>> In terms of quarkonium physics, here are the triggers we
>>> propose:
>>>>
>>>> * dimuon+zdc_coin+vpd100
>>>> * BHT2+zdc_coin+vpd100
>>>> * BHT1+zdc_coin+vpd10
>>>>
>>>> * monitor triggers: vpd-zdc-novtx, vpd-zdc-10
>>>>
>>>> Best
>>>> Rongrong
>>>>
>>>> -------------------------
>>>>
>>>> From: Star-hp-l <star-hp-l-bounces AT lists.bnl.gov> on behalf of
>>> Nihar
>>>> Sahoo via Star-hp-l <star-hp-l AT lists.bnl.gov>
>>>> Sent: Thursday, March 30, 2023 12:45 AM
>>>> To: Star-hp L <Star-hp-l AT lists.bnl.gov>
>>>> Subject: [Star-hp-l] Run23 data taking plan from HP-pwg
>>>>
>>>> Hello HP-pwg members,
>>>>
>>>> We were asked to provide inputs, particularly on trigger setup,
>>> vertex
>>>>
>>>> selection, and BSMD usage, for Run23 data taking. You must have
>>> seen
>>>> Rongrong's emails in this direction.
>>>>
>>>> A few slides that we have prepared our response (questions can
>>> be
>>>> found
>>>> inside).
>>>>
>>>
>> https://drupal.star.bnl.gov/STAR/blog/nihar/HP-pwg-Run23-discussion
>>>>
>>>> Mainly we have included STAR gamma+jet and also dimuon
>>> measurements
>>>> requirement in these slides if you want to propose/suggest any
>>>> specific
>>>> trigger/detector usage for RUn23 relevant to your analysis,
>>> please let
>>>>
>>>> us know asap.
>>>>
>>>> Coming Monday we plan to present at the trigger board meeting.
>>>>
>>>> Thank you
>>>> Nihar for HP-conveners
>>>> _______________________________________________
>>>> Star-hp-l mailing list
>>>> Star-hp-l AT lists.bnl.gov
>>>> https://lists.bnl.gov/mailman/listinfo/star-hp-l
>>> _______________________________________________
>>> Star-hp-l mailing list
>>> Star-hp-l AT lists.bnl.gov
>>> https://lists.bnl.gov/mailman/listinfo/star-hp-l
>> _______________________________________________
>> Star-hp-l mailing list
>> Star-hp-l AT lists.bnl.gov
>> https://lists.bnl.gov/mailman/listinfo/star-hp-l
>
> --
> He/Him/His
> Please do not feel obligated to respond to this message outside of
> your work hours.
> James C Dunlop Ph.: (631) 344-7781
> Building 510A         Cell: (631)316-8153
> P.O. Box 5000
> Brookhaven National Laboratory
> Upton, NY 11973
> dunlop AT bnl.gov