Skip to content

Document new scoring mechanism (PR #390) - #525

Open
dl1jbe wants to merge 17 commits into
Tlf:masterfrom
dl1jbe:document_scoring
Open

Document new scoring mechanism (PR #390)#525
dl1jbe wants to merge 17 commits into
Tlf:masterfrom
dl1jbe:document_scoring

Conversation

@dl1jbe

@dl1jbe dl1jbe commented Aug 2, 2026

Copy link
Copy Markdown
Member

Work in Progress. Feedback is welcomed.

dl1jbe and others added 12 commits July 31, 2026 13:54
@dl1jbe
rework scoring rules (see issue Tlf#178)
8b9197d
@dl1jbe
Drop USE_COUNTRYLIST_ONLY keyword
d69c771 
Was used for control of point scoring. By leaving all point controlling
keywords (besides COUNTRYLIST_POINTS) undefined the same result can be
achieved.
@dl1jbe
Drop continentlist_only from scoring
68c5441 
* Do some further cleanup  and
* adapt test code
@dl1jbe
Drop superfluous variable
849d4ec
@zcsahok @dl1jbe
add test for spdx_dx
15c77d1
@dl1jbe
Readd USE_COUNTRYLIST_ONLY keyword as deprecated
d1e7494
@dl1jbe
Add missing spdxmults
1ef31bd
@zcsahok @dl1jbe
update rules/spdx_dx
591681f 
* set Cabrillo contest name
* add SERIAL_OR_SECTION to get rid of annoying "section?" question
* remove USE_COUNTRYLIST_ONLY
@dl1jbe
Typos
ded2868
@dl1jbe
Move keywords for country/continent scoring to one place
2574d14
@dl1jbe
Move BANDWEIGHTPOINTS keyword to points section
76549e3
@dl1jbe
Fix description of USE_CONTINENTLIST_ONLY
f341e46
@dl1jbe dl1jbe mentioned this pull request Aug 10, 2026
Closed
@zcsahok zcsahok mentioned this pull request Aug 11, 2026
Merged
@zcsahok

zcsahok commented Aug 16, 2026

Copy link
Copy Markdown
Member

Minor comment: 2EU3DX_POINTS is not deprecated, it is not supported at all.

Maybe a reference to the delivered rules would be helpful as they can serve as a starting point for a new contest.

@dl1jbe

dl1jbe commented Aug 23, 2026

Copy link
Copy Markdown
Member Author

Minor comment: 2EU3DX_POINTS is not deprecated, it is not supported at all.

Maybe a reference to the delivered rules would be helpful as they can serve as a starting point for a new contest.

Thanks for reminding. It got dropped in 2013 but mentioned as 'deprecated' in man page and left as comments in some rules. So time to go. Will drop it.

@dl1jbe

dl1jbe commented Aug 26, 2026

Copy link
Copy Markdown
Member Author

Finished documentation of point scoring logic. Feedback is welcomed.

@dl1jbe
dl1jbe requested a review from zcsahok August 26, 2026 08:48
zcsahok
zcsahok reviewed Aug 29, 2026
View reviewed changes
Comment thread tlf.1.in
points and multipliers.
.
.P
.B POINTS

@zcsahok zcsahok Aug 29, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All-caps make it look like a keyword. (Multipliers further below is ok)

Adding a .P after .B would avoid the run together of the title and the text:

       Points Parameters controlling point scoring are listed below.  Not  all
       can be combined arbitrarily.  To use them correctly one should be aware

v.

       Points

       Parameters controlling point scoring are listed below. Not all  can  be
       combined arbitrarily.  To use them correctly one should be aware of the

Comment thread tlf.1.in
.
.P
.B POINTS
Parameters controlling point scoring are listed below. Not all can

@zcsahok zcsahok Aug 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about this wording?

Not all parameters can be combined arbitrarily. To use them correctly, one should be aware of the evaluation order, in order of precedence, discussed below.

Comment thread tlf.1.in
\(bu Any contact which is evaluated as \fIdupe\fR gets zero points.
.
.P
\(bu If a python plugin module ist used for the contest (see

@zcsahok zcsahok Aug 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: ist

Comment thread tlf.1.in
contacts with portable stations can be honored (see \fBPORTABLE_MULT_2\fR).
.
.P
\(bu Finally the default scoring is done by evaluating the country prefix

@zcsahok zcsahok Aug 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alt. wording/punctuation?

Finally, the default scoring is performed by evaluating the country prefix of the other station. This is controlled by the following parameters, in order of precedence.

Comment thread tlf.1.in
.TP
\fBCOUNTRYLIST\fR=\fI"comma separated list of prefixes"\fR
e.g. SM,LA,OZ,OH.
E.g. SM,LA,OZ,OZ

@zcsahok zcsahok Aug 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OZ is now twice, OH removed?

Comment thread tlf.1.in
multiplied score.
.
.P
.B Multipliers

@zcsahok zcsahok Aug 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as for Points: an extra .P would make it stand out clearer

Comment thread tlf.1.in
.
.IP
Bands not in the list are weighted by 1.
Count as multi only if worked stations continent is CONTINENTLIST.

@zcsahok zcsahok Aug 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

multi -> multiplier

@zcsahok

zcsahok commented Aug 29, 2026

Copy link
Copy Markdown
Member

This PR shall be about the man page only, Would it be possible to say rebase this branch on current master?

@N0NB

N0NB commented Aug 30, 2026

Copy link
Copy Markdown
Member

As I was setting up for the KS QP this weekend I became a bit confused over the options for GENERIC_MULT as my old rules file had ONCE and the updated file in the master branch also has ONCE. However, the man page references ALL. Looking at the source I did find the two keywords are still accepted to do the same thing. Regardless, I can report that all mults were counted correctly.

I see the man page has ALL as the name to use but no mention that ONCE is deprecated. Also that section states "see above" but I didn't find anything about a multiplier counting rule. This should refer to a specific option rather than some unknown place in previous text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zcsahok zcsahok zcsahok left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dl1jbe @zcsahok @N0NB