-
Notifications
You must be signed in to change notification settings - Fork 24
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
QSO Detail - DXCC Statistics picks more entities as worked/confirmed than the one it should.. #601
Comments
Could you export and post a sample ADI with the pair of QSOs that are showing incorrectly? In looking at the code it looks like for the QSO Details/DXCC it should just be grouping by the DXCC in the log entries, so not sure why it would be doing that.
Also maybe post a screenshot of the Details panel for the KX6PC qso.
Thanks
Michael, AA5SH
… On Feb 18, 2025, at 12:32 PM, rsaue ***@***.***> wrote:
rsaue
created an issue
(foldynl/QLog#601)
Hi, I am using Qlog 0.42 on Linux/win/Mac, thank you for the steady progress in development.
Investigating an issue related to Lotw I found what i believe is a Bug in QLog.
I was checking out the V77WW Expedition to Marshall Island, I knew that i had the entity confirmed back in 1988 on 20 meter CW - Call KX6PC, which also is accepted by the DXCC program.
Clicking on KX6PC, enableling the QSO Detail Window with the DX Stats tab, I found that the Station Statistics were correct, but the DXCC Statistics field gave wrong information as it stated that I had a lot more bands and modes worked and confirmed on Marshall Islands.
Cleaning the database and importing the KX6PC and a random W-qso, showed that the DXCC Statistics field on Marshall Island picked the W-qsos. Doing a similar test on Franz Josef Island and a random UA1-qso, showed the same problem with the Franz Josef Island DXCC Statistics. Doing the same test on JW and LA (different entities. but same country) did not give similar false information. See enclosed screenshots..
It looks like the problem is in the DXCC statistics in the QSO detail only, as the Award View shows correct data.
73 de LB2EG Richard
Skjermbilde.fra.2025-02-18.19-04-43.png (view on web)
Skjermbilde.fra.2025-02-18.19-05-34.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
<https://github.com/user-attachments/assets/5057231c-40f5-42ea-974e-b2ade7755814>
<https://github.com/user-attachments/assets/2a76eded-0e56-4f84-80ae-fa312f593a22> <#601> <https://github.com/notifications/unsubscribe-auth/AUEEMXQYPJVZUA7LBJ4LI532QN4ELAVCNFSM6AAAAABXMKOU4WVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA3DCMRYGU3TANY>
rsaue
created an issue
(foldynl/QLog#601)
<#601>
Hi, I am using Qlog 0.42 on Linux/win/Mac, thank you for the steady progress in development.
Investigating an issue related to Lotw I found what i believe is a Bug in QLog.
I was checking out the V77WW Expedition to Marshall Island, I knew that i had the entity confirmed back in 1988 on 20 meter CW - Call KX6PC, which also is accepted by the DXCC program.
Clicking on KX6PC, enableling the QSO Detail Window with the DX Stats tab, I found that the Station Statistics were correct, but the DXCC Statistics field gave wrong information as it stated that I had a lot more bands and modes worked and confirmed on Marshall Islands.
Cleaning the database and importing the KX6PC and a random W-qso, showed that the DXCC Statistics field on Marshall Island picked the W-qsos. Doing a similar test on Franz Josef Island and a random UA1-qso, showed the same problem with the Franz Josef Island DXCC Statistics. Doing the same test on JW and LA (different entities. but same country) did not give similar false information. See enclosed screenshots..
It looks like the problem is in the DXCC statistics in the QSO detail only, as the Award View shows correct data.
73 de LB2EG Richard
Skjermbilde.fra.2025-02-18.19-04-43.png (view on web) <https://github.com/user-attachments/assets/5057231c-40f5-42ea-974e-b2ade7755814>
Skjermbilde.fra.2025-02-18.19-05-34.png (view on web) <https://github.com/user-attachments/assets/2a76eded-0e56-4f84-80ae-fa312f593a22>
—
Reply to this email directly, view it on GitHub <#601>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXQYPJVZUA7LBJ4LI532QN4ELAVCNFSM6AAAAABXMKOU4WVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA3DCMRYGU3TANY>.
You are receiving this because you are subscribed to this thread.
|
Hi , Enclosed is also a screenshot of the Details panel of the KX6PC QSO 73 de LB2EG Richard |
Ok I see what is going on. When the Country stats is updating currently it is decoding the callsign to determine the country and not looking at the current record to get the country. So KX6PC now is mapped to US. I have a potential fix for it by not sure if it is the best way @foldynl . I will put it in a pull request but there may be a better way. |
The fix is available - v0.42.1 |
Hi, I am using Qlog 0.42 on Linux/win/Mac, thank you for the steady progress in development.
Investigating an issue related to Lotw I found what i believe is a Bug in QLog.
I was checking out the V77WW Expedition to Marshall Island, I knew that i had the entity confirmed back in 1988 on 20 meter CW - Call KX6PC, which also is accepted by the DXCC program.
Clicking on KX6PC, enableling the QSO Detail Window with the DX Stats tab, I found that the Station Statistics were correct, but the DXCC Statistics field gave wrong information as it stated that I had a lot more bands and modes worked and confirmed on Marshall Islands.
Cleaning the database and importing the KX6PC and a random W-qso, showed that the DXCC Statistics field on Marshall Island picked the W-qsos. Doing a similar test on Franz Josef Island and a random UA1-qso, showed the same problem with the Franz Josef Island DXCC Statistics. Doing the same test on JW and LA (different entities. but same country) did not give similar false information. See enclosed screenshots..
It looks like the problem is in the DXCC statistics in the QSO detail only, as the Award View shows correct data.
73 de LB2EG Richard
The text was updated successfully, but these errors were encountered: