Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+ARRL\s+RTTY\s+Round\-Up\s+\-\s+Log\s+checking\s*$/: 3 ]

Total 3 documents matching your query.

1. [RTTY] ARRL RTTY Round-Up - Log checking (score: 1)
Author: dk3vn@nexgo.de
Date: Wed, 14 Dec 2005 08:36:17 +0100 (CET)
Hi, copied from the "2006 ARRL RTTY Round-Up Rules": 3.2.5 Limited to 6 band changes (maximum) in any clock hour. 3.2.6 The clock hour is from zero through 59 minutes. To count the number of band cha
/archives//html/RTTY/2005-12/msg00088.html (6,796 bytes)

2. Re: [RTTY] ARRL RTTY Round-Up - Log checking (score: 1)
Author: "J. Edward (Ed) Muns" <w0yk@msn.com>
Date: Wed, 14 Dec 2005 06:05:19 -0800
Just because it is possible to write more log checking code, doesn't mean it is a good thing to do. The clock hour rule is much easier to monitor during the contest, compared to a sliding hour. Few,
/archives//html/RTTY/2005-12/msg00089.html (7,486 bytes)

3. Re: [RTTY] ARRL RTTY Round-Up - Log checking (score: 1)
Author: Waldemar DK3VN <dk3vn@nexgo.de>
Date: Wed, 14 Dec 2005 17:46:18 +0100
What an operator is able to do and what the log checker is able to do, that are two different affairs. If an operator don't want to .. or is not able to control his number of band changes during a s
/archives//html/RTTY/2005-12/msg00091.html (9,061 bytes)


This search system is powered by Namazu