FWD Software

[Manny Rosales Aguilar <maro323 AT g.uky.edu>]

Hi Daniel,

As I promised here are a few slide that hopefully shed light on what may be happening with the no track finding using the FST as the track source in data. Perhaps we are both running into the same issue. 

Below is a few details on the slides

I am looking at the data under the following production stream for Run 22  production=P23if,trgsetupname=production_pp500_2022

Slide 2:

The top plot shows the average energy of the towers in the ECal agains the RunNumber (the runs start with 22 but they get cut off in the pdf) . This plot is based on the instances when the fcsJP2 Trigger fired in the data but the points below hold for other FCS Triggers as well.

The Red vertical line indicates the approximate RunNumber when the official Trigger Promotion took place while the Green Vertical Line indicates the approximate time RunNumber when the ECal Tower calibrations took place which was around December/January in 2023.

The bottom plot show the average number of tracks we are finding against the RunNumber. The plot show that we are unable to reconstruct tracks after the approximate RunNumber = 22356049 which is before the RunNumber of when the official Trigger Promotion took place. This is consistent with what you are seeing in your slides from today for runs after 23000000 in the Zero Field data. 

Slide 3: 

In this slide I have the debug output from the StFwdTrackMaker for runs after runNumber 22356049 and you can see from the debug comment that even after this RunNumber we do find several hits in the FST but from slide two we know we are not finding any tracks. 

Hopefully this helps but please let us know if you have any questions .

Best,

Manny R.

Attachment: 05:03:24 - Tracking on QA.pdf
Description: Adobe PDF document