40′ Series — First Look

The concept is great!
There are six races and three boats, each of which have to be sailed twice.
We have to choose which boat to sail when.
OMG, I love it!
So … Here is some data:

I routed all three boats using the polars you would get from Kipper’s DC_Checker software.
I started each ‘multiple’ routing at 23JAN0800Z, and continued for 5 routes at 1hr intervals.
What that gave me was this Expedition summary of results:

22JAN2230ZThreeBoatRoutingsGPS025
Three boat routing comparison

So … based on that data, the Ker_40 is a clear choice.
But is it?
We have to use the other two boats as much as the Ker_40.
So is THIS the time to sail the Ker_40?
Or should we hold this speedy boat in reserve?

To analyze this fully, we need to look at the other courses, and at the weather we might expect along those courses at the time of year when those races are run.

Kudos to the race committee for coming up with this wonderfully complex racing series.
Ultimately, the analysis is weather based.
But it also incorporates game-theory aspects that are truly exciting to me.

That said, I encourage the race committee to level the playing field by making available to SOL skippers:

    • The polars of all three boats in full detail.
    • The courses of all six races in gpx format

Limiting access to (paid) SOL skippers will act as an incentive to join SOL.
Making these data available to SOL skippers will make racing more interesting to skilled routers.
I mean, you thought you had this figured out?
Well, guess what, there is a whole lot of figuring left to do.

That’s a challenge to me.
I’m sure it will be a challenge to most of the SOL routing skippers.

 

 

3 thoughts on “40′ Series — First Look”

  1. Viva Bob,

    I can almost agree with all you wrote about this SOL 40Series.
    Now the “Making these data available to SOL skippers will make racing more interesting to skilled routers.” statement.

    I would say: Not disclosing live boats data makes racing fairer and competitive.
    You just need to look for the recent races outcomes.

    The time for the Copy/Paste “routers” went with the shutdown in hmm’s data center.
    I sincerely hope it keeps like that.

    João/psail

    1. Hi João,

      I wasn’t thinking about making live boat data available.
      You and I agree on that point.

      What I was trying to suggest was that polar and course data should be published by the Race Committee before the race(s).
      My reasoning is this:

      1) I already have the polars and the courses for the Q1 races because I have raced those courses and boats in prior years. I’m sure many other multi-year members have this information as well. But newcomers to SOL don’t have that information, and are thus at a disadvantage.

      2) It should be the race committee that does the publishing. That makes it official [and copyright legal].

      3) Although I did not say this in the original post, I think access to the polar and course data should be restricted to SOL members in-good-standing — that is, the skippers who have paid their dues.

      But all this is really of no great import.
      I love the concept of this series.
      I’m sure this will be great sport!

  2. Viva Bob,

    Good morning.

    Some time ago, during the Cabo-Rio race I’ve made a chat comment for SOL OPS, precisely your point “1”, about the obvious need for having the (#3) 40Sereis boats Polars published in due time, i.e., before the Series start – and off course, especially for the SOL newcomers.

    But not only the boats Polars are needed before the races.
    The remaining courses paths should also have been published.
    Am I seeing it wrong?

    Your point 3 is a bit arguable. Just think a little more on it.

    I wish you a good race, Bob.

    João/psail

Leave a Reply

Your email address will not be published. Required fields are marked *


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>