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

INITIAL_EXCHANGE handling #356

Open
dh5fs opened this issue Oct 24, 2022 · 2 comments
Open

INITIAL_EXCHANGE handling #356

dh5fs opened this issue Oct 24, 2022 · 2 comments

Comments

@dh5fs
Copy link
Contributor

dh5fs commented Oct 24, 2022

INITIAL_EXCHANGE is a nice thing for contests with a predefined exchange. It is tied together with RECALL_MULTS. This is a problem in a contest like WAG (DL side), because there are not only DOK's from the multi file are exchanged but also serial numbers from non-DL stations which should not get recalled. So both commands should not be coupled together.

@zcsahok
Copy link
Member

zcsahok commented Oct 25, 2022

I see the point. Not all DL stations are in the initial exchange file so there must be some other criterion to select whether to recall an exchange or not. (btw RECALL_MULTS is a misnomer as it recalls the exchange irrespective of whether it's a mult or not)

Maybe recall of exchanges looking like a serial number could be optionally disabled?

@dh5fs
Copy link
Contributor Author

dh5fs commented Oct 25, 2022

Yes, if that can be distinguished from numeric looking Mults? Now it recalls every exchange. For my use it would be fine if everything that is inside the initial exchange (if its used) file gets filled it and that's it. In the recent WAG all previous received serial numbers got recalled which was a bit annoying.

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

No branches or pull requests

2 participants