FWD Software

[Akio Ogawa <akio AT bnl.gov>]

Hello

Unless we have a short term solution for FTT and you plan to switch with 
FTT (for both MC and data) soon-ish, can we have separate Pico DST from 
Pythia MC with FTT added after FST seeding?

I don't know what pt (or zvertex) resolution to be expected from FST only 
tracking (in MC or ideal case for now). But it seems like we lost it and 
don't have any pt resolution nor charge separation.

If we go on without FTT for a while, we need to do something else, like 
including ECAL cluster in the track fit or something. Unless there is some 
code issue of some sort?

OGAWA, akio                 Email : akio AT bnl.gov
BrookHaven National Lab. Physics Dep. 510A 2-235
Upton, NY, 11973-5000          Tel. 631-344-5293

On Wed, 13 Aug 2025, "Brandenburg, Daniel" wrote:

> Hi Kumar,
>
> Apologies- I didn’t make it clear but until we have a plan for finishing the 
> FTT reconstruction and
> including those points *in real data* I have disabled them in the track 
> fitting. This provides for the
> time being, the most accurate and honest data to simulation comparison. 
>
> Best,
> Daniel 
>
> _________________________________________________________________________________________________________
> From: star-fwd-software-l-request AT lists.bnl.gov 
> <star-fwd-software-l-request AT lists.bnl.gov> on behalf of
> Borna Maghoul <star-fwd-software-l AT lists.bnl.gov>
> Sent: Tuesday, August 12, 2025 11:24:05 PM
> To: star-fwd-software-l AT lists.bnl.gov <star-fwd-software-l AT lists.bnl.gov>
> Subject: [[Star-fwd-software-l] ] Forward Track Fits Missing FTT points  
> Hi all, I've been playing around with the most recent commit of the 
> StFwdTrackMaker on some simulated
> muon and pythia datasets and I've noticed that the reconstructed tracks only 
> use the FST and the vertex
> for fits, and that another
> Hi all,
>
> I've been playing around with the most recent commit of the StFwdTrackMaker 
> on some simulated muon and
> pythia datasets and I've noticed that the reconstructed tracks only use the 
> FST and the vertex for fits,
> and that another fit using FTT hits aren't done. Based off of the debug, the 
> FTT hits are being loaded
> in, as seen below:
> image.png
> I'm using the FST seeding. After the seed fitting with the FST points, no 
> further fits are done, so the
> total number of fit points for the track is at most 4. Does anyone know why 
> this is occurring? It seems
> that last month the tracker didn't seem to have this issue.
>
> Regards,
> Kumar