By |
TSN but a memory soon |
STUBALL 10/10/2009 12:10:06 PM | TSN will be closing soon so those of us that use TSN Advantage will have to cut down to certain tracks unless Bris starts a comparable program....Bris owned both so looks like a $$$$$$$$$ move.
Stuball
|
JimG 10/10/2009 12:49:40 PM | Looks like that will make it easier for some of you to move to HDW if Jeff goes in that direction.
As for me, I have used Bris data from day one and have been pleased. In my limited comparison of Procaps and Brisnet data, Brisnet data was superior for JCapper purposes.
It is a shame for those of you that have used the advantage plan for years. Hopefully, Bris will come up with a similar plan.
Jim
|
jeff 10/10/2009 5:42:52 PM | I had a talk with Ron Tiller at HDW this afternoon.
There are a few more things on my plate that I want to add to JCapper in SQL Mode.
After that I'm going to make a serious push to finish up the dev work I started a few months ago.
HDW data WILL be available for those JCapper users who want to go in that direction.
-jp
.
|
ryesteve 10/11/2009 12:57:26 PM | Do you have a rough estimate when you might be good to go with that? I'm very, very concerned about the loss of TSN. Assuming BRIS doesn't decide to support and maintain the Procaps format, I'm dreading having to do a data transition and assess how it affects all of my UDMs, UPRs and User Factors. The pain would be somewhat eased if I only had to make this transition once, rather than having to go from TSN to BRIS, and then BRIS to HDW.
|
jeff 10/11/2009 2:07:19 PM | Steve,
There's still a number of things I have to do coding/development-wise to make this happen.
That said I'm going to be pushing hard for a 12/01/2009 go live date - possibly sooner.
-jp
.
|
ryesteve 10/11/2009 2:55:11 PM | Thanks, Jeff, that'd be great if we could bypass BRIS. If/when you get to the point where you need any beta testers for the routines that read and calc the new format, I'm first in line.
|
Tom C 10/13/2009 3:24:07 AM | I spoke to Robert at TSN tech support Monday. He told me that BRIS intends to honor the Pro Caps Advantage Plan, if the subscribers wish to continue, with the BRIS equivalent Multicaps data file until the end of 2010 at the same price for unlimited downloads.
The changeover is supposed to take place November 17th of this year.
TSN Advantage plan subscribers will be notified of their options soon and BRIS will be preparing cd-roms of all the files we have downloaded from TSN, in the Multicaps format, so we can have a complete race history.
Note to Jeff:
Will this cause a problem building databases as long as all of the files are in the same format?
Tom C
|
jeff 10/13/2009 11:08:00 AM | Tom,
I spent some time this morning looking over data file structures listed in the Library section of the BRIS site.
It does look like the file format is JCapper compatible.
If the user took a Multicaps .MCP file and renamed the file extension to either .PCS or .DRF it appears the resulting file would be JCapper compatible.
A couple of questions need to be addressed though.
The speed and pace figs in TSN .PCS files are generated using a a different algorithm than counterpart numbers in BRIS .DRF files... most likely BRIS .MCP files too.
If BRIS honors TSN data subscriptions by providing TSN .PCS subscribers access to .BRIS .MCP files, what algorithm will the speed and pace figs in the .MCP file be based on? - The TSN algorithm or the BRIS algorithm?
If BRIS changes the algorithm to satisfy TSN subscribers, how does that affect current users of the .MCP file?
If BRIS keeps the speed and pace algorithm the same to satisfy current users of the .MCP file, how does that affect TSN subscribers who make the switch-over?
Same thing goes for cxn names... Will trainer names in the .MCP file keep the current BRIS format? Or will they take on the TSN format?
TSN subscribers considering switching over to .MCP files will need to... at a minimum ... get those issues ironed out.
-jp
.
|
Tom C 10/13/2009 1:29:46 PM | Jeff,
You said "If the user took a Multicaps .MCP file and renamed the file extension to either .PCS or .DRF it appears the resulting file would be JCapper compatible."
Does that mean that we would be able to calculate races with no problem?
Can you add .MCP as a choice to the card loader or will additional programming on your part be involved?
Tom
|
jeff 10/13/2009 3:28:24 PM | --quote:"Does that mean that we would be able to calculate races with no problem?" --end quote
Of course I'll have to test it out first... DB Builds too...
However, judging from the data file structure for the .MCP file published in the Library section of the BRIS site it certainly "looks" compatible.
--quote:"Can you add .MCP as a choice to the card loader or will additional programming on your part be involved?" --end quote
Of course additional programming hours are involved. They always are...
That said... If BRIS is going to switch TSN subscribers over to .MCP files...
and IF those files ARE genuinely compatible...
Rest assured I'll work the .MCP file extension into the Card Loader, Screen Two of the File Downloader, Scratch Bot, Scratch Parser, The Manual Changes Module, The DB Builder, and at least a dozen separate algorithms inside of the Main Module... I know it seems like a simple change but it takes more work and hours than most people would think at first glance...
I'll get it worked into one of the upcoming new program versions before the switch-over becomes problematic for you guys.
I do need to make one thing perfectly clear:
I do not have the ability to go back in time and add changes like this to older program versions.
For about the past year I have maintained one code stream only - and that code stream - meaning all JCapper source code - is for the new current program version only.
Access to new current program versions requires a current renewal.
-jp
.
|
jeff 10/14/2009 4:43:00 PM | Just got off the phone a few minutes ago with Corby Corbett and Happy Broadbent of Brisnet.com.
The topic of the call was the transition for TSN Advantage Plan data subscribers from TSN to Brisnet.
TSN is being absorbed by Brisnet.com as of 11/17/2009.
My impressions from the overall tone of the call were very positive. I believe that Brisnet really does want to make the transition for TSN Advantage Plan subscribers go as smoothly as possible:
Here's a brief write up of what was discussed on the call:
* TSN will be absorbed by Brisnet on 11/17/2009
* Current TSN Advantage Plan subscribers will be "grandfathered in" and have the option to extend their data subscriptions through the end of 2010. Grandfathered in means the same monthly fee and access to an equivalent data file.
* Non TSN subscribers will not be grandfathered in and new TSN Advantage Plan data subscriptions became no longer available as of 10/01/2009.
* Grandfathered in TSN .PCS file subscribers will be given access to Brisnet MultiCaps .MCP files at the same monthly data subscription fee currently being paid to TSN.
* Brisnet's immediate goal is simple: Current TSN data subscribers will enjoy a seamless transition to the new Brisnet equivalent data file type without an increase in price.
* Yet to be determined at this time is what happens at the end of 2010.
Final comment from Happy Broadbent of Brisnet.com: --quote:
"As I said on the phone, we are here to take care of your customers and to be sure that the transition is smooth for them. We have set up a specific email address to answer any customer questions:
tsninfo @ brisnet . com (remove the blank spaces first)
Or they can contact us by calling:
8 0 0 - 3 5 4 - 9 2 0 6 option 5."
--end quote--
Now you know what I know.
-jp
.
~Edited by: jeff on: 10/14/2009 at: 4:43:00 PM~
|
TomV 10/16/2009 1:13:28 PM | Field Differences in the Procaps and Multicap files: (At least what I noticed comparing 2 current files)
What is gained using Multicaps:
Field 15 Track Record Field 856-865 Speed Rating Field 866-875 Track Variant Field 1167 - 1176 Bris Speed par for Class Level Field 1177 - Sire Stud Fee Field 1182 - 1191 - Bar Shoe Field 1192 - 1201 Company Line Codes Field 1264 - Bris dirt pedigree rating Field 1265 - Bris mud pedigree rating Field 1266 - Bris turf pedigree rating Field 1267 - Bris dist pedigree rating
What fields are lost when switching to multicaps:
Field 249 - Equibase Race name Field 1224 - 1253 Breed Type of Race (past performance races - Does not apply to todays race)
~Edited by: TomV on: 10/16/2009 at: 1:13:28 PM~
|
kingfish 10/28/2009 4:22:20 PM | Received my letter today from tsn about the transition from procap files to multicap files. Will jcapper be ready by november 17 to use the new multicap files? Also do you still plan on going forward with the conversion to hdw race files? Don't feel too secure with bris not making any guarantees past 2010.
kingfish
|
ryesteve 10/29/2009 11:28:11 AM | Did they notify you via email or real mail? Still haven't heard a thing from them. If not for message boards, I'd have no clue they were about to disappear.
|
kingfish 10/29/2009 3:17:34 PM | Received my notice by real mail yesterday. They should send be sending yours very soon. They still have about three weeks to notify you. Still wondering when they are going to send replacement multicap files. Too replace the databases we will have to rebuild. Unless they plan on having us download them from the brisnet archive page.
kingfish
|
GlennF 11/2/2009 6:00:31 PM | I called BRIS tech support today and was told they will send a disk with your procaps files converted to multicaps but they won't send it automatically, you have to request it.
|
JackB 11/2/2009 6:36:52 PM | Jeff,
Back in '05, I want to think you wrote a little thingy for me that loaded multicaps into JCapper. I'v lost a couple of computers since then so I'm no help as usual.
|
jeff 11/3/2009 11:08:55 AM | I'll be adding a Brisnet .MCP MultiCaps File option to the file type drop downs of the Card Loader, Screen Two of the File Downloader, and the Database Builder so that you can load .MCP files into JCapper and use them for Calc Races and Build Database routines.
You'll see it in a new program version published in the next few days.
However. I need to make this crystal clear:
I am no longer maintaining separate code streams for both older program versions and new program versions.
About a year ago I stopped maintaining the code stream for older program versions and began maintaining the code stream for the current program version only.
For that reason I no longer have the ability to modify older program versions.
If you are running a 2008 or earlier program version and haven't upgraded to the current program version (you know who you are) you WILL need to upgrade to the current program version to get access to this (and other more important) new features.
-jp
.
|