As of Sunday, July 28

Exacta Paste Works!

Next is Results.

You guys are all right!
The way this works...

The RED OBJECT
i.e. E=1st call, EP=2nd, LP=Not E, SR=Not E or EP.
... predicts the running style of the race.

Another way to look at it is:
_________________
RED E Means should be 1st call, possibly 2nd call, but not likely later.
_________________
RED EP Means should be 2nd call, but could be 1st or 3rd call.
_________________
RED LP Means could be anything after 1st call.
_________________
RED SR Means should be Str Call or Last Furlong, but might be as early as 2nd call.
_________________
Pay special attention to the SHOULDS versus the COULDS.

@Jim Parker
Your answer is the RED pace object.

Plus/minus 1 call.

As of Saturday, July 27.

1. Odds Paste Works
2. Scratches work.

Next is exactas.

I cut the screen down.

Very interesting, this explains a new screen that I'm seeing "Entries" when I'm looking at yesterday's races. — Jim Parker

That one isn't new.

Still writing code, but...

Imagine Scotty's voice...

A GLOSSARY is a great idea

Understanding Reports - 001 The Basics
This video is a 2.5 hour class that covers How to Create, Use, and Understand Reports.

Don't miss the 15-minute intro with our star panelists & Teaching Members.
@ponyplayer
@Jim Michalak
@john g
@Tony Kofalt
@Dave R

As they should be, yes.

The Odds are derived from the projected pool percentages, therefore they should be the same $nets and grades.

My question: How to create a report to determine if a horse is dropping in class today? Also, class in general-- a report to show which horses have the best class (maybe a ranking). — Jim Pommier

Yes.
That's what I was referring to.
We'll get to it tonight.

Any chink in the armor is a BALO. Any magnitude that is not a 1 is a BALO. — Dennis

That sounds right to me.
Exceptions for turf.

In fact, I'd leave turf out for now.
@Dennis

So, the stats were actually better.
Hmm... going to mull that.

Perhaps in the relatively near future we'll be able to capture the data and take a look at grades as well.

I wonder if, for example, a BALO w/B+ performs differently than a BALO w/D.

First, really good work on this.

A few comments to begin

• I am a little disappointed that they were ONLY -21% losers, but considering that these are the horses who are usually considered the best bet at the track, I can't complain much.
• I wonder if the Double BALO races might make a difference in that.
• Also, could take a look at the 1.21 and below BALOs to make it stronger.

As for your question about smaller tracks, yes, I have seen similar before. I think it ties to top trainers, because at the small tracks there are so few really "top" trainers.

We'll hold the horses a bit for you.

Can't wait to hear what other people think of this.

Remember - BUILD USEFUL COMPONENTS!
Not just REPORTS!
If you have too many reports - as I built in the original MY PRIME - it actually dilutes your effort by providing too many answers.

Some Key Points About Reports[/Components
1. Every report should serve a single purpose!
2. You have SIX FIELDS to ANSWER ONE QUESTION.
3. Decide on the question ahead of time, then build the report that answers that question only.
4. The report YOU design should lead you to THE ANSWER you seek.
5. If you need multiple reports to answer a single question, you are probably over-complicating things.
6. You may need to tinker with the order of the fields on a report - comparing different configurations.

Looking Deeper

• Perhaps build a list of questions ahead of time.
• Then prioritize those questions and build them top-down.
• Remember that you should have a short list of components but they should all work towards your chosen end.
• Build your own "Prime Report" and test it across some back races.
• Do not test it across 47 different kinds of races.
• Instead, test against (say) Non-Maiden Races, Older, Fast Tracks.
• Do this before build a whole stable of reports.
• You can build 2 or 3 versions of the same report and do a little simple data study.

Final word: Keep this as simple as possible.

Hopefully you can join a few minutes late?

If we pushed back to 6:00 could you make it?

Very difficult for learned people to do because we specialize in LOGICAL SOLUTIONS.

Not sure what your referring to, you did talk about -- 1. Fixed Error #35 after changing Report Set --
but what I'm addressing isn't the Report Set. It's closing the main screen as stated, am I missing something ? — Jim Parker

Yes.
https://www.community.horsestreet.com/discussion/588/determinator-upgrade-version-1-0006-is-available/latest/comment

Problem solved.