[upl-image-preview url=https://storage.hamcq.cn/2024-09-29/1727614312-887310-image.png] [upl-image-preview url=https://storage.hamcq.cn/2024-09-29/1727614318-612094-image.png] 想完成DX100的目标，发现好多FT8通联完成后，对方不一定会上传日志，所以无法记录为有效通联。但是在JTDX软件上，已经记录过的DXCC，不会再把该DXCC重新标记新的DXCC，有什么办法可以把这部分未确认的QSO剔除，让JTDX重新标记成新的DXCC。

@"BI7ALG"#p34980 我也想知道，但他好像会记录到日志文件，然后日志文件里面可以编辑删除，但是。。。有点累

@"dovesky"#p34984 主要是不好把通联日志删掉重来，始终会面临这个问题，尤其是DXCC超过50个以后，新的DXCC会变得更加稀有，一些已经通联过，却没有确认通联的QSO，无法在软件上反馈是未有效确认通联的新的DXCC。

同问此问题。短波萌新，正在搞DXCC100 目前实体56，确认才三十多

未确认不代表对方没和你通联完成,只是对方可能未上传到LOTW,日志要养成一个习惯,通了就不要随便删(个别比赛除外),没准什么时候对方就上传了

DXCC的数量可以通过GT网格助手,或者各log平台查询,而不是确认了,你就留着,暂时没确认你就要删掉,这是各不负责的做法

@"BD3OOX"#p35053 已上传的日志不会删，主要是想JTDX的日志要把未确认通联的QSO部分删除，否则JTDX不会重新标记成未通联过的DXCC。

你只是想要有重点提示,用GT网格助手,他有log确认对比和音频提示

@"BI7ALG"#p35055 不建议你这么做,因为本地保存的才是你的财富,上传的日志一个是下载难,一个是下载的数据不如你本地的完整,因为各大日志网站都有自己的储存规则,会去除一些他认为没用的数据

建议就是你把jtdx的"每波段,每模式"和下面"新dxcc 波段/模式"勾上,这样会在当前波段如果你没通过做出提示

How to remove unconfirmed communication logs in FT8?

BI7ALG

I was trying to achieve DX100, but I found that even after successful FT8 contacts, the other person might not upload logs, making it impossible to record them as valid contacts.
However, in the JTDX software, DXCCs that have already been recorded will not be re-marked as new DXCCs. What is the way to remove these unconfirmed QSOs and allow JTDX to re-mark them as new DXCCs?

dovesky

BI7ALG I also want to know, but it seems like it will be logged in a file, and then I can edit or delete that file... but it's a bit tiring.

BI7ALG

dovesky The main problem is that deleting and re-establishing Logbook of The Observers (LOB) connections always leads to this issue, especially when you have more than 50 DXCC contacts. New DXCCs become increasingly rare, and some QSOs may be established without confirmation, making it impossible to accurately reflect in the software that these new DXCCs have not been successfully confirmed.

BH7HQT

It is recommended to manually edit the adif file.

BI4PMQ

I also have this question. Shortwave DXing is a new hobby I'm exploring, and I'm currently working on completing DXCC 100.
Currently, there are 56 entities, but only around 30 have been confirmed.

BD3OOX

Not confirmed does not mean that the other party has not communicated with you and completed the exchange. However, it is possible that the other party has not uploaded it to LOTW. It's important to establish a habit of logging communications; once a communication is made, do not delete it arbitrarily (except in specific cases). There may be a chance that the other party will upload it later.

BI7ALG

BD3OOX The uploaded logs will not be deleted. The main reason is to remove the unconfirmed QSO parts from JTDX's logs, so that JTDX can re-mark them as DXCC QSOs that have not been connected.

BD3OOX

The number of DXCCs can be obtained through the GT Grid Assistant or various logging platforms. If you haven't confirmed them yet, keep them for now; if you haven't confirmed them, delete them immediately. This is a practice that each platform takes responsibility for.

BD3OOX

BI7ALG I don't recommend doing that, because keeping your logs locally is the best way to preserve them. Uploading logs has two main drawbacks: it's difficult to download them, and the downloaded data will be incomplete compared to what you have stored locally. This is because major logging websites all have their own rules for storing data, which means they may remove some information that they deem unnecessary.

BD3OOX

I just want a focused reminder, using the GT grid assistant, which provides log confirmation and audio cues.

BD3OOX

The suggestion is that you check off "each segment, each mode" for jtdx and the following "new dxcc segment/mode", so that a prompt will appear if you haven't made contact in the current segment.

BD7PPD-xiaohei-lv

It feels like a straightforward Python script could solve this, so just write one!

闽ICP备2021006864号-7

闽公网安备35020602002794号互联网举报中心

用户协议隐私政策社区规范积分规则中继规则转载须知
更新日志联系我们常见问题友情链接运营报告赞助

浩奇科技（厦门）有限公司

是无线电，把我们联系在一起