TUP Modeler Bug…

[DanG]

Weird one; at least for me. :confused:

TUP, 02/13/2011, Race #1 (or any of their 6.5f’s on this date) please run a track, dist, surf 90 day model and see if it goes past 20 races until it hits 99! :eek:

[Mechanic]

same issue here (99):eek:

[DanG]

same issue here (99):eek:

Thanks 'M; maybe after the contest Ken can take a look at it.

[fred4now]

Also another one, not sure it is related to TUP or not.
On 12/19/10 Tup5, The wizard output shows the #2 as the winner when the charts show the #9 as the winner. Not sure how this could happen.

Also sometimes I see the odds as 0.0.

[Mechanic]

Also another one, not sure it is related to TUP or not.
On 12/19/10 Tup5, The wizard output shows the #2 as the winner when the charts show the #9 as the winner. Not sure how this could happen.

Also sometimes I see the odds as 0.0.

12/19/2010 TUP #2 babyface won the race but was DQ'd, the WIZARD will show #2 as the winner as will Robot2, keeping the data correct.

[del_dog]

I am thinking dq or problem with the name of the horse.

You will also find that when the original files are created that the jky data will not change if a different jky actually gets the ride.

This is normally, in real time , not a big deal as the original jky , unless riding a different horse in the same race, shows the horse was a go today.

However it can give you false positives when testing for top X jky and/or running jky plays via the robot.

[fred4now]

Yup, that explains it. Kind of a pain when looking at past data though.

[km]

I'll check it out when i get home, thanks.

Why does it seem like TUP is always involved with these bugs :confused:

[DanG]

Perhaps a connection...

Today's (03/06/2011) GP race #5, with class and 999 days 36 races modeled.

[km]

Thanks Dan, a cursory look failed to locate the problem in MaxVel. Somehow the stop-gap at 20 races during the loop is bypassed. I'm knee deep in Robot2 upgrade and will tackle it asap.