Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

I cannot agree more This subject deserves its own environment. Please keep it away from the devel list 73, Serge On 08/03/2021 23:13, Joe Taylor wrote: Hi Dave, I was not looking for confrontation, at all.  Just looking to help you and all readers of this list to have convenient access to

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Joe: Neither am I looking for confrontation. But that's what I've gotten from a small vocal minority of this list: confrontation, hatred and bullying. When I approached you privately, off-list, about the bullying and hatred: you told me to "ignore it". I can attach a copy of your response to my

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Hi Dave, I was not looking for confrontation, at all. Just looking to help you and all readers of this list to have convenient access to the information you're most interested in, on the appropriate list. -- 73, Joe, K1JT On 3/8/2021 2:21 PM, Dave Slotter, W3DJS wrote: K1JT: Are

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Il 08/03/21 15:34, Joe Taylor ha scritto: Hi all, Perhaps it's time to move discussion of "update_wsjtx_log.py" onto another email list.  Other WSJT-related software, including derivative programs (JTDX, MSHV, JS8Call, ...) as well as

[wsjt-devel] JT65 shorthands and "q3" decodes in Q65

Hi all, Several people have asked recently about relative sensitivities of the two-tone shorthand messages in JT65, which have been widely used for EME QSOs for nearly 20 years, and the "q3" decodes in Q65. Facts relevant for EME on VHF bands are summarized in the attached plot. The

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

K1JT: Are you stating this as a personal opinion, or as the moderator of the wsjt-devel@lists.sourceforge.net mailing list? -- Dave Slotter, W3DJS On Mon, Mar 8, 2021 at 1:38 PM Joe Taylor wrote: > Hi all, > > Perhaps it's time to move discussion of

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Hi all, Perhaps it's time to move discussion of "update_wsjtx_log.py" onto another email list. Other WSJT-related software, including derivative programs (JTDX, MSHV, JS8Call, ...) as well as cooperative programs (JTAlert, ...) have their own lists, and these distinctions serve all users

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

One more thing: I neglected to mention in the release notes that this app adds a custom tag to the ADIF logs it modifies, so that one can tell which logs have been post-processed: It adds the custom ADIF 3.1 tag: "" with the source used to fill in the data, e.g. "qrz.com" or "callook.com". So

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

I think people operating in contests should be intelligent enough to know what to do. And QRZ isn't the only data source. If the other party didn't send the grid, why would it be in ALL.TXT? WSJT-X doesn't do any looking up -- otherwise what is my tool for? If you don't find the tool useful,

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Sam, Yes, and it is for the end user to decide if they want to use that backend. 73, -- Dave Slotter, W3DJS On Mon, Mar 8, 2021 at 12:44 PM Sam W2JDB wrote: > Dave, > > You do realize that callbook.info is strictly a USA only call sign lookup. > > 73, > > Sam

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Dave, You do realize that callbook.info is strictly a USA only call sign lookup. 73,  Sam W2JDB -Original Message- From: Dave Slotter, W3DJS To: ham...@groups.io; ha...@groups.io; linux...@groups.io Group Moderators ; ws...@groups.io; WSJT software development Sent: Mon, Mar 8, 2021

Re: [wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Dave Remember to remind people not to use it in contests - if there is a mismatch between what is sent over the air and what is recorded in QRZ - points will be lost. If the grid is blank it highlights the user need to take action - usually checking all.txt and not grabbing qrz.com

[wsjt-devel] ANNOUNCEMENT: update_wsjtx_log.py version 1.1.1 released

Fellow hams and users of WSJT-X: I am pleased to announce the creation and immediate availability of version 1.1.1 of a Python application to address some of the deficiencies of WSJT-X not providing a method to automatically look up callsigns and missing grid squares and fill them in. Changes: *