CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] possible changes for CQ VHF Contest

To: "rjairam@gmail.com" <rjairam@gmail.com>
Subject: Re: [CQ-Contest] possible changes for CQ VHF Contest
From: Edward Sawyer <EdwardS@sbelectronics.com>
Date: Wed, 24 Jul 2019 08:52:10 -0400
List-post: <mailto:cq-contest@contesting.com>
I thought that was likely the source.

It’s a very common misconception that Clublog logs pick up all of the “traffic” 
on the air.  I tested this theory a month or so ago.

I called CQ on SSB for an hour and called CQ on CW for an hour.  I worked about 
100 stations.  This was a weekday evening with a mix of NA, SA, and Eu 
stations.  I then looked up each call to see how many were log uploaders to 
Clublog.  The answer, only 20% of that “traffic” uploaded to clublog.

Beware of assumptions on data.

75% of clublog uploaders may be FT8 – to your point probably higher.  But that 
does not represent the HF traffic at all.  Even clublog itself has a statement 
about drawing wide conclusions from its log data.

Ed  N1UR

From: rjairam@gmail.com [mailto:rjairam@gmail.com]
Sent: Wednesday, July 24, 2019 8:46 AM
To: Edward Sawyer
Cc: cq-contest@contesting.com
Subject: Re: [CQ-Contest] possible changes for CQ VHF Contest

Analysis of logs submitted to ClubLog.

This is 2017 when it was introduced. I have to find the more recent analysis. 
It’s higher now.

https://g7vjr.org/2018/01/proportion-of-modes-used-on-the-air-2017-update/


Ria
N2RJ

On Wed, Jul 24, 2019 at 8:28 AM Edward Sawyer 
<EdwardS@sbelectronics.com<mailto:EdwardS@sbelectronics.com>> wrote:
"70% of ham traffic is now FT8."

I am curious where this datapoint is coming from?

Ed  N1UR
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com<mailto:CQ-Contest@contesting.com>
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
<Prev in Thread] Current Thread [Next in Thread>