Star-fst-l mailing list

["Visser, Gerard" <gvisser AT indiana.edu>]

Yeah... That may be a better plan. Anyway it is not a worse plan, so you are right let's do this.

Ziyue we will stay in current cosmic run while I edit - there is no problem with that, config file is only used at run start. I will send you shortly an email that I'm done, and then you should ask for the run to stop, do a new pedestal run, and then run cosmics again or whatever is the run plan, including FST.

Thanks,

      Gerard

---

From: Zhenyu Ye <yezhenyu2003 AT gmail.com>
Sent: Wednesday, June 21, 2023 6:18 PM
To: Visser, Gerard <gvisser AT indiana.edu>
Cc: L Star-fst <star-fst-l AT lists.bnl.gov>
Subject: Re: [Star-fst-l] FST with 9 Time Bins Diagnostic

 

Hi Gerard, 

If we change the latency in the middle of a fill w/o taking a pedestal run, 

the pedestals won’t be correct. I think we can change the latency by three

now, retake the pedestal run, and be ready for beam. 

Zhenyu

On Jun 22, 2023, at 12:08 AM, Visser, Gerard <gvisser AT indiana.edu> wrote:

Hi Zhenyu,

    Great - thanks! I was just not getting it by comparing the config files, but that's just my confusion. So at the moment we are taking cosmics in a situation like 2 & 3 below. Maybe we should see first collisions like that too, and then change to the situation like 1. I will prepare the file & discuss w/ Ziyue. Not sure when the collisions come again, I hope before 1 AM. Sorry for my confusion.

          Gerard

---

From: Zhenyu Ye <yezhenyu2003 AT gmail.com>
Sent: Wednesday, June 21, 2023 6:02 PM
To: Visser, Gerard <gvisser AT indiana.edu>
Cc: L Star-fst <star-fst-l AT lists.bnl.gov>
Subject: Re: [Star-fst-l] FST with 9 Time Bins Diagnostic

 

Hi Gerard

To commission FST in Run22, we started data taking with 9 time bins, with the ADC peaked in the 5th time bin, see [1].

Before making that change in firmware to go to 3 time bins, we changed the latency setting so that the ADC peaked in 

the 2nd time bin on 12/20/2021, see [2] and [3]. Then on 12/21/2021 we changed the time bin to 3, see [4]

[1] https://online.star.bnl.gov/runPlots/22354004.shift.pdf

[2] https://online.star.bnl.gov/runPlots/22354028.shift.pdf

[3] https://online.star.bnl.gov/runPlots/22355037.shift.pdf

[4] https://online.star.bnl.gov/runPlots/22355048.shift.pdf

On Jun 21, 2023, at 11:01 PM, Visser, Gerard <gvisser AT indiana.edu> wrote:

hi all,

     We are making the change to 9 timebins.

     I am seeing the latency settings for 3 timebin operation are roughly same as they were for 9 timebin operation prior to 12/20/21. This is confusing to me. I HOPE that we had already adjusted the latency to put the peak in 2^nd of 9 timebins rather than 4^th or 5^th of 9. Zhenyu do you have any recollections on this?

     We may have to try a few latency settings when we have collisions. I sincerely hope we haven't been looking at some background all this time, rather than the real crossing. Surely that can't be... But I am confused.

          Gerard

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