Measuring junk sailing performance

  • 13 Nov 2018 17:24
    Reply # 6902791 on 4913961

    Robert, Poppy was fitted with racing instruments, giving water speed, true or apparent wind speed and I think direction as well as VMG to up wind or down wind with an expanded scale apparent wind direction from directly up wind or down wind. This latter instrument was very useful and if I remember correctly for beating I simply selected the apparent angle as appropriate to the sea state, trimmed the sails to best speed (all luff tell-tales flying) and stuck to that apparent wind angle. This got the respect of the Bermudan boys.

    Unfortunately I cannot remember the exact range for apparent wind angles I used as I used them as pips on the scale rather than numbers, but they could be remarkably small. I do remember that pointing above 45° true wind angle did not really increase VMG to windward, but it was often useful to point much higher if you sheeted in further trying to pass a moored boat or buoy and know that the speed would not drop of significantly and stall the keel. The 30° angle does not surprise me as I have a recollection of tacking through 60° one occasion.

    Poppy could point much higher than her Bermudan sister, if for no other reason than the headsail sheeting angle on her sister was right out on the toe rail and the split rig could be sheeted almost to the centre line so that the jibs only had their inbuilt sheeting angle, which was about 10° (I think). The split rig can be sailed very tightly sheeted, but not necessarily with a better VMG. The Longbow is very susceptible to sea state as the bow is quite blunt to give a good fore cabin berth, however in flat water (it does occur occasionally) it was fun to out point all the Bermudan boats. We got some very funny looks at such times.

    As for downwind speed, on the run we always got boat speed equal to relative wind speed which meant running at half true wind speed. This held up to 6 kts boat speed, but above that LWL length limitations slowed the increase down. Going onto a broad reach could increase the boat speed in winds under 12 kts, but the VMG down wind would only increase a little so we didn't really bother to tack downwind.

    I see little point in comparing the boat speeds recorded for the various boats, even with corrections (or fiddle factors) as a slight variation in sea state can make a mockery of any results, and that is why I have always tried to assess performance when sailing beside similar boats of known handicap (even though handicaps are not perfect). I think the only thing that might come out of this exercise would be to show the shape of the windward performance curve and close windness of a rig, but on Poppy I wasn't worried about that as we had the VMG meter to confirm our performance.

    I hope this is of some use.

    Cheers, Slieve.

  • 13 Nov 2018 15:08
    Reply # 6902464 on 4913961

    dd/mm/yyyy is right for Weaverbird: 06/08/2018 = 6th August.

  • 13 Nov 2018 13:55
    Reply # 6902357 on 4913961
    Deleted user

    Now that I'm manipulating the date-time stamp just want to make sure about format. Poppy files are obvious dd/mm/yyyy (15/09/2018). Weaverbird format could go either way: 06/08/2018.

    Thanks

    rself

    Last modified: 13 Nov 2018 13:56 | Deleted user
  • 11 Nov 2018 20:10
    Reply # 6899470 on 4913961
    Deleted user

    FYI---I just noticed that 3 of the Poppy CSVs are empty.

    PS actually 6, s5,6,and 7  and p4,5,6.

    1 file
    Last modified: 11 Nov 2018 20:24 | Deleted user
  • 11 Nov 2018 19:14
    Reply # 6899435 on 4913961
    Deleted user

    Poppy prelims. Even TWSs. Histograms, etc here. I also have a split junk rig so found these results particularly interesting.

    In Slieve's AYRS catalyst article he mentions that Poppy goes at about half the wind speed. These preliminary results supports that. I point to the TWS=6knt polar plot which, most likely, all 7 panels were up. N=1100 plus data points. Many of those point in the 30,40,50 and 150,160,170 and 180 degree bins, i.e. upwind and downwind TWAs. Median boat speed 3 knts or better in all bins in the 6 knt wind.

    I'm wondering about the "30 deg" TWA...is that realistic for a westerly longbow? Seems unusually close-winded for the design but I don't know the boat. There are 200 points in that bin having TWAs between 25 and 34.9 degrees. Are all/most due to tacking? It's fairly easy to look at the time series of d(twa)/dt and d(tws)/dt. Obvious tacks should show up as hills or valleys and "steady state" as flats.....maybe.

    rself

    9 files
    Last modified: 11 Nov 2018 19:26 | Deleted user
  • 11 Nov 2018 18:45
    Reply # 6899424 on 6899329
    Deleted user
    Anonymous wrote:

    Hello Robert,

    The CV7 wind sensor is outputting eg

    $IIMWV,047.0,R,014.9,N,A*32

    where 047.0 is wind direction
    R is reference
    014.9 is wind speed
    N is knots
    A is 'correct measure'
    *32 is checksum

    Also $WIXDR wind temperature which we aren't interested in.

    The DX900+ log sensor is outputting eg

    $VMVBW,4.65,-1.00,A,,,V,,V,,V*64    dual speed
    $YXXDR,A,-3.4,D,PTCH,A,-10.6,D,ROLL*6D pitch and roll
    $VMNLA,25.6,A*06     leeway
    $VMVLW,38.68,N,28.07,N,,,,*5E    distance
    $VMVHW,,,,,4.96,N,9.19,K*5D     boat speed

    I think that NavMonPC is then adding date and time, because that sentence is $GPZDA which doesn't appear in the text files. We would need another source if we don't use NavMonPC.

    I've put a full list of the NMEA 0183 sentences here





    OK. Thanks David. Looks like only the strings that need to be pulled are $VMVHW and $IIMWV to generate the stw, awa and aws values in the  .csv's. I'll do a test run with the first weaverbird text file and see if get any sequences of values that resemble what's in the csv.
    Last modified: 11 Nov 2018 18:48 | Deleted user
  • 11 Nov 2018 16:13
    Reply # 6899329 on 4913961

    Hello Robert,

    The CV7 wind sensor is outputting eg

    $IIMWV,047.0,R,014.9,N,A*32

    where 047.0 is wind direction
    R is reference
    014.9 is wind speed
    N is knots
    A is 'correct measure'
    *32 is checksum

    Also $WIXDR wind temperature which we aren't interested in.

    The DX900+ log sensor is outputting eg

    $VMVBW,4.65,-1.00,A,,,V,,V,,V*64    dual speed
    $YXXDR,A,-3.4,D,PTCH,A,-10.6,D,ROLL*6D pitch and roll
    $VMNLA,25.6,A*06     leeway
    $VMVLW,38.68,N,28.07,N,,,,*5E    distance
    $VMVHW,,,,,4.96,N,9.19,K*5D     boat speed

    I think that NavMonPC is then adding date and time, because that sentence is $GPZDA which doesn't appear in the text files. We would need another source if we don't use NavMonPC.

    I've put a full list of the NMEA 0183 sentences here





    Last modified: 11 Nov 2018 16:26 | Anonymous member
  • 11 Nov 2018 14:14
    Reply # 6899240 on 6886808
    Deleted user
    Anonymous wrote:

    Ideally, we should write our own software for the recording programme as the prospects of getting the authors of NavMonPC to update theirs seem slim.

    Hi Alan--Question about the processing steps:

    1. All the data collected by the electronics is in the .txt files (??).

    2. .txt files read by NavMonPc --- user sets some parameters---then outputs a .csv file.

    So date, time, aws, awa and port/stbd information are all in the .txt file?

    Found a Matlab nmea decoder in the Mathworks file exchange but none of $G--strings in your files match the strings in the prog. Do you have a source for the sentence definitions?

    I'll post first half of Poppy results pretty soon.

    rself

    Last modified: 11 Nov 2018 14:21 | Deleted user
  • 11 Nov 2018 12:04
    Reply # 6899181 on 6898120
    Alan wrote:

     I think it confirms my impression that the approach of taking the median of all the data leads to an unrealistically low result.

    It occurs to me that a better approach might be to use an idea similar to the concept of "significant wave height", which is the mean of the highest third of the data, the data being the measured wave height of thousands of waves. This gives a figure that corresponds to an experienced observer's assessment of the sea conditions, but effectively smooths out any extremely large waves, and discounts the lowest two thirds of the data. Maybe we could and should use a similar approach to extract a result from the data that an experienced observer would recognise as "reasonable".

    The Pareto Principle, or 80/20 rule, might also be applied. That is, it's easy to get 80% of available performance with 20% crew effort/concentration, but getting that last 20% of performance requires a much higher level of skill and concentration. I would guess that most of us sail at the 80% of available performance level (unless we're racing and concentrating 100%). Sea state, too, will have an enormous influence. In flat water, we might get 100% of available performance, but in wind against tide conditions we might struggle to get 50%. 

    Once Anthony's approach has discarded data that is not steady state, because the boat is turning, or the wind is changing, then perhaps a line drawn through the 80% points would be quite realistic, as a guide to what performance is readily achievable.

    Last modified: 11 Nov 2018 12:16 | Anonymous member
  • 10 Nov 2018 12:46
    Reply # 6898120 on 4913961
    Anonymous

    That is very interesting because it shows the wide distribution of the data points about the median points and the smoothed curve through the median points.

     I think it confirms my impression that the approach of taking the median of all the data leads to an unrealistically low result.

    It occurs to me that a better approach might be to use an idea similar to the concept of "significant wave height", which is the mean of the highest third of the data, the data being the measured wave height of thousands of waves. This gives a figure that corresponds to an experienced observer's assessment of the sea conditions, but effectively smooths out any extremely large waves, and discounts the lowest two thirds of the data. Maybe we could and should use a similar approach to extract a result from the data that an experienced observer would recognise as "reasonable".

    I'm delighted that we are investigating several approaches to analysing the data.

    Anthony Cook is refining his software to eliminate points where the wind speed drops more than 0.7 knots per second, and where the wind direction changes by more than 5 degrees per second. The intention is to eliminate any data that may show a false over-performance because the boat speed drops off more slowly than the falling windspeed, or change of angle. He is also eliminating all the subsequent data points until the boat speed changes, to be sure that the effect of the change of wind speed or direction has been reflected in the boat speed.

    I hope, Robert, that you will be able to extend your analysis to the other boats. It would be very interesting to see the resulting curves for all the boats at one wind speed on the same graph.

       " ...there is nothing - absolutely nothing - half so much worth doing as simply messing about in junk-rigged boats" 
                                                               - the Chinese Water Rat

                                                              Site contents © the Junk Rig Association and/or individual authors

Powered by Wild Apricot Membership Software