New FlightScope Trajectory Optimizer Interface

[HiTrajLoSpin]

The FlightScope Trajectory Optimizer (FTO) is very useful for doing just that, but its interface has lacked the ability to see more than one data set at a time.

 

The FTO now has a new interface that solves that issue, enables export of the data sets as CSV files, and provides standard sea level or local weather conditions (with wind on/off and direction changes).

 

 

Edited November 25, 2021 by HiTrajLoSpin

[RCGA]

Anyone else getting numbers that don't align with reality? 

 

I hit a PW around 105 ball speed, 24 launch, 9500 RPM for around a 136y carry. 

 

Flightscope has me hitting the same shot 127y. 

 

Into a wind it's even worse. Flightscope has me hitting that same shot into a 25mph wind at 70y total. A more traditional calculation has me around 95y.

[HiTrajLoSpin]

1 hour ago, RCGA said:

Anyone else getting numbers that don't align with reality? 

 

I hit a PW around 105 ball speed, 24 launch, 9500 RPM for around a 136y carry. 

 

Flightscope has me hitting the same shot 127y. 

 

Into a wind it's even worse. Flightscope has me hitting that same shot into a 25mph wind at 70y total. A more traditional calculation has me around 95y.

 

Are you using 'Local Weather' or 'Standard Sea Level' ? Is the 'Wind' set to 'Off' ?

 

'Standard Sea Level' for your speed, launch, and spin gives 129.5 carry.

 

 

[RCGA]

Using Trackman's Tour numbers here: https://blog.trackmangolf.com/trackman-average-tour-stats/

 

For a 102 ball speed on a PW gets 136y. Using the same stats on the Trajectory Optimizer, I get 126y. A 10y difference using the same input numbers is a lot. 

 

I'm assuming the Trackman numbers for the Tour are normalized. So wind, temp and elevation are similar. 

[HiTrajLoSpin]

1 hour ago, RCGA said:

Using Trackman's Tour numbers here: https://blog.trackmangolf.com/trackman-average-tour-stats/

 

I'm assuming the Trackman numbers for the Tour are normalized. So wind, temp and elevation are similar. 

 

The Trackman numbers aren't normalized (see the fine print below the table):

 

Please be aware that the location (altitude) and weather conditions have not been taken into consideration for the above data

 

[RCGA]

9 hours ago, HiTrajLoSpin said:

 

The Trackman numbers aren't normalized (see the fine print below the table):

 

Please be aware that the location (altitude) and weather conditions have not been taken into consideration for the above data

 

 

That's the very definition of normalized, though. 

[RCGA]

Looking at the cross wind data and inputting their PW data (https://blog.trackmangolf.com/trackman-average-tour-stats/)

 

It's saying a 20mph cross wind will push a 125y PW 28y off line.

 

I've never had a 20mph left to right wind that required me to aim almost a full green width to the left just to hit the left side. 

[HiTrajLoSpin]

12 hours ago, RCGA said:

 

That's the very definition of normalized, though. 

 

Normalization of golf data, such as the Trackman PGA/LPGA averages, would adjust for the elevation, temperature, wind, pressure, humidity, etc. at which those data were measured; that adjustment then gives results for a standard set of conditions, e.g., sea level,  77°, 0 wind speed, 14.7 psi, 50% humidity for the FlightScope Trajectory Optimizer.

 

Think of it as being similar to adjusting your golf score for the course rating and slope to give your handicap index ( i.e., normalized)

Edited December 4, 2021 by HiTrajLoSpin

[Stuart_G]

On 12/3/2021 at 6:56 PM, RCGA said:

Using Trackman's Tour numbers here: https://blog.trackmangolf.com/trackman-average-tour-stats/

 

Those are just averages, each line does not represent a real shot.  e.g.  Each category is averaged independently

 

Edited December 9, 2021 by Stuart_G