Rantoul_Eagles__FS__V_Invite_4-2-2016_054am.zip

Here is the file that I get when importing entries from Direct Athletics

Views: 199

Reply to This

Replies to This Discussion

Here is a photo of what the field event entries look like when they are imported in to Race Tab.

You probably had the event set up as english but imported as metric or something. It would be helpful if you included the meet (rtab) file and what you are importing.

I see your "tfx" file now, which I presume is the way DA downloads the semi-colon delimited. Having your rtab file would be helpful so that I don't have to try to set up a meet from scratch to match your event/division set up and make sure we're looking at the same thing.

But I do notice in the file that they put in the field event marks for english as 5' 10" with a space between and the ' and ". That could potentially be the problem since that's not the typical format. I will test it once you send me your rtab file and make a fix accordingly in 4.22

I am set to English and get the same outcome he did.

D;Buford;DeShawn;;M;;RANT;Rantoul;;11;LJ;20' 1";E;1;;;D;

comes out at 100' in the seeding.

I am thinking it's that space between feet and inches. Typically we use a dash but I think RaceTab probably supports the ' and " but maybe not with the space.

Okay I have it replicated with just that one line. Working on debugging and a solution now. Will update.

There were multiple issues with it actually. I have fixed them all for version 4.22

I was also noticing something odd in entering "fake results" for a field event.

If you type 1 in for a distance ... just one, you get 3-03. Type 2 and you get 6-06, type 3 and you get 9-10. But you don't get 1, 2, nor 3 as the result.

It tries to be smart to recognize the input, Don. Arguably too smart. But if it's an english event and you don't type a a valid english mark or it's outside of the expected range for feet or something... it will think "oh you mean meters" and convert it. So that's what it's doing there.

I guess that makes sense (ish) -- at least I understand now. I found this when just trying to quick create results with 1, 2, 3, etc.

Jason Byrne said:

It tries to be smart to recognize the input, Don. Arguably too smart. But if it's an english event and you don't type a a valid english mark or it's outside of the expected range for feet or something... it will think "oh you mean meters" and convert it. So that's what it's doing there.

Yeah the logic is actually quite complex. It looks at how many numbers you typed in, what event it is, what would make sense as valid for that mark, and even additional clues like if it ends in 25 or 50 or 75 it's probably a quarter inch decimal. Except in long throws which it would not be. 

So there may be places where it can improve or tries to be too smart, but yeah.

If you type that single digit in for a high jump or pole vault it's going to convert it to feet. like 9 would become 9-0 but if you do it for something else where a single digit foot distance wouldn't typically make sense then it's going to not assume that and figure you must mean meters.

Reply to Discussion

RSS

Facebook Page

© 2017   Created by Jason Byrne.   Powered by

Badges  |  Report an Issue  |  Terms of Service