[sailwave] Scoring problem with Redress Given

Richard,

A frustrating situation. I agree that there is a problem in Sailwave

with this scenario. I used scoring code RDG the same as you and also
RDGa and get same results as you do.

I have got round it by using the scoring code Duty which gives 3

points to the 29er and 4.5 points to the two boats with the same
corrected time in R1.

Over to Jon & Colin to discover the problem in the code.

Kind regards,
Huw
···

On 05/08/2013 20:04, Richard Evans
(GMail) wrote:

            I have attached the blw file that

exhibits the problem that we had at the weekend - “2013
CSC Dinghy Regatta.blw”. There are two fleets racing
under Portsmouth Yardstick and only 2 races each with 2
starts.

            In Race 1 the 29er was awarded redress

because the race committee changed the course
configuration after they had gone afloat.

            The file as attached reflects the

situation before the decision of the Protest Committee
has been included. You will note that two other boats
in the fast handicap fleet have identical corrected
times and are scored correctly with 4.5 points each. The
29er is 9th because it sailed a longer course and fewer
laps than the Mustos.

            The request for redress decision was

that the 29er be granted redress in the form of points
equal to their place in the 2nd - and only other - race;
i.e. 3rd.

            On editing the R1 result for the 29er -

setting code RDG and inputting 3 points - and performing
a “Rescore”, the points for the tied boats become 4.0
each, instead of 4.5, and the 29er ranked 3rd overall -
see attached “2013 CSC Dinghy Regatta FINAL.blw”.

The 29er should be 2nd!

            I hope someone can spot what is going

wrong.

Thanks

** Richard**

              Evans

              m: 07777670525

              t: 01381 620746

Thanks Huw - I will do as you say and then edit the published html to show RDG. Thanks.
Richard

···

--- In sailwave@yahoogroups.com, Huw Pearce <huw.pearce@...> wrote:

Richard,

A frustrating situation. I agree that there is a problem in Sailwave
with this scenario. I used scoring code RDG the same as you and also
RDGa and get same results as you do.

I have got round it by using the scoring code Duty which gives 3 points
to the 29er and 4.5 points to the two boats with the same corrected time
in R1.

Over to Jon & Colin to discover the problem in the code.

Kind regards,
Huw

Richard,

Further to my earlier reply, I have been in conversation with Jon

and he has found the solution which seems counter intuitive.

To make work in your scenario edit the result code RDG and change on

the properties page “This is a code where rule A6b applies…” by
unchecking. Jon is further investigating this counter intuitive
solution.

Kind regards,
Huw
···

On 05/08/2013 20:40, Huw Pearce wrote:

Richard,

          A frustrating situation. I agree that there is a problem

in Sailwave with this scenario. I used scoring code RDG
the same as you and also RDGa and get same results as you
do.

          I have got round it by using the scoring code Duty which

gives 3 points to the 29er and 4.5 points to the two boats
with the same corrected time in R1.

          Over to Jon & Colin to discover the problem in the

code.

          Kind regards,
          Huw
          On 05/08/2013 20:04, Richard

Evans (GMail) wrote:

                I have attached the blw file

that exhibits the problem that we had at the weekend

  • “2013 CSC Dinghy Regatta.blw”. There are two
    fleets racing under Portsmouth Yardstick and only 2
    races each with 2 starts.
                In Race 1 the 29er was awarded

redress because the race committee changed the
course configuration after they had gone afloat.

                The file as attached reflects

the situation before the decision of the Protest
Committee has been included. You will note that two
other boats in the fast handicap fleet have
identical corrected times and are scored correctly
with 4.5 points each. The 29er is 9th because it
sailed a longer course and fewer laps than the
Mustos.

                The request for

redress decision was that the 29er be granted
redress in the form of points equal to their place
in the 2nd - and only other - race; i.e. 3rd.

                On editing the R1 result for

the 29er - setting code RDG and inputting 3 points -
and performing a “Rescore”, the points for the tied
boats become 4.0 each, instead of 4.5, and the 29er
ranked 3rd overall - see attached “2013 CSC Dinghy
Regatta FINAL.blw”.

The 29er should be 2nd!

                I hope someone can spot what

is going wrong.

Thanks

**
Richard**

                  Evans

                  m: 07777670525

                  t: 01381 620746

I have found the issue and corrected it in version 2.12.3 which is available for download from the Beta section of the Sailwave website.

From what I can determine this issue is present in all earlier versions so I recommend upgrading. For those interested the cause was if there was a tie it checks to see if a code is involved in creating the tie. Then if it is, is it one such as RDG which doesn't affect other results. Unfortunately if no code was involved, rather than default to no code, it used the previous code. In this particular case RDG which stops the averaging.

Jon

···

--- In sailwave@yahoogroups.com, Huw Pearce <huw.pearce@...> wrote:

Richard,

Further to my earlier reply, I have been in conversation with Jon and he
has found the solution which seems counter intuitive.

To make work in your scenario edit the result code RDG and change on the
properties page "This is a code where rule A6b applies..." by
unchecking. Jon is further investigating this counter intuitive solution.

Kind regards,
Huw
On 05/08/2013 20:40, Huw Pearce wrote:
>
> Richard,
>
> A frustrating situation. I agree that there is a problem in Sailwave
> with this scenario. I used scoring code RDG the same as you and also
> RDGa and get same results as you do.
>
> I have got round it by using the scoring code Duty which gives 3
> points to the 29er and 4.5 points to the two boats with the same
> corrected time in R1.
>
> Over to Jon & Colin to discover the problem in the code.
>
> Kind regards,
> Huw
>
> On 05/08/2013 20:04, Richard Evans (GMail) wrote:
>> I have attached the blw file that exhibits the problem that we had at
>> the weekend - "2013 CSC Dinghy Regatta.blw". There are two fleets
>> racing under Portsmouth Yardstick and only 2 races each with 2 starts.
>>
>> In Race 1 the 29er was awarded redress because the race committee
>> changed the course configuration after they had gone afloat.
>>
>> The file as attached reflects the situation before the decision of
>> the Protest Committee has been included. You will note that two
>> other boats in the fast handicap fleet have identical corrected times
>> and are scored correctly with 4.5 points each. The 29er is 9th
>> because it sailed a longer course and fewer laps than the Mustos.
>>
>> The request for redress decision was that the 29er be granted redress
>> in the form of points equal to their place in the 2nd - and only
>> other - race; i.e. 3rd.
>> On editing the R1 result for the 29er - setting code RDG and
>> inputting 3 points - and performing a "Rescore", the points for the
>> tied boats become 4.0 each, instead of 4.5, and the 29er ranked 3rd
>> overall - see attached "2013 CSC Dinghy Regatta FINAL.blw".
>>
>> The 29er should be 2nd!
>>
>> I hope someone can spot what is going wrong.
>>
>> Thanks
>>
>> *Richard *
>> Evans
>> m: 07777670525
>> t: 01381 620746
>
>

Would it be unduly pedantic to point out that there is no A6b in the new rule book? This rule has now been re-numbered A6.2!

Gordon

···

On 06/08/2013 01:01, JON wrote:

I have found the issue and corrected it in version 2.12.3 which is available for download from the Beta section of the Sailwave website.

>From what I can determine this issue is present in all earlier versions so I recommend upgrading. For those interested the cause was if there was a tie it checks to see if a code is involved in creating the tie. Then if it is, is it one such as RDG which doesn't affect other results. Unfortunately if no code was involved, rather than default to no code, it used the previous code. In this particular case RDG which stops the averaging.

Jon

--- In sailwave@yahoogroups.com <mailto:sailwave%40yahoogroups.com>, Huw Pearce <huw.pearce@...> wrote:
>
> Richard,
>
> Further to my earlier reply, I have been in conversation with Jon and he
> has found the solution which seems counter intuitive.
>
> To make work in your scenario edit the result code RDG and change on the
> properties page "This is a code where rule A6b applies..." by
> unchecking. Jon is further investigating this counter intuitive solution.
>
> Kind regards,
> Huw
> On 05/08/2013 20:40, Huw Pearce wrote:
> >
> > Richard,
> >
> > A frustrating situation. I agree that there is a problem in Sailwave
> > with this scenario. I used scoring code RDG the same as you and also
> > RDGa and get same results as you do.
> >
> > I have got round it by using the scoring code Duty which gives 3
> > points to the 29er and 4.5 points to the two boats with the same
> > corrected time in R1.
> >
> > Over to Jon & Colin to discover the problem in the code.
> >
> > Kind regards,
> > Huw
> >
> > On 05/08/2013 20:04, Richard Evans (GMail) wrote:
> >> I have attached the blw file that exhibits the problem that we had at
> >> the weekend - "2013 CSC Dinghy Regatta.blw". There are two fleets
> >> racing under Portsmouth Yardstick and only 2 races each with 2 starts.
> >>
> >> In Race 1 the 29er was awarded redress because the race committee
> >> changed the course configuration after they had gone afloat.
> >>
> >> The file as attached reflects the situation before the decision of
> >> the Protest Committee has been included. You will note that two
> >> other boats in the fast handicap fleet have identical corrected times
> >> and are scored correctly with 4.5 points each. The 29er is 9th
> >> because it sailed a longer course and fewer laps than the Mustos.
> >>
> >> The request for redress decision was that the 29er be granted redress
> >> in the form of points equal to their place in the 2nd - and only
> >> other - race; i.e. 3rd.
> >> On editing the R1 result for the 29er - setting code RDG and
> >> inputting 3 points - and performing a "Rescore", the points for the
> >> tied boats become 4.0 each, instead of 4.5, and the 29er ranked 3rd
> >> overall - see attached "2013 CSC Dinghy Regatta FINAL.blw".
> >>
> >> The 29er should be 2nd!
> >>
> >> I hope someone can spot what is going wrong.
> >>
> >> Thanks
> >>
> >> *Richard *
> >> Evans
> >> m: 07777670525
> >> t: 01381 620746
> >
>

Hi Gordon,

No its not unduly pedantic - I love to get the feedback and if I forget don’t hesitate to remind me. Thanks Huw also pointed out that it has been changed. I have changed the code now so the next version will have A6.2 changed it in 3 places hope that is all.

Jon

···

Jon Eskdale
Sailwave

03333 443377

07976 709777

On 6 August 2013 10:47, Gordon Davies gordondavies@eircom.net wrote:

  Would it be unduly pedantic to point

out that there is no A6b in the new rule book? This rule has now
been re-numbered A6.2!

  Gordon


  On 06/08/2013 01:01, JON wrote:
          I have found the issue and corrected it in version 2.12.3

which is available for download from the Beta section of
the Sailwave website.

          >From what I can determine this issue is present in all

earlier versions so I recommend upgrading. For those
interested the cause was if there was a tie it checks to
see if a code is involved in creating the tie. Then if it
is, is it one such as RDG which doesn’t affect other
results. Unfortunately if no code was involved, rather
than default to no code, it used the previous code. In
this particular case RDG which stops the averaging.

          Jon

          --- In sailwave@yahoogroups.com              ,

Huw Pearce <huw.pearce@…> wrote:
>
> Richard,
>
> Further to my earlier reply, I have been in
conversation with Jon and he
> has found the solution which seems counter intuitive.
>
> To make work in your scenario edit the result code
RDG and change on the
> properties page “This is a code where rule A6b
applies…” by
> unchecking. Jon is further investigating this counter
intuitive solution.
>
> Kind regards,
> Huw
> On 05/08/2013 20:40, Huw Pearce wrote:
> >
> > Richard,
> >
> > A frustrating situation. I agree that there is a
problem in Sailwave
> > with this scenario. I used scoring code RDG the
same as you and also
> > RDGa and get same results as you do.
> >
> > I have got round it by using the scoring code
Duty which gives 3
> > points to the 29er and 4.5 points to the two
boats with the same
> > corrected time in R1.
> >
> > Over to Jon & Colin to discover the problem
in the code.
> >
> > Kind regards,
> > Huw
> >
> > On 05/08/2013 20:04, Richard Evans (GMail)
wrote:
> >> I have attached the blw file that exhibits
the problem that we had at
> >> the weekend - “2013 CSC Dinghy Regatta.blw”.
There are two fleets
> >> racing under Portsmouth Yardstick and only 2
races each with 2 starts.
> >>
> >> In Race 1 the 29er was awarded redress
because the race committee
> >> changed the course configuration after they
had gone afloat.
> >>
> >> The file as attached reflects the situation
before the decision of
> >> the Protest Committee has been included. You
will note that two
> >> other boats in the fast handicap fleet have
identical corrected times
> >> and are scored correctly with 4.5 points
each. The 29er is 9th
> >> because it sailed a longer course and fewer
laps than the Mustos.
> >>
> >> The request for redress decision was that
the 29er be granted redress
> >> in the form of points equal to their place
in the 2nd - and only
> >> other - race; i.e. 3rd.
> >> On editing the R1 result for the 29er -
setting code RDG and
> >> inputting 3 points - and performing a
“Rescore”, the points for the
> >> tied boats become 4.0 each, instead of 4.5,
and the 29er ranked 3rd
> >> overall - see attached “2013 CSC Dinghy
Regatta FINAL.blw”.
> >>
> >> The 29er should be 2nd!
> >>
> >> I hope someone can spot what is going wrong.
> >>
> >> Thanks
> >>
> >> *Richard *
> >> Evans
> >> m: 07777670525
> >> t: 01381 620746
> >
> >
>