Last week I was scoring the Zhik 29er World Championship at the new
Plas Heli facility in Pwllheli, North Wales and an unusual scoring
issue arose.
A Request for Redress was submitted to the Jury for consideration
and their decision was to award average points to the competitor for
two races, e.g . RDGa. The scoring code was changed from DNC
to RDGa for both races and the series was re-scored. This was where
the issue arose.
When the series was re-scored unexpected things happened, I can not
remember the all the effects but two were in one race the leader was
scored 2 points instead of 1 point and in the other race the leader
was scored 0.5 points not 1 point. Somewhere deep in Sailwave the
scoring logic does not expect to encounter a situation where a boat
is given redress via RDGa code when it does not have a finish place.
**The solution** is to give the boat in question a finish place,
any will do but makes sense to make it last place for the race then
switch to the scoring code for the boat using the radio buttons in
the ‘Edit result’ window for the boat/competitor. Then when the
series is re-scored everything is OK.
Kind regards,
Huw
···
This email has been checked for viruses by Avast antivirus software.
I can not explain what is going on but I have found a work around.
In the attached file I have put a dummy elapsed time for each
occurrence of OOD. I did this using the following steps for each
occurrence of OOD code:
right click cell with OOD code and select edit result
click elapsed time radio button and entered dummy time of
59.59
click code radio button
click OK
Then I scored the series.
As I said Jon is looking at the issue and is aware of of Peter van
Muyden’s comment about working is Sailwave 2-19-0. Unfortunately,
Jon has on issue with his server which he is having to resolve
before he can look for code differences between 2-19-0 and following
versions to try and identify when and where the issue arose.
Tomorrow if Jon is not able to find the problem area I will track
back through Sailwave versions 2-19-1, 2-19-2 and 2-19-3 to see if
they exhibit he same problem. So helping Jon narrow the issue down.
Jon finally sorted out his PC problems late last night and
determined that a change in Sailwave version 2-19-1 seems to be the
cause. Further investigation is being undertaken.
The change that seems to have caused the scoring problems reported
by you and a couple of others was to address and highly unusual but
possible situation when using the PHRF ToD rating system where the
corrected time could be negative. The PHRF ToD formula “Corrected =
Elapsed - (Rating*Distance)”.
Jon is planning to release a new version soon with the code
introduced in version 2-19-1 removed. More work will be done on
investigating the potential for Corrected times under PHRF ToD to be
negative. Perhaps Art Engel could help our understanding.
I can not explain what is going on but I have found a work
around. In the attached file I have put a dummy elapsed
time for each occurrence of OOD. I did this using the
following steps for each occurrence of OOD code:
right click cell with OOD code and select edit result
click elapsed time radio button and entered dummy time
of 59.59
click code radio button
click OK
Then I scored the series.
As I said Jon is looking at the issue and is aware of of
Peter van Muyden’s comment about working is Sailwave 2-19-0.
Unfortunately, Jon has on issue with his server which he is
having to resolve before he can look for code differences
between 2-19-0 and following versions to try and identify
when and where the issue arose.
Tomorrow if Jon is not able to find the problem area I will
track back through Sailwave versions 2-19-1, 2-19-2 and
2-19-3 to see if they exhibit he same problem. So helping
Jon narrow the issue down.
Kind regards,
Huw
This email has been checked for
viruses by Avast antivirus software. www.avast.com
This email has been checked for viruses by Avast antivirus software.
I suppose it is possible in theory to have negative corrected times but
I wouldn't expect it in practice.
My area (Southern California PHRF) has handicaps from -135 to 270. To
come up with a negative corrected time, the -135 boat would have to have
an average speed around the course of 3600/135 = 26.7 kts. A boat with a
rating of -150 would need an average speed of 24 kts (3600/150 = 24).
Neither seems likely, though certainly possible. In general, bigger
boats with such high performance don't sail under PHRF, which started as
a system aimed at much slower and lower performance boats.
The anomaly is created by the choice of a base (or 0-rated) boat. With
~50 years of history I don't see the base boat being changed so the
problem won't be going away. But, not sure I'd worry much about it now.
My advice would be delete it for now and put it back in when you can get
it working properly.
Art
PS - I think the IRC base boat (rates 1.000) has a PHRF rating of around 90.
Jon finally sorted out his PC problems late last night and determined
that a change in Sailwave version 2-19-1 seems to be the cause. Further
investigation is being undertaken.
The change that seems to have caused the scoring problems reported by
you and a couple of others was to address and highly unusual but
possible situation when using the PHRF ToD rating system where the
corrected time could be negative. The PHRF ToD formula "Corrected =
Elapsed - (Rating*Distance)".
Jon is planning to release a new version soon with the code introduced
in version 2-19-1 removed. More work will be done on investigating the
potential for Corrected times under PHRF ToD to be negative. Perhaps Art
Engel could help our understanding.
I can not explain what is going on but I have found a work around. In
the attached file I have put a dummy elapsed time for each occurrence
of OOD. I did this using the following steps for each occurrence of
OOD code:
* right click cell with OOD code and select edit result
* click elapsed time radio button and entered dummy time of 59.59
* click code radio button
* click OK
Then I scored the series.
As I said Jon is looking at the issue and is aware of of Peter van
Muyden's comment about working is Sailwave 2-19-0. Unfortunately, Jon
has on issue with his server which he is having to resolve before he
can look for code differences between 2-19-0 and following versions to
try and identify when and where the issue arose.
Tomorrow if Jon is not able to find the problem area I will track back
through Sailwave versions 2-19-1, 2-19-2 and 2-19-3 to see if they
exhibit he same problem. So helping Jon narrow the issue down.
