[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tlf-devel] Tlf with ARRL 160m, some thoughts

From: Nate Bargmann
Subject: Re: [Tlf-devel] Tlf with ARRL 160m, some thoughts
Date: Sun, 6 Dec 2015 10:45:45 -0600
User-agent: Mutt/1.5.23 (2014-03-12)

* On 2015 06 Dec 09:53 -0600, Thomas Beierlein wrote:
> Hi Nate and others,
> let me first congrats to your 160m results. Well done.

Thanks, Tom.

I was a bit disappointed to not make a complete QSO with C6AUM early
this morning.  He couldn't quite pull me out this year so I never had a
chance to see Tlf count a 5 point QSO.  I did have one dupe call me this
AM and Tlf correctly scored it at zero points.

I opened an issue against my repository this morning where I worked the
ONE (Ontario East) section and Tlf counted it as NE (Nebraska).  When I
did work an NE station later, no additional mult was counted.  I need to
go through the logic on that one.

> Am Sat, 5 Dec 2015 08:31:39 -0600
> schrieb Nate Bargmann <address@hidden>:

> > Sort out the cases where some cty.dat entities are ARRL sections or
> > entities.  For the most part this would affect ARRL 160, ARRL FD, and
> > ARRL SS where all US territories are counted as an ARRL section.  For
> > other events such as ARRL DX they are entities rather than sections,
> > as I recall, so there may need to be an addition rules file keyword
> > and some logic added.
> > 
> What kind of support do you have in mind? Some new scoring keywords?

Right now as I incompletely understand the logic, the issue appears a
bit tricky and I don't have a solution handy at the moment.  What I did
was a trick offered on this list a year ago and I simply deleted the
conflicting entities from a local copy of cty.dat placed in the working

Since I didn't actually get a chance to try this in the contest since
the only one of those entities I heard, KP2 in VI, did not hear me, I
can only go by my tests before the contest.  In those tests with an
unmodified cty.dat, with the DX_&_SECTIONS keyword in the rules file Tlf
chose to apply the mult for the entity rather than the section even
though it took my entry in the exchange field.  More testing is needed.

Perhaps the solution is to include two section files in the
distribution, one with all the sections and the other with just the
mainland sections for ARRL DX.  I think the logic would still need to be
looked at in the case where a US entity appears in cty.dat, did the op
enter a section abbreviation for the exchange, if so, then count it as a
section, etc.

As the next event where this will be an issue is over six months away,
there is some time for me to study this more.

73, Nate


"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]