Re: wsjt-x QSO log import into L32


John Munton <JOHNG7SSE@...>
 

Gary

You could try using the ADIF Filter program available from here: http://sp7dqr.pl/en/converters.php

Have it filter your WSJT-X log by date based on the last qso in your Logger32 log.
This will produce a filtered ADI file of only new qso's which you can then import into Logger32.
You would of cause have to do this every time prior to import.

If you do try the program you may need to add FT8 and JT9 to its ADIF modes list.

73
John
G7SSE

------ Original Message ------
From: "Gary@... [hamlogger]" <hamlogger@...>
Sent: 16/10/2017 19:14:05
Subject: RE: [hamlogger] wsjt-x QSO log import into L32

 

Thanks Gerald.

 

Yes … but checking through the bad.adi is a separate, optional user activity after the import is done, which I suspect hardly ever gets done.  I’m suggesting it might be nice to know what’s going on under the covers while the import is happening. 

 

Personally I don’t think detected-and-skipped duplicate QSOs even qualify as “errors”: I’d quite like to know if there are any genuine errors in the ADIF (meaning data record/field formatting or content errors such as 160 or 99 or missing etc.), but at present any genuine errors may be buried under an unsightly pile of dupes.

 

If we were shown live counts of errors and dupes racking up during the import, it would also be clearer to the user that both are being identified and handled.

 

For bonus marks, I’d quite like to know if there are any ‘new ones’ in the import – perhaps sounding the same audio cues as are defined for new ones arriving on DXcluster (since I think the cluster feed is suspended during the import), and showing the counts e.g. “1 new DXCC, 3 new band-mode slots, 2 new IOTAs …” [I realise there are lots of ways to define ‘new ones’, hence it may be quite complicated to specify the requirement properly for Bob, but since the import function updates the statistics already, I’m naively suggesting giving us the option to notify us when it updates the stats].

 

73,

Gary  ZL2iFB

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Tuesday, 17 October 2017 2:15 a.m.
To: hamlogger@...
Subject: RE: [hamlogger] wsjt-x QSO log import into L32

 

 

Gary,

 

You may already know this, but looking at the bad.adi file that is generated during an import includes all the rejected qsos along with the reason they were rejected.

 

> Gerald, VE1DT



---In hamlogger@..., <Gary@...> wrote :

…. Talking of which, when we import an ADIF with duplicate records, the dupes are skipped but are identified as “Errors”: it might be nice if the import routine displayed the count of “Duplicates skipped” as well as “Errors” so we would know what was happening.

 

[Clearly this would be a nice-to-have, a low-priority idle suggestion.]

 

73,

Gary  ZL2iFB

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Monday, 16 October 2017 5:35 a.m.
To: hamlogger@...
Subject: Re: [hamlogger] wsjt-x QSO log import into L32

 

 

Peter:

 

Thanks for you reply and help. Some of the QSO's in that log are already in my L32 log. I am assuming that if I import the entire file, it will just ignore those QSO's that are already in the log?? I can edit the file and get rid of those QSO's that are already in my log if needed.

 

Thanks again

John Owens

Join hamlogger@groups.io to automatically receive all group messages.