|| Couple of questions
|Can you do add two factors and sort the sum to order of the HTML report? Say, adding FigConsensus and Early Consensus and then ordering by the rank of that combined number.|
Is there a factor for Horse Win Percentage much like Rider or Trainer?
Is there a way to see an average odds rank for a horse?
In the HDW pp's, is there to see horses that have raced against each other. In the DRF the bold horses in the company line from a common race.
On a screen print of an HTML report, it has A/E. What is that?
|Mike, In my opinion, the best way to accomplish what you are asking for here would be a separate data project outside of JCapper. |
The basics involve importing data from JCapper tables (starterhistory and starterstoday) - and possibly (selected data fields or even all data fields) from the .JCP and HDW Text Chart Results Files into Excel 2010, Access, MySQL, SQL Express - or another 3rd party app of your own choosing.
From there it would be easy (provided you are willing to burn the needed programming hrs) to create all of this - as well as pretty much any other custom data points you see fit to derive from JCapper data going forward.
|That said, you can do some of this within JCapper.|
For example, you can sum numeric values for multiple factors inside of a SQL expression.
Suppose for the sake of argument that in your sql factor setup F13 is FigConsensus and F19 is EarlyConsensus.
You could sum the two in a sql expression as follows:
AND (VALF13 + VALF19) >= 180
Creating a UDM around something like the above line of sql won't make the value of VALF13 + VALF19 appear sorted on an html report. But it will enable you to make UDMs flagging horses meeting factor constraints embedded in the UDM Definition appear (sorted by UDM name) on an html report.
Alternately, and although my own R&D indicates better results are obtainable using behaviors 14 and 15... You could create a USERFACTOR equal to the sum of two or more JCapper factors using behavior 10.
~Edited by: jeff on: 1/27/2014 at: 10:24:25 AM~
"In the HDW pp's, is there to see horses that have raced against each other. In the DRF the bold horses in the company line from a common race."--end quote
Yes. In the Enhanced Settings Module, persist the setting for PPs Company Line Display as: 2 Display FULL Company Line in PPs
You'll have to look at the "company line" names displayed for each running line and then compare them against the horse names squaring off in today's race. (But the company line names certainly aren't hidden from you.)
"Is there a factor for Horse Win Percentage much like Rider or Trainer?"--end quote
"Is there a way to see an average odds rank for a horse?"--end quote
"On a screen print of an HTML report, it has A/E. What is that?"--end quote
In the Enhanced Settings Module there's a setting labeled as Rider-Trainer A/E Rating History Type where you have the ability to select a time frame to be used by the Interface when it generates the rating.
A/E stands for Actual vs. Expected and when you select something other than "0 None" as your persisted setting: The Interface will compile stats for each rider and each trainer by querying your StarterHistory table during a Build .JCP File Routine. (The generated ratings are actually written to the JCP file.)
FYI, toggling this function "on" in the Enhanced Settings Module causes an increase to the amount of time it takes to build each .JCP File... how much of an increase depends on the capabilities of your machine. Some older machines may slow to a crawl. However, on most newer machines the time increase isn't that bad.
Currently, as I type this, the only place the A/E Rider Profile Rating or A/E Trainer Profile Ratings appear in JCapper are in the stat boxes for both rider and trainer when PPs are generated in SQL Mode. (I'm guessing that's what you are referring to in your above post.)
That said, I do plan on making both A/E Rider Profile Rating and A/E Trainer Profile Rating available in UPR Tools (Platinum only in an upcoming program update) so that these ratings can be used as inputs when creating UPR and UserFactors.
~Edited by: jeff on: 1/27/2014 at: 2:37:30 PM~
Doing a lot of research and I have a series of little questions that I haven't found the answers on. I appreciate you fielding a few of them.
Actually I just tried your format and it worked. Using
ORDER BY (RANKF13 + RANKF19) ASC
I would prefer a "then by" but this works.
|Using normal SQl, you can do something like this:|
Order By (RankFX +RankFX) ASC, RankFX DESC
Not sure if that would work, but give it a shot. Just separate your sorts by a comma. Make sure if you're using ASC or DESC to do it before the comma.