star-fwd-software-l AT lists.bnl.gov
Subject: FWD Software
List archive
Re: [[Star-fwd-software-l] ] [[Star-fcs-l] ] Request : Run25 AuAu FCS Ecal calibration production
- From: Akio Ogawa <akio AT bnl.gov>
- To: "star-fcs-l AT lists.bnl.gov" <star-fcs-l AT lists.bnl.gov>, "star-fwd-software-l AT lists.bnl.gov" <star-fwd-software-l AT lists.bnl.gov>
- Cc: Xilin Liang <xlian046 AT ucr.edu>
- Subject: Re: [[Star-fwd-software-l] ] [[Star-fcs-l] ] Request : Run25 AuAu FCS Ecal calibration production
- Date: Tue, 24 Mar 2026 09:47:51 -0400 (EDT)
I'm sorry
One of 26232012 -> 26232013
One of 26232015 -> 26232005 26161021 emc-check -> 26161028
26303017 CosmicLocalClock -> 26303004
26303042 emc-check -> 26303040
Fixed at
https://www.star.bnl.gov/protected/spin/akio/fcs/run25.html
as well.
OK, I think I understand and can proceed with a sufficient chain....
For our main purpose of Ecal pi0 calibration you can go withiut FWD tracking data...
But maybe tracking people are interested in using low mult AuAu mudsts and wants to run afterburner later which should be possible with keeping fst & ftt data by keeping "fst,ftt,fstMuRawHit" options even without fwd tracking enabled.
Daniel?
OGAWA, akio Email : akio AT bnl.gov
BrookHaven National Lab. Physics Dep. 510A 2-235
Upton, NY, 11973-5000 Tel. 631-344-5293
On Mon, 23 Mar 2026, Van Buren, Gene wrote:
OK, I think I understand and can proceed with a sufficient chain....
...but I do have one more question. The 120 runs that are in those 6 table
boxes on the web page contain two duplications:
26232012,26232015
Please let me know if those should be two different run numbers.
Thanks,
-Gene
On Mar 23, 2026, at 3:57 PM, Xilin Liang <xlian046 AT ucr.edu> wrote:
This Message Is From an External Sender
This message came from outside your organization.
Dear Gene,
I remember that we had the fast offline QA for fcs stream in Run 25. Do you
remember what is the production chain for that fast offline production?
Since this is for calibration purpose, at the current stage, it does not
matter to me for whether to include the tracking detectors or not. This is
NOT the final production for this dataset. If any one have any other use with
this test production, please feel free to mention.
I will suggest to use the fast offline QA chain or the chain without the FWD
tracking detectors.
Akio, please share your thought.
Thank you!
Best regards,
Xilin
On Mar 23, 2026, at 3:18 PM, Van Buren, Gene <gene AT bnl.gov> wrote:
Looking back at what we did for 2022 data, we had an even more minimal chain (starting with the base
"B" chain instead of the "pp" or "P" chain). Something like this:
"B2025,BAna,trgd,ZDCvtx,emcDY2,-ITTF,-TpcIT,-tpcX,-tpx,-TpcHitMover,fcs,fst,ftt,fstMuRawHit"
Do we want something like the above, _with_ FWD tracking detectors (or
perhaps even with FWD tracking enabled?), or something like the below chain,
_without_ the FWD tracking detectors ?
"B2025,BAna,trgd,ZDCvtx,emcDY2,-ITTF,-TpcIT,-tpcX,-tpx,-TpcHitMover,fcs"
Thanks,
-Gene
On Mar 23, 2026, at 2:37 PM, Van Buren, Gene <gene AT bnl.gov> wrote:
Hi, Xilin
I haven't yet produced anything. I had some questions embedded in my previous
email that I wasn't sure about, so I will clarify those here:
1) Any objection to using SL25y?
2) Do you have any test DAQ files available that either you or I could run
the chain on?
Thanks,
-Gene
On Mar 23, 2026, at 1:43 PM, Xilin Liang <xlian046 AT ucr.edu> wrote:
This Message Is From an External Sender
This message came from outside your organization.
Dear Gene,
Thank you for helping to produce the files for Run 25 with fcs .
I’m wondering if you have already produced several MuDst files? If yes, could
you share the location? I can help to test to see if the files are good for
the calibration.
Thank you!
Best regards,
Xilin
On Mar 18, 2026, at 3:37 PM, Van Buren, Gene <gene AT bnl.gov> wrote:
Thanks, Akio.
For the production of FCS in 2024 st_fwd stream , we used this chain:
"pp2024a -ITTF -sti -TpcIT -tpcX -tpx -TpcHitMover -mtd fcs -ftt -fttdat
-ftthitcalib -fttclu -fttpoint"
I'm guessing we will similarly want:
"P2025 -ITTF -sti -TpcIT -tpcX -tpx -TpcHitMover -mtd fcs -ftt -fttdat
-ftthitcalib -fttclu -fttpoint"
You are welcome to test this if you have an st_fcs DAQ file handy (I don't),
and see if it gives the output you want.
Unless you believe otherwise, I suggest we use the SL25y library, as I expect we will
be processing all Run 25 data with the new TPC alignment (hence the "y"),
despite that the TPC alignment is moot for this track-less production, because then any
st_physics production with FCS will have the same alignment with respect to the TPC
that is used in the st_fcs production.
Thanks for getting the current version of the gains into the database!
-Gene
On Mar 18, 2026, at 3:22 PM, Ogawa, Akio <akio AT bnl.gov> wrote:
Hello Gene,
Here I'm officially requesting FCS Ecal calibration prodiction of 120 runs
listed at
https://www.star.bnl.gov/protected/spin/akio/fcs/run25.html
- "fcs" stream files only, but all events in all files
- Just fcs chain and NO need for TPC reconstruction
- Keep Mudst and hopefully they fit on disks
- No need for StEvent/picodst files
Also I've finally pushed Run24 FCS Ecal gains to offline DB. It does not
matter much since we are changing the gain anyway, but this production will
have at least good starting gains as of end of Run24, which is better than
what I pushed as initial guess of gains.
OGAWA, akio Email : akio AT bnl.gov
BrookHaven National Lab. Physics Dep. 510A 2-235
Upton, NY, 11973-5000 Tel. 631-344-5293
- Re: [[Star-fwd-software-l] ] [[Star-fcs-l] ] Request : Run25 AuAu FCS Ecal calibration production, Akio Ogawa, 03/24/2026
Archive powered by MHonArc 2.6.24.