I’ve just used this for the first time. I can
confirm that contrary to the Sailwave help the required date format is
dd/mm/yy - you don’t have to edit anythign afterwards then (but maybe
yyyy-mm-dd works as well). Keep in mind however that the RYA end
involves processing the results on a per race per start basis so in my
case of a 6 race series of two fleets it was 12 iterations of the
loop. AT the end of each ‘llop’ you can get back to the start using
the drop down menu at the top of the site saying “import results”.
Just checked on of the Sailwave files I used to upload a series worth
of data and the date format I used was YYYY-MM-DD. Another little
thing to be aware of is that if one of the starts you upload has no
entrants it causes the post processing a problem. I will try and
remember tomorrow to write a fuller description.
I agree that having to post process each start of each race is a pain.
I have been uploading a 13 week series with 2 races per day each with
up to 6 starts, so that is 156 races to post process. Some of the
starts do not use the RYA PY scheme but the ISAF SCHRS rating system
and the way they are handled I have not yet been able to fathom out.
Kind regards,
Huw
Colin Jenkins wrote:
···
I’ve just used this for the first time. I
can
confirm that contrary to the Sailwave help the required date format is
dd/mm/yy - you don’t have to edit anythign afterwards then (but maybe
yyyy-mm-dd works as well). Keep in mind however that the RYA end
involves processing the results on a per race per start basis so in my
case of a 6 race series of two fleets it was 12 iterations of the
loop. AT the end of each ‘llop’ you can get back to the start using
the drop down menu at the top of the site saying “import results”.
i just came across the non rya py rating system problem myself - was
unsure what to do with a file of 3 fleets - py, texel and onedesign
racing - elapsed times are elapsed times regardless of how a club
scored them so the rya would be chucking away gobs of data if they
can’t handle it - almost all cat events are schrs or texel…
i need to do some tweaks to it:-
allow class names used to be mapped to offical class name.
allow some scored fleets to be not sent - e.g. ISAF or texel or
fleet racing mixed in with rya - in case they can never be handled.
show the race dates in the plugin ui and allow them to be changed.
i think that’s all i can do my end to help…
ps: simon l - the xls file on the site - of official ratings - is 2007
vintage.
i just came across the non rya py rating system problem myself - was
unsure what to do with a file of 3 fleets - py, texel and onedesign
racing - elapsed times are elapsed times regardless of how a club
scored them so the rya would be chucking away gobs of data if they
can’t handle it - almost all cat events are schrs or texel…
i need to do some tweaks to it:-
allow class names used to be mapped to offical class name.
allow some scored fleets to be not sent - e.g. ISAF or texel or
fleet racing mixed in with rya - in case they can never be handled.
show the race dates in the plugin ui and allow them to be changed.
i think that’s all i can do my end to help…
ps: simon l - the xls file on the site - of official ratings - is 2007
vintage.
cj
Huw Pearce wrote:
Hi
Colin,
Just checked on of the Sailwave files I used to upload a series worth
of data and the date format I used was YYYY-MM-DD. Another little
thing to be aware of is that if one of the starts you upload has no
entrants it causes the post processing a problem. I will try and
remember tomorrow to write a fuller description.
I agree that having to post process each start of each race is a pain.
I have been uploading a 13 week series with 2 races per day each with
up to 6 starts, so that is 156 races to post process. Some of the
starts do not use the RYA PY scheme but the ISAF SCHRS rating system
and the way they are handled I have not yet been able to fathom out.
Kind regards,
Huw
Colin Jenkins wrote:
I’ve just used this for the first time.
I
can
confirm that contrary to the Sailwave help the required date format is
dd/mm/yy - you don’t have to edit anythign afterwards then (but maybe
yyyy-mm-dd works as well). Keep in mind however that the RYA end
involves processing the results on a per race per start basis so in my
case of a 6 race series of two fleets it was 12 iterations of the
loop. AT the end of each ‘llop’ you can get back to the start using
the drop down menu at the top of the site saying “import results”.
CJ
---
No virus found in this incoming message.
Checked by AVG - Version: 9.0.704 / Virus Database: 270.14.59/2494 - Release Date: 11/10/09 07:38:00
I’ve been discussing the issues with Chris Gandy, as I had a go a uploading 2 slow handicap series over the weekend.
The data format required by RYA site is definately yyyy-mm-dd.
I originally used dd/mm/yy in Sailwave but this failed so have had to modify every date in every series manually before updating.
The RYA site is a bit cluncky and doesnt look pretty, plus there is no capability of editing once in there which is a pain.
That said within a few hours I had worked it all out and got a couple of series in so about 50 races.
Only problem now is that because I had a couple of people shifting classes midway through the series, I now have strange PY numbers on the RYA site, which will currently require me to delete the entire race from the site and re-load and process which is an arse.
For me its the most critical item that needs sorting. Now that I know the date format I can live with it.
i just came across the non rya py rating system problem myself - was unsure what to do with a file of 3 fleets - py, texel and onedesign racing - elapsed times are elapsed times regardless of how a club scored them so the rya would be chucking away gobs of data if they can’t handle it - almost all cat events are schrs or texel…
i need to do some tweaks to it:-
allow class names used to be mapped to offical class name.
allow some scored fleets to be not sent - e.g. ISAF or texel or fleet racing mixed in with rya - in case they can never be handled.
show the race dates in the plugin ui and allow them to be changed.
i think that’s all i can do my end to help…
ps: simon l - the xls file on the site - of official ratings - is 2007 vintage.
cj
Huw Pearce wrote:
Hi Colin,
Just checked on of the Sailwave files I used to upload a series worth of data and the date format I used was YYYY-MM-DD. Another little thing to be aware of is that if one of the starts you upload has no entrants it causes the post processing a problem. I will try and remember tomorrow to write a fuller description.
I agree that having to post process each start of each race is a pain. I have been uploading a 13 week series with 2 races per day each with up to 6 starts, so that is 156 races to post process. Some of the starts do not use the RYA PY scheme but the ISAF SCHRS rating system and the way they are handled I have not yet been able to fathom out.
Kind regards,
Huw
Colin Jenkins wrote:
I’ve just used this for the first time. I can confirm that contrary to the Sailwave help the required date format is dd/mm/yy - you don’t have to edit anythign afterwards then (but maybe yyyy-mm-dd works as well). Keep in mind however that the RYA end involves processing the results on a per race per start basis so in my case of a 6 race series of two fleets it was 12 iterations of the loop. AT the end of each ‘llop’ you can get back to the start using the drop down menu at the top of the site saying “import results”.
CJ
---
No virus found in this incoming message.
Checked by AVG - [www.avg.com](http://www.avg.com/)
Version: 9.0.704 / Virus Database: 270.14.59/2494 - Release Date: 11/10/09 07:38:00
Add other email accounts to Hotmail in 3 easy steps. Find out how.
