I scored a season long series this year, where the skippers used multiple boats and handicaps. I did not attempt to merge multiple race files, I just used one large sailwave file for the season.
What I did was modify the “Boat” field, so that it reflected all the boats used by a skipper over the series.
For instance, “Mirage 25/Hobie Tiger/Hobie 14”. The handicap for each race was set manually for these skippers, and reflected the handicap for the boat used in that race. So the only way to tell what boat was used in a race was to look at the handicap. The handicap shown for the series summary was therefore incorrect, and had to be ignored, but otherwise, the scoring was correct.
I scored a season long series this year, where the skippers used multiple boats and handicaps. I did not attempt to merge multiple race files, I just used one large sailwave file for the season.
What I did was modify the “Boat” field, so that it reflected all the boats used by a skipper over the series.
For instance, “Mirage 25/Hobie Tiger/Hobie 14”. The handicap for each race was set manually for these skippers, and reflected the handicap for the boat used in that race. So the only way to tell what boat was used in a race was to look at the handicap. The handicap shown for the series summary was therefore incorrect, and had to be ignored, but otherwise, the scoring was correct.
I have the same problem in my club. Many skippers hop in and out of different boats and we have a season long series for both a handicap and a yardstick.
I use 2 sailwave files for each of the handicap and the yardstick races, and have one called ‘working’ where each boat & skipper combination is an entity and another called ‘final’ where the skippers have multiple boats attached to them. The working file does all the mathematics regarding corrected times and the final file is scored with just places.
It is duplication but I think it is the cleanest way to do the job
I scored a season long series this year, where the skippers used multiple boats and handicaps. I did not attempt to merge multiple race files, I just used one large sailwave file for the season.
What I did was modify the “Boat” field, so that it reflected all the boats used by a skipper over the series.
For instance, “Mirage 25/Hobie Tiger/Hobie 14”. The handicap for each race was set manually for these skippers, and reflected the handicap for the boat used in that race. So the only way to tell what boat was used in a race was to look at the handicap. The handicap shown for the series summary was therefore incorrect, and had to be ignored, but otherwise, the scoring was correct.
I have the same problem in my club. Many skippers hop in and out of
different boats and we have a season long series for both a handicap and a
yardstick.
I use 2 sailwave files for each of the handicap and the yardstick races, and
have one called 'working' where each boat & skipper combination is an entity
and another called 'final' where the skippers have multiple boats attached
to them. The working file does all the mathematics regarding corrected times
and the final file is scored with just places.
It is duplication but I think it is the cleanest way to do the job
I re-enter the places. That works for me at present as we have small numbers. I could do it differently next season by having one file and one skipper per line, but maybe steering a few different boats, and changing the rating on a race by race basis, depending on what boat they are steering.
I have the same problem in my club. Many skippers hop in and out of
different boats and we have a season long series for both a handicap and a
yardstick.
I use 2 sailwave files for each of the handicap and the yardstick races, and
have one called ‘working’ where each boat & skipper combination is an entity
and another called ‘final’ where the skippers have multiple boats attached
to them. The working file does all the mathematics regarding corrected times
and the final file is scored with just places.
It is duplication but I think it is the cleanest way to do the job