CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] Does Using ViewProp Make You Assisted

To: <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] Does Using ViewProp Make You Assisted
From: "Rick Kiessig" <kiessig@gmail.com>
Date: Sun, 24 Nov 2013 18:48:53 +1300
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
While I agree that using ViewProp in its current form would make someone
assisted, I also think it would help everyone if the contest rules were less
ambiguous.

Exactly what is meant by "providing call signs" and "multiplier
identification" and "along with frequency information"? Concrete examples of
what's allowed and what's not would be very helpful.

Especially with increasing use of new and innovative forms of cheating (not
always purposeful), I would like to suggest a new approach for next season.
Rather than focusing on specific technologies, such as Skimmer or ViewProp,
which will always be a moving target, why not draw the line between assisted
and unassisted in a very clear, unambiguous place:

Unassisted means no connections to the outside world, and no radio or
contest related help from someone there in person. No Internet, phone, HT,
satellite, or anything similar. Any such devices must be unplugged, turned
off, or definitively not accessible to participants for the entire duration
of the contest.

Assisted allows Internet access.

This would allow unassisted contesters to use any technology they wish,
provided it runs entirely at their location. That might be a local Skimmer
or other decoding software, or something new like ViewProp, provided it
didn't connect to the Internet.

This would also put the focus back on what you can build and integrate at
your site. Tinkering is a big part of the hobby for many of us, and that
should include software.

If adopted exactly as above, this would also put remote operations
automatically into the assisted category.

I realize there is still a strong sentiment for "a boy and his radio" type
contesting on the unassisted side. Unfortunately, with technology the way it
is now, that line is hard to draw, and pretty much impossible to enforce.

BTW, one reason this is an issue for me (other than as the author of
ViewProp), is that the number of people who compete as assisted in this part
of the world is relatively small compared to unassisted -- and competing
against very small group turns a contest into something else entirely.

73, Rick ZL2HAM / ZM1G


-----Original Message-----
From: CQ-Contest [mailto:cq-contest-bounces@contesting.com] On Behalf Of
Chris Hurlbut
Sent: Wednesday, November 20, 2013 3:29 PM
To: Ken Widelitz
Cc: cq-contest@contesting.com
Subject: Re: [CQ-Contest] Does Using ViewProp Make You Assisted

Of course it makes you assisted.
It provides "multiplier identification" as far as I'm concerned.  What a
great way to keep an eye on 10m during marginal conditions!  When are the
single ops in the Caribbean firing up on 160?  Easy, just look at the map!


No frequency information required.  You know it's open, you will find them.
1000 examples would be easy to come up with, but a debate is not required in
this case.
-Chris KL9A


On Mon, Nov 18, 2013 at 9:01 PM, Ken Widelitz <widelitz@gte.net> wrote:

>
>    I've just downloaded and started to plan with ViewProp. What a neat 
> tool!
>    If I don't display the path grid which shows call signs, does 
> displaying the
>    DX Atlas map that ViewProp creates make me assisted?
>    Per CQWW rule VIII 2. QSO alerting assistance: The use of any 
> technology or
>    other source that provides call sign or multiplier identification 
> along with
>    frequency information to the operator.
>    I think viewing the DX Atlas map is NOT assistance per rule VIII, 
> since it
>    doesn't show call signs and frequencies. The ViewProp grid does not 
> tie into
>    my band maps, so I can't see the calls and frequencies there either.
>    73, Ken, K6LA / VY2TT


_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

<Prev in Thread] Current Thread [Next in Thread>