FWD Software

["Ogawa, Akio" <akio AT bnl.gov>]

Daniel did it and I did not do that part. But code is right there so we can read and understand … 

It would be good to check all 6 towers are in a row or column for that case. 

Or 5 towers in a raw, and a tower in next row but very weak? (With log weighting, I doubt this can produce e-15…)

Akio

From: David Kapukchyan <david.kapukchyan AT email.ucr.edu>
Date: Wednesday, March 4, 2026 at 1:25 AM
To: Ogawa, Akio <akio AT bnl.gov>
Cc: Brandenburg, Daniel <star-fwd-software-l AT lists.bnl.gov>
Subject: Re: Strange behavior of points and clusters in Run 22 production

This Message Is From an External Sender

This message came from outside your organization.

 

Hello Akio,

I can confirm that those lines in StMuFcsUtil are important for saving the associations to the MuDst however how should the MuDst save the cluster id? Because, as you know, in the MuDst the cluster Id is sequential regardless of detector id but not in StEvent. Maybe this is why the lines were commented out because the saved cluster id needs to take into account the detector id?

Also, it seems the near zero sigma min/max values don't always appear for single or double tower clusters. There can be more towers and still get a sigma min/max near zero. I haven't had time to check this but presumably they are coming from a cluster where all the towers are in a line. Most I saw was "nTowers:6|sigmamin:3.17344e-15|sigmamax:0.449337".

Best,

David