Re: [wsjt-devel] Logging Issue

[Ed Wilson via wsjt-devel]

Thanks, Joe...r8591 fixed this little "glitch".
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/ 

On Thursday, March 29, 2018, 10:47:03 AM EDT, Ed Wilson via wsjt-devel 
 wrote:  
 
 I reverted back to r8576 and this anomaly did not appear.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/ 

On Thursday, March 29, 2018, 8:58:24 AM EDT, Ed Wilson via wsjt-devel 
 wrote:  
 
 I am currently running WSJT-X 1.9-rc3 r8590. I have set the option to have the 
program prompt me to log a QSO. I noticed this morning that upon a prompt, the 
Report Rcvd field is blank and that I have to enter that value manually.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Ed Wilson via wsjt-devel]

I reverted back to r8576 and this anomaly did not appear.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/ 

On Thursday, March 29, 2018, 8:58:24 AM EDT, Ed Wilson via wsjt-devel 
 wrote:  
 
 I am currently running WSJT-X 1.9-rc3 r8590. I have set the option to have the 
program prompt me to log a QSO. I noticed this morning that upon a prompt, the 
Report Rcvd field is blank and that I have to enter that value manually.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Bill Somerville]

On 12/03/2018 21:05, Louis Ricci wrote:

Just for my own information, what is the difference between wsjtx.log and
wsjtx_log.adi?


Hi Lou,

the fromer is in CSV format and is write only by WSJT-X, the latter is 
in ADIF format and is read in full on WSJT-X startup to load the 
in-memory worked before callsigns and DXCC entities, it is also written 
to when you log QSO.


The ADIF format is the main log because it is the most versatile 
allowing QSOs to be transferred both out and into WSJT-X or other 
logging applications.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Louis Ricci]

Bill,

My apologies.  I was under the impression that wsjtx.log was the main
logfile, and that wsjtx_log.adi was for convenience, since WSJT-X proves an
option to deleted the .adi and it operates (pretty much) properly when the
.adi is deleted, showing may CQs in GREEN.

I will attempt what you suggest.

Just for my own information, what is the difference between wsjtx.log and
wsjtx_log.adi?

Many thanks

73
Lou

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, March 12, 2018 4:55 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Logging Issue

On 12/03/2018 20:44, Louis Ricci wrote:
> It's not ALL QSOs  that are show up as not previously worked, only 
> some of them.  If I have one giant .adi file that never gets deleted, 
> then every time I import it into my main logger, all of those QSOs get 
> duplicated.  The next time make some additional contacts and import it 
> again, then there will be a bunch of triplicates and so on.  It's a 
> real pain to then manually delete the dupes.  As an experiment, I just 
> made some QSOs, deleted the .adi shut down and restarted WSJT-X and I 
> am seeing a bunch of 'green'  stations calling CQ .
>
> Is there nothing else that might be done?

Lou,

WSJT-X needs a complete log file to be able to tell you who has been worked
before and what DXCC Entities are new. The wsjtx_log.adi is that file.

If you main logging application doesn't have an option to ignore duplicates
when importing an ADF file then I suggest you ask the
author(s) to consider adding such a feature, other users will appreciate it
too.

I'm not sure what you are asking for here, either you keep a complete
logfile for WSJT-X or you use some other method of detecting worked before
stations. If you are on Windows and use one of the logging applications
supported by JTAlert then that may well be you best solution.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Bill Somerville]

On 12/03/2018 20:44, Louis Ricci wrote:

It's not ALL QSOs  that are show up as not previously worked, only some of
them.  If I have one giant .adi file that never gets deleted, then every
time I import it into my main logger, all of those QSOs get duplicated.  The
next time make some additional contacts and import it again, then there will
be a bunch of triplicates and so on.  It's a real pain to then manually
delete the dupes.  As an experiment, I just made some QSOs, deleted the .adi
shut down and restarted WSJT-X and I am seeing a bunch of 'green'  stations
calling CQ .

Is there nothing else that might be done?


Lou,

WSJT-X needs a complete log file to be able to tell you who has been 
worked before and what DXCC Entities are new. The wsjtx_log.adi is that 
file.


If you main logging application doesn't have an option to ignore 
duplicates when importing an ADF file then I suggest you ask the 
author(s) to consider adding such a feature, other users will appreciate 
it too.


I'm not sure what you are asking for here, either you keep a complete 
logfile for WSJT-X or you use some other method of detecting worked 
before stations. If you are on Windows and use one of the logging 
applications supported by JTAlert then that may well be you best solution.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Louis Ricci]

Hi Bill,

It's not ALL QSOs  that are show up as not previously worked, only some of
them.  If I have one giant .adi file that never gets deleted, then every
time I import it into my main logger, all of those QSOs get duplicated.  The
next time make some additional contacts and import it again, then there will
be a bunch of triplicates and so on.  It's a real pain to then manually
delete the dupes.  As an experiment, I just made some QSOs, deleted the .adi
shut down and restarted WSJT-X and I am seeing a bunch of 'green'  stations
calling CQ .

Is there nothing else that might be done?

Thanks for your support

Lou

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, March 12, 2018 4:34 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Logging Issue

On 12/03/2018 20:14, Louis Ricci wrote:
> The original .adi file are gone

Hi Lou,

there is you problem then. I suggest you select all the JT9/JT65/JT9 QSOs in
your main station log and export an ADIF file of them. Rename that file
wsjtx_log.adi and put it into the WSJT-X log file directory and leave it
there.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Bill Somerville]

On 12/03/2018 20:14, Louis Ricci wrote:

The original .adi file are gone


Hi Lou,

there is you problem then. I suggest you select all the JT9/JT65/JT9 
QSOs in your main station log and export an ADIF file of them. Rename 
that file wsjtx_log.adi and put it into the WSJT-X log file directory 
and leave it there.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Louis Ricci]

The original .adi file are gone, but the fact that they are in my main
logging program (because I imported the .adi's into it) twice would indicate
that they were in fact in the .adi

Thanks,
Lou

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, March 12, 2018 4:08 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Logging Issue

On 12/03/2018 19:59, Louis Ricci wrote:
> No, it wasn't.
>
> Some examples are MI0LLG, VA3HP, K4GHS
>
> Excerpt from the log file:
>
> 2018-03-04,20:36:45,2018-03-04,20:37:45,MI0LLG,IO65,14.075858,FT8,-05,
> -04,,,
> <== First time
> 2018-03-12,19:14:45,2018-03-12,19:16:15,MI0LLG,IO65,14.075369,FT8,-06,
> -09,,, <== Duplicate 'cause I didn't realize I worked him before
>
> 2018-03-12,13:54:45,2018-03-12,13:55:45,VA3HP,EN92,7.076022,FT8,-17,-1
> 1,,, 
> 2018-03-12,17:48:30,2018-03-12,17:49:30,VA3HP,EN92,7.075005,FT8,-01,+0
> 7,,,
>
> 2018-03-12,13:49:15,2018-03-12,13:50:15,K4GHS,EM96,7.076104,FT8,+02,-0
> 2,,, 
> 2018-03-12,17:42:15,2018-03-12,17:43:45,K4GHS,,7.075521,FT8,-16,-08,,,
> <== Just noticed that Grid is missing.  Could that be a factor?

HI Louis,

can you check if those QSOs are in the other WSJT-X log file, the ADIF one
called wsjtx_log.adi, in the same place. We have had anther report of
missing QSOs in the ADIF file so there may be a defect where that gets
written.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Bill Somerville]

On 12/03/2018 19:59, Louis Ricci wrote:

No, it wasn't.

Some examples are MI0LLG, VA3HP, K4GHS

Excerpt from the log file:

2018-03-04,20:36:45,2018-03-04,20:37:45,MI0LLG,IO65,14.075858,FT8,-05,-04,,,
<== First time
2018-03-12,19:14:45,2018-03-12,19:16:15,MI0LLG,IO65,14.075369,FT8,-06,-09,,,
<== Duplicate 'cause I didn't realize I worked him before

2018-03-12,13:54:45,2018-03-12,13:55:45,VA3HP,EN92,7.076022,FT8,-17,-11,,,
2018-03-12,17:48:30,2018-03-12,17:49:30,VA3HP,EN92,7.075005,FT8,-01,+07,,,

2018-03-12,13:49:15,2018-03-12,13:50:15,K4GHS,EM96,7.076104,FT8,+02,-02,,,
2018-03-12,17:42:15,2018-03-12,17:43:45,K4GHS,,7.075521,FT8,-16,-08,,,
<== Just noticed that Grid is missing.  Could that be a factor?


HI Louis,

can you check if those QSOs are in the other WSJT-X log file, the ADIF 
one called wsjtx_log.adi, in the same place. We have had anther report 
of missing QSOs in the ADIF file so there may be a defect where that 
gets written.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Louis Ricci]

Hi Bill,

No, it wasn't.

Some examples are MI0LLG, VA3HP, K4GHS

Excerpt from the log file:

2018-03-04,20:36:45,2018-03-04,20:37:45,MI0LLG,IO65,14.075858,FT8,-05,-04,,,
<== First time
2018-03-12,19:14:45,2018-03-12,19:16:15,MI0LLG,IO65,14.075369,FT8,-06,-09,,,
<== Duplicate 'cause I didn't realize I worked him before

2018-03-12,13:54:45,2018-03-12,13:55:45,VA3HP,EN92,7.076022,FT8,-17,-11,,,
2018-03-12,17:48:30,2018-03-12,17:49:30,VA3HP,EN92,7.075005,FT8,-01,+07,,,

2018-03-12,13:49:15,2018-03-12,13:50:15,K4GHS,EM96,7.076104,FT8,+02,-02,,,
2018-03-12,17:42:15,2018-03-12,17:43:45,K4GHS,,7.075521,FT8,-16,-08,,,
<== Just noticed that Grid is missing.  Could that be a factor?


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, March 12, 2018 3:45 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Logging Issue

On 12/03/2018 19:37, Louis Ricci wrote:
> I had a QSO with that station several days ago on 20.  Wondering why 
> wasn’t the CQ displayed in GREEN, I opened the wsjtx.log file and sure 
> enough, the WSO was in the file.

HI Lou,

was the offending callsign a KG4 plus three or KG4 plus one format? If so
then there is a defect in WSJT-X v1.8.0 related to this, it has been
repaired for subsequent releases.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logging Issue

[Bill Somerville]

On 12/03/2018 19:37, Louis Ricci wrote:
I had a QSO with that station several days ago on 20.  Wondering why 
wasn’t the CQ displayed in GREEN, I opened the wsjtx.log file and sure 
enough, the WSO was in the file.


HI Lou,

was the offending callsign a KG4 plus three or KG4 plus one format? If 
so then there is a defect in WSJT-X v1.8.0 related to this, it has been 
repaired for subsequent releases.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel