DOS vs. WIN

[Cliff]

To all those who have made the complete transition to Windows, please forgive my newbie- type questions as I plunge in.

1) Is the nLDR in Windows a better predictor, or, put another way, why would a horse (in DOS) be designated as the nLDR and maybe be ranked in FR1 as high as 2 or 3?
1a) Can there be more than one nLDR per race?

2) Where is the DNF factor now located?

3) Is nBLF now nFNBL1 in HX5?

Thanks,
More to come, I'm sure.

[Donnie]

Cliff----
Please change your avitar...it is too distracting!!:D

[MikeDee]

for 1) ken will have to answer

for 1a) yes

for item # 2 and 3)

Hx4 item
112 "nABLF" Beaten Lengths at the finish.
0 = winner
99 = DNF, lame, pulled up, etc
-1 = no chart found for this horse or race

I keep watching thinking one of them is sure to flop out, but no luck yet:(

[km]

Ditto Donnie on your icon - try something tasteful Cliff, but I know that's a lot to ask :)

1) Leader combines 3 factors
Quirin speed points
Running Style
Fr1

Updated the formula slightly in the Windows version.
In realtime, (*) leader will take the front about 80% in dirt routes, 70% in d sprints, 60% in turf.

2) DNF is not a factor, it meant = "did not finish". That was used in the DOS as a blanket comment for the finish position because we didn't have room for the position calls. DNF was listed for any horse that finished 40 or more lengths back at the wire or was "eased", "lame", etc. In the Windows version, the speed figure will be missing if the horse was so far back that we can't assign it the lowest possible figure. Most horses eventually cross the wire, even if they are eased, and then you'll see "99" maximum for the BL, but a position was still assigned by the chartcaller. The trip note explains what happened.

If you are trying to make a system out of the 'DNF' as Tomcat's friend Bob did, then you need to use HX4 and query =
nLPOS1 > 0 (the horse did run to the first call last out)
nLCSF = 0 (horse was so far back or eased at the finish that a speed figure could not be assigned)

3) yes, nFNBL1 from HX5 is the "finish beaten lengths in the most recent start".
You could use > 40 to test the DNF with this field.

PS: MikeDee mentions nABLF, from the charts, but that is the current race outcome, I think Cliff was looking for a horse that was DNF in its previous start. By using the query with nLPOS1 > 0 and nLCSF = 0; you also avoid phony DNF's such as foreign shippers (they don't get a POS1)

[Cliff]

Avatar changed by popular demand!

a) nLDR - Thanks for the clarification (should have known that)
b) DNF - Yes! That's the one, "factor" term used loosely
c) nFNBL1 - Yes, looking for most recent race so that's the number I'd need.

Here's a new batch I can't seem to find in the HX exports:

1) vE/P
2) nEPDIF
3) nLEV
4) nSPCA (specifically sprint to route change in current race for now)

Thanks all,
LMK when you get tired of that avatar....shouldn't take long!

[tomcat]

Don't forget to use lay=<30. The theory is that if the horse came right back, what ever caused the DNF didn't hurt the horse too much, but would underbet for sure.

[MikeDee]

Cliff

If you need any hints on linking hx4 and hx5 to pick up thenfinbl1 let us know.

[tommyc]

You handicapping guys still give me a headache....and NOW you've pressured Cliff into ditching his wonderfully entertaining "big boob" Avatar for M. Jackson ?

Methinks our bbs is now beginning to take itself TOO seriously and starting to believe a lot of our own b.s.

Just a personal observation....bring it on.

tommyc

[Donnie]

I don't think anyone asked him to put MJ up there, but for some queer reason he did!! what was that they say about Texans.....??

That don't look like no steer!!



Donnie (now on a qwest to find the most "wonderfully entertaining" avatar EVER!!!)