-
Notifications
You must be signed in to change notification settings - Fork 12
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
Improve QSO exchanges after entering partial callsign #315
Comments
Here is the link to build v1.85-dev.3 which includes this change. |
When running a simulation, sometimes a callsign is copied incorrectly and entered into the Callsign exchange entry field. After hitting Enter, the partial callsign is sent. The calling station will respond with a corrected callsign and optionally the exchange information. There are two scenarios. 1 - User sends partial call only (using F5 function key)This condition can easily be created by following these steps:
State
|
Original | Freq | Revised (v1.85) | Freq |
---|---|---|---|
DE <call> |
50% | DE <call> |
16.7% (1/6) |
DE <call> <call> |
50% | DE <call> <call> |
16.7% (1/6) |
. | . | <call> <call> |
16.7% (1/6) |
. | . | <call> <call> <exch> |
16.7% (1/6) |
. | . | <call> <exch> |
33.3% (1/3) |
The following is the new code showing the responses for this case (osNeedCallNr
).
// osNeedCallNr - They have sent an almost-correct callsign.
osNeedCallNr:
if (RunMode = rmHst) then
Result := msgDeMyCall1
else
case Trunc(R2*6) of
0: Result := msgDeMyCall1; // DE <my>
1: Result := msgDeMyCall2; // DE <my> <my>
2: Result := msgMyCall2; // <my> <my>
3: Result := msgMyCallNr2; // <my> <my> <exch>
4,5: Result := msgMyCallNr1; // <my> <exch>
end;
2 - User sends partial call and their exchange (using Enter key)
This condition can easily be created by following these steps:
- start a simulation in Single Call mode.
- Enter the calling callsign, but change the last letter.
- Hit
Enter
to send the partial callsign and exchange - This will now enter the
osNeedCall
state. - The calling station will send a response with the corrected callsign and exchange.
State osNeedCall
The following messages are sent after receiving a partially-correct callsign and exchange information from the user.
The first column shows the original messages and the second column shows the revised messages.
Notice the revised messages are now always sending the exchange. I suppose I should leave out the exchange on one of these.
Original | Freq | Revised (v1.85) | Freq |
---|---|---|---|
DE <call> <exch> |
50% | DE <call> <exch> |
16.7% (1/6) |
DE <call> <call> <exch> |
25% | DE <call> <call> <exch> |
16.7% (1/6) |
<call> <call> <exch> |
25% | <call> <call> <exch> |
33.3% (1/3) |
. | . | <call> <exch> |
33.3% (1/3) |
The following is the new code showing the responses for this case (osNeedCall
).
// osNeedCall - I have their Exch (NR), but need user to correct my call.
osNeedCall:
if (RunMode = rmHst) then
Result := msgDeMyCallNr1
else
case Trunc(R2*6) of
0: Result := msgDeMyCallNr1; // DE <my> <exch>
1: Result := msgDeMyCallNr2; // DE <my> <my> <exch>
2,3: Result := msgMyCallNr2; // <my> <my> <exch>
4,5: Result := msgMyCallNr1; // <my> <exch>
end;
After entering a partial callsign and exchange information, the user will hit `Enter` to finish the QSO and log the QSO. The QSO is not logged. This was caused by the logging module only comparing for a perfect match against the caller callsign and not considering the common occurrence of a partially-correct callsign. Code was changed to allow a partially-correct callsign. This allows these QSO to be included in the log as expected. Checkin notes: ``` Improve handling of partial callsign matches - Report both callsign and exchange errors in QSO log. - Add argument to IsMyCall to enable random result for lids. ``` Issue #315 will add improved messages for the partially-correct callsign case. This next review will be posted soon. Once the second pull request/review is submitted, I will post an engineering build for testing. Stay tuned...
Closing this. |
Summary
When the user has copied only part of the simulated callsign, the station will respond by repeating its callsign and sometimes its exchange. When doing so, there are currently limited messages being returned. Actual contests use different and shorter messages as compared to the MRCE simulation. This change is related to Issue #314.
Motivation
Improved realism. One of the goals of MRCE is to create a realistic contest simulation. This change will improve the realism of the contest exchange when partial callsigns are entered.
Detailed Description
After the user enters a partially-correct callsign, the existing simulation will return the following messages:
Seasoned contesters will minimize the length of messages being sent by eliminating the
DE
and sending both corrected call and exchange information. To that end, we will add the following (shorter) messages:Both sets of response messages should be sent in a random manner with priority given to the shorter messages.
Additional context
I found this paper, Do's and Don'ts of CW Contesting and More Do’s and Don’ts in CW Contesting, written by Rob Brownstein, K6RB. It discusses recommended practices for CW Contesting. It was posted by the K1USN group who sponsor the weekly CWOPS SST Contest. I thought it was a good read.
On page 2 of the second article in the above link, it mentioned:
Based on the above, we should keep the exchange after the corrected callsign and increase the frequency of responses of this type. We also want to shorten the responses as mentioned in the article.
Tasks
The text was updated successfully, but these errors were encountered: