Powered by
WIND


Recent Posts

Recent Comments

  • IMHO

    Modifying the SIs after a race is completed happens all the time and is not prohibited by 90.2(c).  The requirement that the change is communicated prior to the warning signal only applies when the change is made on the water.  Consider the case where a change is made prior to the second day's racing and applies going forward in the event. 

    The PC cannot change the SIs, or the NoR or any of the other documents that govern the event for that matter.  The RC is the responsible party for the SIs and the only they can change the document.  The PC's job is to interpret and apply all the rules in the documents as written, provided that each rule conforms to the rules, e.g. properly changes a rule, etc.  If an individual SI (or NoR) does not conform to the rules then it cannot be enforced, effectively deleting it.  But the PC cannot change a rule to make it conform to the rules.

    63.5(c) handles when there is a conflict between some specific rules, those in the SI, NoR, & documents from item (g) in the definition of rule, then the PC must select which of those rules will provide the fairest result for all boats effected.  But the PC cannot change the rule or create a new rule.  It must pick one of the rules to use.  This also effectively deletes the rules not selected.
    Today 16:50
  • Ben ... I think you had it nailed with the simple observation, and that is ..

    In mark-room, the term proper course only has one function, and that is a test condition of whether or not a boat's MR includes room to sail  to the mark.  That's all. 

    I think the confusion also comes in that def: MR previously stated a boat's MR included room to pass or round as necessary to sail the course.  I think people commonly replaced the phrase "as necessary to sail the course" with "proper course" in their minds.  That was a mistake, as they were different.

    But that said, that phrase is no longer in the rule, and the proposed inclusion of proper course in the new def: MR did not make it.

    So proper course in def: MR is a "test, apply and forget" modality. 

    In this OP, with this specific geometry, Blue's PC is to sail close to the left gate.  Therefore her MR includes room to sail to the mark on its proper side.  Though we do not have updated Case 75 yet, this portion of def:MR did not change. Assuming Case 75 does not change that portion of the discussion, Blue's MR is a corridor directly to the mark from the edge of the zone to proper side of the mark. 

    Yellow is in a position when she reaches the zone to provide that corridor, so she needs to maneuver promptly to do so, as soon as her obligation comes into existence. 
    Fri 13:17
  • Yes - "virtual" is a pretty lame word.

    I was struggling with the word 'signal' used in the definition. In general / nautical English a signal is a man-made visual or aural communication to mark a time, event or state. 

    How then can 'nothing' be a signal?  Even 'deeming' or' taking it to be' are a little loose. I thought about 'pseudo'. But yes, I agree.  'Virtual' doesn't really work.

    For fixed timings, I've seen it all. Exact start times listed, times offset from the first start and even just watch for your flags on the day. Agree with postponement issues, but with 21st technology it gets easier to recalculate and disseminate new times on the fly. 

    I guess the main point I have is that persuit style of starts changes a great deal of RRS26.  That can't be avoided. 

    Cheers. 



  • And the starboard rounding comparison (the lazy author version)

    image.jpeg 122 KB
    Tue 13:54
  • Paul just informed me that if you highlight a text selection before hitting the reply button, the reply will include the highlighted text along with the bookmark-link to the replied-to comment. 

    Try it out! 
    Tue 12:33

Forums Leader Board

This Month

1 John Allan 3.8K
2 Michael Butterfield 1.6K
3 Jim Champ 1.6K
4 Benjamin Harding 1.5K
5 Gijs Vlas 1.4K
Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more