|
JCapper Message Board
JCapper 101
--
Track Profile report not working?
|
|
By |
Track Profile report not working? |
busseb 8/22/2021 4:09:31 PM | Went to export - Jeff's Track Profile Report Generator.
Cleared it.
Ran a UDM for all.
Then tried to run the report. My only options were all-all-all-...
It wouldn't let me input any definitions and the run option was never available.
Probably me, as usual.
Any suggestions?
Must I be in PlayList or sql mode or either?
~Edited by: busseb on: 8/22/2021 at: 4:09:31 PM~
| jeff 8/22/2021 8:01:39 PM | It was created years before SQL Mode was created.
You have to be operating in Playlist File Mode to run it.
Here's a link to an older thread where you can find pretty much all the relevant info: http://www.jcapper.com/messageboard/TopicReader.asp?topic=1902&forum=JCapper%20101
-jp
.
| busseb 8/22/2021 11:07:52 PM | Do you still use it and if not, is it worth taking the time to try and make it relevant?
| jeff 8/25/2021 2:56:58 PM | I'm using the SQL Data Window because it offers several advantages over PLMode Exports.
First, you don't have to run a separate export in PLMode that takes several minutes to run to completion.
Instead, you can create sql expressions that return targeted query results to cover pretty much any situation you can imagine - including track bias.
It's not that hard to create sql expressions that act as a template for analyzing track bias - save them as inactive UDMs - and pull them up later - and after minimal edits to date ranges, track, intsurface, and dist - use them over and over again.
Here's a link to a thread where I posted examples showing how to combine two or more sql expressions: http://www.jcapper.com/messageboard/TopicReader.asp?topic=1736&forum=JCapper%20101
--quote:"Easy enough...
Let's start with a sql expression in its simplest form:
SELECT * FROM STARTERHISTORY WHERE (X)
Note that in the above template, even though the expression is as simple as it gets, I am using parenthesis characters.
It's also implortant to note that in sql expressions, everything inside a set of parenthesis characters, even if it is hundreds of lines long, gets evaluated as if it were a single parameter.
Therefore, placement of parenthesis characters in sql expressions is critical.
In the above sql expression 'X' can represent either a single sql command or even hundreds of lines of sql commands.
Because 'X' is wrapped in parenthesis characters 'X' is evaluated as if it were a single line of sql.
Let's expand the above sql expression a bit...
What happens if we replace 'X' with individual sql commands? (Substitution.)
Instead of SELECT * FROM STARTERHISTORY WHERE (X) if we replace 'X' with '(A) OR (B) OR (C) OR (D)' our sql expression now looks like this:
SELECT * FROM STARTERHISTORY WHERE ((A)
OR (B)
OR (C)
OR (D))
The above sql expression can be used as a basic template to combine 4 multiple sql UDMs into a single sql UDM.
In the above sql expression (A) is a single sql UDM.
In the above sql expression (B) is a second single sql UDM.
In the above sql expression (C) is a third single sql UDM.
In the above sql expression (D) is a fourth single sql UDM. " --end quote
More to come...
-jp
.
| jeff 8/25/2021 3:13:47 PM | Here's a link to a thread in the Private area of the board from 2019 where I posted about combining two or more sql UDMs into a single SQL UDM and (on 5/22/2019 at 9:50:22 PM) some thoughts about track bias: http://www.jcapper.com/messageboard/TopicReader.asp?topic=2227&forum=Private
--quote:"Track bias can shape race results in the near term - Imo, to a greater degree than most players realize.
In the past I've posted about the influence of track surface (track maintenance, materials composition including water, depth of harrowing, degree of banking, and placement of banking, etc.) on track biases.
Here's a link to one such thread: http://www.jcapper.com/messageboard/TopicReader.asp?topic=1480&forum=Private
However, I don't think I've ever posted any of my thoughts about weather --
Weather systems that bring cycles of wind, rain, and sunshine have the ability to create cycles of track bias.
The winds of low pressure weather systems in the Northern Hemisphere rotate in a counterclockwise direction.
The couterclockwise rotation of a large low pressure system traveling west to east across the US would (likely) create winds out of the southwest as its first edges reach (say) Lexington, KY where Keeneland is located.
Winds out of the southwest at Keeneland can translate to presser types getting a boost from a tailwind on Keeneland's far turn. When that happens, early types can be at a disadvantage compared to normal circumstances.
But once the "eye" of a low pressure system traveling west to east across the country passes over Keeneland, that same counterclockwise rotation would now (likely) create winds coming from the opposite direction: the northwest.
Winds out of the northwest at Keeneland can translate to presser types facing a headwind on Keeneland's far turn. When that happens, early types can be at a slight advantage compared to normal circumstances.
On top of that, a large low pressure system traveling west to east across the country will (likely) bring rain to the area.
Depending on how much rain, the grounds crew at Keeneland may (or may not) decide to seal the dirt surface.
Of course, each surface is different. The amount of moisture in the surface, as well as how tightly compressed the surface is, has an effect on track bias.
As the low pressure system moves out of the area the sun comes out. The weather warms, and surfaces go through a drying out period. Of course this drying out period can bring its own unique short term track biases.
Eventually, after enough drying out, things get back to normal. The dirt course becomes fast and the turf becomes firm.
But a few days later, maybe a week, maybe several weeks --
The cycle repeats itself (not just at Keeneland, but at every track you can name) as the next storm system moves into the area.
My point?
The development samples that we use to create UDMs, UserFactors, UPR, or MLR models are influenced not just by track maintenance but by weather patterns too.
It is not only possible (but highly likely) that the validation samples we use to forward test and tune UDMs, UserFactors, UPR, or MLR models are influenced not just by variations in track maintenance but by variations in weather patterns too." --end quote
More to come...
-jp
.
| jeff 8/25/2021 3:42:06 PM | What if I were tracking weather systems traveling west to east across the US?
What if I picked just one track and made an effort to compile my own data?
The date the leading edge of a system reaches the area where my chosen track is located and begins dumping rain? The amt of rain. Change in temperature. Change in wind speed and direction, etc.
And then noted any resulting change in track bias.
The date the trailing edge of the system reached the area where the track is located and stopped dumping rain? The amt of rain if any. Change in temperature. Change in wind speed and direction, etc.
And then noted any resulting change in track bias.
Dates while the area where the track is located was drying out? Change in temperature. Change in wind speed and direction, etc.
And noted any resulting change in track bias while the track surfaces were in the drying phase.
Dates after the area where the track is located had completed the drying out phase? Temperature. Wind speed and direction, etc.
And noted any resulting change in track bias now that the track was fast and firm again.
Now suppose after compiling my own weather cycle data for a few seasons --
What if I used the technique posted above for combining multiple sql expressions?
What if I started creating a sql expression by inserting track-intsurface-dist into (A)?
And inserted dates when the leading edge of each system had reached the area where the track is located and began dumping rain into (B) (C) (D), etc.?
I'd have a sql expression that would tell me what to expect when a storm front first starts dumping rain on my chosen track.
On top of that I could just as easily create sql expressions designed to tell me what to expect bias-wise as each phase of the weather cycle affects my chosen track.
The SQL Data Window enables me to think outside the box.
-jp
.
|
|