Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

North American Exchange Hanling #373

Closed
VictorDenisov opened this issue Jan 13, 2023 · 2 comments · Fixed by #383
Closed

North American Exchange Hanling #373

VictorDenisov opened this issue Jan 13, 2023 · 2 comments · Fixed by #383

Comments

@VictorDenisov
Copy link
Contributor

VictorDenisov commented Jan 13, 2023

What would be the best way to approach NA qso party exchange?
NA qso party requires sending name and state.
I use SERIAL_OR_SECTION exchange option.
If I put name and state in the field then it doesn't understand that state is a multiplier.
If I flip the order then it drops the name field:

40CW  13-Jan-23 05:17 0001  AA6BT          ---  ---  MB SAM                 1         
40CW  13-Jan-23 05:17 0002  W6UU           ---  ---  CA            CA       1         

Is there any way to fix it with what is available. Or will it require more development?

@zcsahok
Copy link
Member

zcsahok commented Jan 13, 2023

It seems that the received name is not used at all. Here are the rules: https://ncjweb.com/NAQP-Rules.pdf
So is your second QSO a valid one? If yes, then just don't log the name. 😄
If the name is required, then it's somewhat analogous for example to HA-DX: one country or region is kind of "zoomed in". For this #347 provides a solution.

SERIAL_OR_SECTION is for the case when DX stations send a serial number. Here DX sends name only.

@VictorDenisov
Copy link
Contributor Author

Name is not used indeed, but it needs to be reported in the submitted log. I can use TLF with WYSIWYG multipliers configuration, but then the score won't be correct during the contest.

@zcsahok zcsahok linked a pull request Mar 20, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants