I'LL LEAVE THIS HERE FOR POSTERITY -- BUT WHAT IS DESCRIBED BELOW IS NOT a BUG. See my self immolations in further posts below.

This was brought to my attention today. It is meaningful now that profiler values are stored in the database.

This is the sequence of events that occur when you store a race's data to the database, irregardless of what method you use to store:

A) The card data is loaded
B) The results are loaded - they need to be present in order to store to DB.
C) Simulations are run
D) The race are profiled (if profiler values are to be stored).
E) The races are stored to db.

Well, hold on there pardner - did you say that the results were loaded? Uh-huh. Well, what happens when you profile? Do the profiles for each race (and their profiler values) make use of their own results?!?!? Yep, sure do, unless you set up the date filters to exclude the results for the race you are storing.

Obviously this is not what we want. To fix it I've added code that will cause the Profiler to NEVER return races in a profile that occurred on the _same day_ as the race being profiled. Note that I did not make it so that only the same race does not get into its own profile, but any race _on the same day_ as that race.

A new build will be available as soon as I'm done with the wager tags stuff since its half baked right now.

-N

[This message was edited by Nathan M. on November 13, 2003 at 11:48 PM.]

[This message was edited by Nathan M. on November 14, 2003 at 06:05 PM.]

Update -- how much of an impact does this have on the profiler value stats? Hard to say. I just ran the DED db through with the new fix (cards from 1/4/2002 to 11/1/2003) and the results actually _improved_ now:
Before:
Profiler: 893 starts, 30.12% wins
Comp: 893 starts, 24.75 wins

After:
Profiler: 871 starts, 30.42% wins
Comp: 871 starts, 26.02% wins

Not sure if I am on solid ground here, so I would appreciate a reply.

What I did to take advantage of the MY PICKS is to create a new database for say Santa Anita.

I have 3 years worth of BRIS files with the Prime Power ratings, so I used STORE BY TRACK and built a database only using Santa Anita races from 2001 and 2002.

I am now going each day of the 2003 season using the Prime Power number sort and then after I record the first 4 pick in the Wager and Selection area, I then save the race to the database.

The results ARE loaded but not saved to the database until after I profiled the race.

Like Dr. Szell said "Is it Safe"

Chris

ARRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRG

Someone please give me a HUGE DUNCE CAP

and I'll go sit in the corner for a while......

BRB....

OK, the evil bug was not a bug at all....

Answering chris's question made me realize this.

A) You load a card. Results are loaded, because you're about ot store to database.

B) You PROFILE. Guess what -- THE RACE YOU ARE HANDICAPPING IS NOT YET IN THE DATABASE. THEREFORE - it will NOT show up in the races used to generate the profile for the race you are handicapping! ERGO - NO BACKFITTING.

I think I need to decrease the meds, or maybe go on some.... boy I feel stupid.

OK, one good thing, I do think its a good idea to never allow the profile to be generated _with the race for which the profile is being generated_ for. This change was made to "fix" the evil bug (that never was) -- ES no longer allows races that took place __on the same day__ as the race being profiled into the profile. So some good came out of it. I think?