Fxt update #721
Fxt update #721
Conversation
…which couldn't possibly cause any side effects, but lets be safe about it shall we?)
…ate the TPC dead region.
|
I see that the 2018 fixed target position was also modified. This may not be justified as yet. My understanding is that the beampipe was removed between 2018 and 2019 for the detector rollout and installation of the iTPC. As such, the 2018 position may be different relative to STAR from the 2019+ position. I understand that the 2018 FXT position of 200.7 was identified in Fig. 19, page 26 of this analysis note: So we probably only want to adjust 2019-2021 geometries to use z = 200.0 cm for now. |
…gov/STAR/system/files/Analysis_Note_for_Higher_Order_Cumulants_FXT_Au_Au_3_0_GeV.pdf. Position likely changed per GVB's comment after 2018.
…into fxt-update
|
Thanks Gene. y2018d removed.
…On 2024-12-10 16:06, Gene Van Buren wrote:
I see that the 2018 fixed target position was also modified. This may
not be justified as yet. My understanding is that the beampipe was
removed between 2018 and 2019 for the detector rollout and
installation of the iTPC. As such, the 2018 position may be different
relative to STAR from the 2019+ position. I understand that the 2018
FXT position of 200.7 was identified in Fig. 19, page 26 of this
analysis note:
https://drupal.star.bnl.gov/STAR/system/files/Analysis_Note_for_Higher_Order_Cumulants_FXT_Au_Au_3_0_GeV.pdf
So we probably only want to adjust 2019-2021 geometries to use z =
200.0 cm for now.
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you authored the thread.Message ID:
***@***.***>
Links:
------
[1]
#721 (comment)
[2]
https://github.com/notifications/unsubscribe-auth/ANL4LVCXQHNVVKRQ24QTDHD2E5JVXAVCNFSM6AAAAABTLN45W2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSHA4TCNJXHA
|
Well.... better to understand the build failure before merging. |
…g some whitespace to try this again ...
|
Build issue was a duplicate entry for y2024a coupled with hubris on my part not to compile locally before making the PR. Second entry should have been tagged as y2024b. Code compiles locally, so I expect this to compile on github. |
|
All tests are passing, so hitting the shining green button. |
No description provided.