CQ-Contest
[Top] [All Lists]

ARRL contest scores online

Subject: ARRL contest scores online
From: frenaye@pcnet.com (frenaye@pcnet.com)
Date: Wed Apr 19 22:43:05 1995
I haven't seen mention of it (unless it was posted when I was in 
black-hole mode) but the ARRL Contest Dept is now posting complete contest 
score information on the ARRL Info Server (and related FTP sites).  The 
intention is for the information to be posted the month after the contest 
results are printed in QST (ARRL members get it quicker!)

Scores from the 1994 ARRL 10 GHz, 1994 IARU HF Championship and 1994 ARRL 
160M contests are available now (file names:  10GHZ.SCR  IARU.SCR and 
160M.SCR).  There's a lot of additional information available - see below!

Thanks KR1R NF1J and K8CH!

73 - Tom

---------------Original Message---------------

HELP on using the ARRL's Automated Information Server (info@arrl.org)

   INFO is a service of ARRL HQ.  To use it, mail messages to:

   info@arrl.org

Each line of the message should contain a single command as shown 
below.  You may place as many commands in a message as you want.  
Each file you request will be sent to you in a separate message. 
Only ASCII text files are supported at present.

If you have FTP access, all of these files can be obtained 
from oak.oakland.edu by anonymous FTP in the files area 
pub/hamradio/arrl/infoserver.  Retrieve the file index.txt 
in this directory for a complete listing of available files 
listed by subdirectory with descriptions. 

W1AW bulletins featuring news of interest to all amateurs (such 
as FCC actions, DX news, satellite orbit data, propagation 
trends, SAREX mission information and other items) are available 
by email from the Netcom List Server.  To subscribe to this 
mailing list, send an email message to listserv@netcom.com with 
any subject (it is ignored) and the following text as the body of 
your message:

subscribe w1aw-list
quit

In addition, W1AW bulletins can also be FTPed from oak.oakland.edu 
in the directory pub/hamradio/barc/w1aw-list.  There are several 
subdirectories under this for each bulletin catagory.  See the 
W1AW bulletin description files (.des extension) for more 
information on each catagory. 

Binary files mentioned in QST that accompany articles are *NOT* 
available via the server.  This is an email service only and can 
not send binary files.  HOWEVER, these files are also available 
from oak.oakland.edu, in the directory pub/hamradio/arrl/qst-binaries

Valid INFO email commands:

help             Sends this help file

index            Sends an index of the files available from INFO

reply <address>  Sends the response to the specified address. Put this
                 at the BEGINNING of your message if your From: address
                 is not a valid Internet address.

send <FILENAME>  Sends "FILENAME" example: send PROSPECT.TXT

quit             Terminates the transaction (use this if you have
                 a signature or other text at the end of the message.)

Note: your message will *not* be read by a human!  Do not include 
any requests or questions except by way of the above commands. 
Retrieve the "USERS.TXT" file for a list of email addresses of 
ARRL HQ staff.

DO *NOT* USE YOUR MAILER'S REPLY FUNCTION TO SEND YOUR NEXT REQUEST!
This message is from info-serv@arrl.org.  Generate a new message 
addressed to info@arrl.org instead.  We set it up this way to 
prevent failed mail from looping endlessly, annoying system 
administrators.  Mail sent back to info-serv@arrl.org ends up in 
the bit bucket.

Your From: field or Reply-to: field in your header should contain a 
valid Internet address, including full domain name.  If your From: 
field does not contain a valid Internet address, the answer will not 
reach you.  However, we have recently added a reply function as a 
server command.  If needed, the REPLY command should be the first 
command in your message.

syntax:

reply mailaddr 

Where mailaddr is a valid Internet mail address (either user@domain 
or bang address accepted.)  An invalid address generates an error. 
A wrong address results in non-delivery of your response. 

The address given in the reply command is the address to which all 
subsequent requests in the message will be sent. 

If an error message is generated, it will be sent to the last reply 
address given.

If anyone needs some help with the server, or has ascii information 
files that they would like to archive on our server, additional 
information or updates for any of our files, or suggestions for 
improvements, please contact me here at ARRL Headquarters via email 
or telephone (203) 666-1541.

73 de ARRL HQ, Michael Tracy, KC1SX, mtracy@arrl.org 


Sample of files available from INFO: (There are lots more!)

FILENAME         SIZE DESCRIPTION
---------------- ---- --------------------
#Note - If you are not yet an Amateur Radio operator retrieve the
#file prospect (send prospect) for information on how to easily get
#started in this fun hobby. 

PROSPECT.TXT       2k How to get your Amateur Radio license
EXAMS.TXT         52k Current exam schedule info - updated bi-weekly
EXAMINFO.TXT       9k Examinations - what to bring - requirements
USERS.TXT          6k List of HQ Email addresses
ARRLCAT.TXT       39k Catalog of ARRL Publications - commercial content
JOIN.TXT           2k How become an ARRL member
SERVICES.TXT       5k A condensed list of ARRL membership services
TOUR.TXT          28k An electronic tour of ARRL Headquarters
DIR.HQ             5k Visiting ARRL HQ - diretions and tour information
HFBANDS.TXT        7k Breakdown of users of HF spectrum
W1AW.SKD           2k W1AW schedule of transmissions and operation
PRODREV.TXT       25k Listing of Product Reviews that appeared in QST
RFIGEN.TXT        37k How to solve an EMI/RFI problem - QST Lab Notes
RFISOURC.TXT      13k Where to buy filters - EMI-proof telephones etc.
ADDRESS.TXT       16k Lots and lots of ham/electonic company addresses
KITS.TXT           6k List of companies that sell kits
BBS.TXT           12k List of ham-radio land-line bulletin boards
HAMFAQ1.TXT       25k Introduction to the FAQ and Amateur Radio
HAMFAQ2.TXT       45k Amateur Radio Orgs, Services and Info Sources
HAMFAQ3.TXT       32k Amateur Radio Advanced and Technical Questions

Enjoy this ARRL service.  Please direct comments or suggestions (or 
flames) to mtracy@arrl.org.  73 from ARRL HQ, Michael Tracy, KC1SX 


----------End of Original Message----------

------------------------------------------------------
E-mail: frenaye@pcnet.com  
Tom Frenaye, K1KI, P O Box 386, West Suffield CT 06093
Phone: 203-668-5444



>From H. Ward Silver" <hwardsil@seattleu.edu  Thu Apr 20 03:59:32 1995
From: H. Ward Silver" <hwardsil@seattleu.edu (H. Ward Silver)
Subject: Bouvet Split Technique and ethics
Message-ID: <Pine.3.07.9504191952.B17540-c100000@bach.seattleu.edu>


On Thu, 20 Apr 1995, Bruce Strong wrote:
> >   
> >   On Tue, 18 Apr 1995, N6MM/W6BAB wrote:
> >   
> >   > > Ethics, schmethics...if you don't listen to the DX station and follow
> >   > > their instructions (even somewhat cryptic instructions) then I'd say 
> > your
> >   > > chances are pretty slim, regardless.  It was a fairly clever solution 
> > to
> >   > > some astounding pileups and separated the sheep from the goats rather 
> >   > > quickly.
> >   
> >   To me, and, evidently, just me, the ethics problem relates not to the
> >   cleverness of separating the 'sheep from the goats' but, by seemingly
> >   implying, or not making it clear, where he would be listening and,
> >   it also seems, to be giving out apparently misleading information -
> >   witness all your comments about the pileup being at the wrong place -
> >   the station is now taking up 3 places on the band; one for himself,
> >   one for the 'deserving', and one for the 'undeserving'.
> >   
> >   This would be ok, at least to me, if dx chaseing were the only game
> >   in town, but many, many amateur radio operators don't care to join
> >   the hunt and this technique necessarily clutters up the available
> >   spectrum more than other techniques might.
> >   
> >   Bruce
> >   hs0zbo@sura1.sut.ac.th

This does raise certain considerations of bandwidth.  I think it depends
on how much "spreading" is done.  I think it's perfectly acceptable to use
20kHz on phone; 7 SSB channels out of 70 available.  40kHz would be really
pushing it and the 100kHz used by 5A0RR was "right out"!  I would even
consider the use of several "auxiliary" channels up and down the band to
be OK.

The irritation comes, I believe, from DX activity on channels that usually
are more or less pileup-free; above 14275, say.  So if a bunch of DXers
just pounce on 290, regardless of who might be there, it can be a serious
pain to the other users.  This is the DX station's fault - he or she
should have listened to find a clear frequency first, not just blindly
choose a spot.  It's also the responsibility of the callers not to QRM a
busy frequency!

But back to the real issue - using bandwidth over time.  It's entirely
fair to suggest that by using more spectrum at any one given time, the
amount of bandwidth required over an extended period is actually reduced. 
For example, wide pileups on Day 1 and 2 of a big expedition, followed by
small listening segments on the remaining days.  An expedition of very
limited duration, like BS7H, can't take advantage of the bandwidth-time
savings, though.  Hmmm, bandwidth (cycles/sec) multiplied by time (sec) is
a dimensionless quantity (channel-seconds?) that would measure the overall
efficiency of a DXpedition.  The smaller the quantity, the less the
disruption to the other users of the band.

So to address the bottom line, DXing (and contesting activity, too) should
not be simply spread out everywhere, anytime.  DX stations and their
callers should avoid disruption when possible.  However, there are
techniques that are useful to more quickly reduce the volume of callers,
thus reducing the amount of bandwidth required in channel-seconds.  This
generally makes everybody happier, DXer and non-DXer alike.  Furthermore,
the higher the rate, the less the perceived need for misbehavior on both
sides.

73, Ward N0AX





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