|
Post by w9mdb on Jan 10, 2023 22:30:28 GMT
I noticed false.txt and was wondering what's it tells us and how the time correlates to the decodes.
3C3CA was getting tagged but I was unable to correlate with the ALL.txt file. I see YYYYMMDD but what is the 2nd column? It's not minutes or seconds.
20230108 232628.897 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232628.976 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232629.211 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232629.289 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232629.431 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232629.528 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232629.603 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232629.697 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232658.855 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232658.949 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232659.346 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232659.398 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232659.517 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
20230108 232659.721 chkgrid 3C3CA JJ43 lgvalid F lchkcall F lwrongcall F
|
|
|
Post by Arvo ES1JA on Jan 11, 2023 14:17:10 GMT
hhmmss.ms
|
|
|
Post by w9mdb on Jan 11, 2023 14:39:36 GMT
OK...so none of the false.txt entries show up in the decoding log. What do the flags mean? What is it telling us? In this case it appears it is rejecting 3C3CA JJ43 which is valid.
|
|
|
Post by Arvo ES1JA on Jan 11, 2023 14:48:10 GMT
Jtdx “thinks” that JJ43 can’t be correct grid for this DXCC. I don’t know is it or not. If it is then jtdx needs a fix.
|
|
|
Post by Wolfgang OE1MWW on Jan 11, 2023 14:50:36 GMT
Mike, maybe I am wrong, but wasn't there a while ago a case, where such call signs goof the software as beeing a locator?
73's de OE1MWW Wolfgang
|
|
|
Post by w9mdb on Jan 11, 2023 15:03:15 GMT
QRZ does show JJ43 as valid for 3C3CA. So guess a fix is needed -- but the question now is how do we see what decode caused the message? Shouldn't they still show up in the ALL.TXT but get tagged? Or even in the decode window tagged so we can see when false positives are happening? 3C3CA for example would have been calling CQ and just getting dropped. I guess all the logic for this is reducing false decodes, pirate, or both?
|
|
|
Post by Arvo ES1JA on Jan 11, 2023 15:42:09 GMT
Yep JJ43 is correct, jtdx checks only for continent part, not island.
|
|
|
Post by w9mdb on Jan 11, 2023 15:52:24 GMT
I can't seem to find where this is printed to false.txt or where it causes the decode to be ignored. I'd like to see what decodes are getting tagged. If 3C3CA is getting blocked I'm really concerned about Bouvet coming up also getting blocked.
|
|
|
Post by Arvo ES1JA on Jan 11, 2023 18:28:49 GMT
It is not blocking decoding, just affect some AP decode false checks. I have done QSO with 3C3CA on many bands. Anyway this grid will be added to current code.
|
|