X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Sun, 24 Sep 2006 23:07:32 -0400 Message-ID: X-Original-Return-Path: Received: from smtp105.sbc.mail.mud.yahoo.com ([68.142.198.204] verified) by logan.com (CommuniGate Pro SMTP 5.1c.4) with SMTP id 1417502 for lml@lancaironline.net; Sun, 24 Sep 2006 00:47:12 -0400 Received-SPF: none receiver=logan.com; client-ip=68.142.198.204; envelope-from=elippse@sbcglobal.net Received: (qmail 61667 invoked from network); 24 Sep 2006 04:46:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=hyHNBhb7uDF9juSYRgezaZmZzIATHadhg+hejiyC2O/r3SNRmV/gMOiXg+rushj/2gH59t9SvDH1OPQybfTOPVBKA5KcUIYpYsnfYmmWYdJR53nWrwD8MnYOFBUxDbEGDSDuuiWiT8Eez/Ku9LMmodYm4erm7+ZxGzBiU7RpLuY= ; Received: from unknown (HELO Computerroom) (elippse@sbcglobal.net@75.15.112.139 with login) by smtp105.sbc.mail.mud.yahoo.com with SMTP; 24 Sep 2006 04:46:31 -0000 X-Original-Message-ID: <000901c6df94$6c284490$8b700f4b@Computerroom> From: "Paul Lipps" X-Original-To: "Marv Kaye" Subject: RARA X-Original-Date: Sat, 23 Sep 2006 21:46:37 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C6DF59.BEDD5EE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C6DF59.BEDD5EE0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Right on, John! RARA owes everyone an explanation of why it took so long to come up = with the supposed/alleged pylon cut. Pylon judges ordinarily give their = inputs within several minutes of the end of the race. GPS data in a race = with high turn rates might show a little time delay, but it should be = possible to compare pylon entry-exit paths over several laps to check = for consistency. ------=_NextPart_000_0006_01C6DF59.BEDD5EE0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Right on, John!

RARA owes everyone an = explanation of=20 why it took so long to come up with the supposed/alleged pylon cut. = Pylon judges=20 ordinarily give their inputs within several minutes of the end of the = race. GPS=20 data in a race with high turn rates might show a little time delay, but = it=20 should be possible to compare pylon entry-exit paths over several laps = to check=20 for consistency.

------=_NextPart_000_0006_01C6DF59.BEDD5EE0--