Computing FPS

[hitbids]

Hello,

I'm fairly to new to some of the methodology of Pace and Cap and other computer programs, but have been delving into some of the readings and applying it to PPS. I can't recall the computation for FPS and was looking for some help? I know I have read it one of the manuals but can't recall which one.

Regards

[tom]

Check out first few Follow Ups, Beginner's Columns by Dick Schmidt.

[lsosa54]

Like Tom said, Follow Up #1, p.23, will give you a good start. The attache quick pace chart from 1982 may be helpful once you understand the calcs. Can't believe it's 30 years old - wow.

[hitbids]

Thanks for the help!

[Ted Craven]

Hitbids,

Just a note, if you are trying to follow along in RDSS - the FPS calcs shown in the early Follow Ups and other papers are a 'classical' guideline. Modern Pace Handicapping (Brohamer) is also an excellent source for the basics. RDSS employs some additional steps to get from published 'raw' running times to FPS velocities shown on the Velocity screen:

- adjusting all pacelines to today's distance and surface using an internal 'par gap' table, adjusting call1, call2 and final time accordingly
- adjust call times using a portion of the DTV and ITV for each line, apportioned to each race segment (DTV is published, ITV is not)
- feet value of beaten lengths may differ from 'classical' value (Default Mode uses 8.333 f/bl during each segment; Val4 mode uses varying f/bl values according to today's race distance)

So, while it is certainly a useful exercise to go through the mechanics of determining a FPS velocity calculation (a couple of times ), if you find it does not exactly correspond to what you see in RDSS, the foregoing are the reasons. The Velocity ranks and the gaps between ranks are more important than the absolute velocity values, and the compounding of velocity into factors such as Total Energy, E/ep L/ep, FX, Deceleration, V/DC and resulting line scores (BL/BL) is more important that simple velocity values.

Ted

[hitbids]

Thanks Ted.