Mike -

 

All your awarded endorsements are still there, even though the checker isn't showing the QSOs. Compare the WM4B and W3XYZ pages: yours has a bunch of lines in blue on the left side. They're the endorsements that are credited, and they don't go away even if the QSOs aren't in the upload. W3XYZ's page has nothing in blue on the left--everything is on the right side in red except for the three "in process" given the three QSOs uploaded.

 

So the database of endorsements earned by WM4B is still there--it's just that you can't get any more until you change your call (or David finds the software gremlin--whichever comes first)!

 

My guess is that something in that ADIF parser that the checker is using is getting hung up on the callsign, and corrupting the internal file it creates in a way that the data can't then be processed. David should be able to see it by looking at the internal file.

 

Steve

 

From: 070Club@groups.io [mailto:070Club@groups.io] On Behalf Of Stephen Melachrinos
Sent: Tuesday, December 19, 2017 8:07 PM
To: 070Club@groups.io
Subject: Re: [070Club] Awards Checker

Mike -

Well poo!  Guess I’m going to have to go back and take my Novice exam again!

 

Steve/David:  Seems to me that kind of proves my theory about my record being corrupt in the database. 

 

Not sure if 070 Awards Dude has captured my latest endorsements or not… I’ve completed a number of them in the past couple weeks!

 

Thanks for the fine work, Steve.  I’ve spend the day trying to get an Echolink node back on the air as well as a Broadcastify feed; it’s fought me tooth and nail.  Probably I good thing I left this to the grownups!

 

73 and thanks again, Steve.  Hopefully David can promote me back to Extra again!  Gotta love this club.

 

Mike

WM4B

 

From: 070Club@groups.io [mailto:070Club@groups.io] On Behalf Of Stephen Melachrinos
Sent: Tuesday, December 19, 2017 7:50 PM
To: 070Club@groups.io
Subject: Re: [070Club] Awards Checker

 

Okay, you guys may not believe this, but Mike has to change his callsign. Yes, I know it's a vanity, and it's his initials, but apparently certain callsigns are rejected by the checker.

 

First I deleted the extra lines, uploaded as W3XYZ, and the file processed.

 

Then I put lower case back in the tags, uploaded as W3XYZ, and it processed.

 

So I then uploaded the EXACT same file under Mike's call, and it failed. I repeat: The WM4B and W3XYZ lines in the checker now used EXACTLY the same ADIF file. W3XYZ processed correctly and WM4B did not!

 

Steve

W3HF

 

David: Sorry, but at least I helped diagnose the issue. I have copies of all the source files if you want to see them.

-----Original Message-----
From: Stephen Melachrinos <melachri@...>
To: 070Club <070Club@groups.io>
Sent: Tue, Dec 19, 2017 7:37 pm
Subject: Re: [070Club] Awards Checker

Okay, new data point. I modified my ultra-simple ADIF:

 

- added two new lines, <LOG_PGM> and <LOG_VER>. Note that these duplicate the <PROGRAMID> and <PROGRAMVERSION> data.

- changed the tags to all caps, instead of lower case

- uploaded under a fake callsign, W3XYZ

- did NOT change any of the data (QSO) lines

 

Still get the warnings about use of uninitialized values, and again those are in line numbers that don't exist.

 

BUT THE FILE PROCESSED! W3XYZ has credit for three of the 24x7 slots, one continent and one of the 365 days.

 

Now to keep experimenting, to determine which of these three changes made the difference.

 

Steve

W3HF (checked that a couple of times)

 

PS to Mike: You might have to change your callsign to stay in the club!

 

-----Original Message-----
From: Mike Besemer <mwbesemer@...>
To: 070Club <070Club@groups.io>
Sent: Tue, Dec 19, 2017 6:55 pm
Subject: Re: [070Club] Awards Checker

That’s correct, Steve.  I basically repeated the steps you tried last night.  No difference.

 

I don’t think the file is bad, but for some reason the checker dislikes it.

 

Mike

WM4B

 

From: 070Club@groups.io [mailto:070Club@groups.io] On Behalf Of Stephen Melachrinos
Sent: Tuesday, December 19, 2017 6:38 PM
To: 070Club@groups.io
Subject: Re: [070Club] Awards Checker

 

Jim -

 

I saw that too, but those are not fatal errors. Look at the last file I uploaded of my own:

 

http://dwestbrook.net/projects/ham/070-checker/data/W3HF-adif.txt?unique=1513726086

 

I have similar errors there and the file processed successfully. 

 

The crazy thing is that those errors are on line numbers that don't exist in the file (of Mike's) I uploaded. My file had only 26 lines--there wasn't a line 70, or 71 or even line 62.

 

I'll bet that David's checker reads the ADIF file that is uploaded, parses it, and creates its own version for processing. And something in those steps is creating those (non-fatal) errors, perhaps because there's no ADIF version specified. 

 

But you can see that Mike uploaded his version again and it still hasn't processed correctly. Looks like he pulled out the non-PSK31 QSOs (since those notes are missing from the report), but even the PSK31 QSOs alone aren't generating credits against any endorsement.

 

Steve

W3HFD    

-----Original Message-----
From: Jim K5SP <jinnis@...>
To: 070Club <070Club@groups.io>
Sent: Tue, Dec 19, 2017 10:02 am
Subject: Re: [070Club] Awards Checker

Steve, I looked at the rpt for the W3hf Fooling around.  It has some errors in it, has anyone checked the file to resolve these errors?  I made them red and bold.

Jim K5SP

Use of uninitialized value $_ in scalar chomp at ../adif-validator/ADIF/Parser.pm line 70, <FILE> chunk 62.

Use of uninitialized value $comments in pattern match (m//) at ../adif-validator/ADIF/Parser.pm line 71, <FILE> line 62.

KJ4IZW ADIF VALIDATOR

        This reviews a AIDF file for warnings/errors using the v3.0.4 spec: http://www.adif.org/304/ADIF_304.htm

Tue Dec 19 09:45:05 EST 2017

==============

ADIF_VER: 

PROGRAMID: W3HF is fooling around

PROGRAMVERSION: 0.1

CREATED_TIMESTAMP: 20171219 032200

Records: 3

==============

Header info

==============

[WARNING: NO_ADIF_VER  x1] Optional ADIF_VER missing from header.

Use of uninitialized value in anonymous hash ({}) at ../adif-validator/adif-validator.pl line 108.

  == 33% of RECORDS == (values:)

==============

FIELDS USED:

        100% (3)       BAND

        100% (3)       CALL

        100% (3)       MODE

        100% (3)       QSO_DATE

        100% (3)       TIME_ON

==============

excluded: BAD_STRING,BAD_MULTILINE_STRING,BAD_MULTILINE_NEWLINE,NO_TYPE,BAD_NUMBER.SRX,BAD_NUMBER.STX,UNKNOWN_SUB_ENUMERATION.CNTY

 

On 12/19/2017 8:39 AM, Stephen Melachrinos wrote:

Mike -

 

The checker still knows that you've already earned certain endorsements. That's why you have 15 awards listed in blue on the left side of the page.

 

The problem (at least as I see it) is that for some reason it's not processing the new file to apply those QSOs either to awarded endorsements or to new ones. It's not even pulling out the fake name I put in my version of the ADIF file for the source of the ADIF. (Usually it's the name of the log program that created the ADIF. My stripped-down version of your log used the phrase "W3HF is fooling around.") That's further indication (at least to me) that the checker isn't seeing the file properly.

 

The other funny thing is the CM2RSV submitted a log in the middle of all of our actions last night, and his log processed normally.

I just tried one last thing--I created a new text file and copied the contents of my version into it, just in case the file itself got weird. Same result.

 

I continue to be stumped.

 

Steve

W3HF

-----Original Message-----
From: Mike Besemer <mwbesemer@...>
To: 070Club <070Club@groups.io>
Sent: Tue, Dec 19, 2017 8:30 am
Subject: Re: [070Club] Awards Checker

I’m with you, Steve. I tried a bit of the same thing last night after I emailed you the file. I didn’t get as far with it as you did, but agree that something is amiss.

Thinking back, the checker *MAY* have given me an error the first time I tried to upload last night. Perhaps something hiccupped and somehow corrupted my existing record during that initial upload process.

I’m sure David will figure it out. Thanks for having a look.

73,

Mike
WM4B

From: 070Club@groups.io [mailto:070Club@groups.io] On Behalf Of Stephen Melachrinos
Sent: Tuesday, December 19, 2017 12:03 AM
To: 070Club@groups.io
Subject: Re: [070Club] Awards Checker

Jerry -

I stripped down Mike's ADIF to three QSOs, all PSK31, and with only the five ADIF fields required. And it still didn't work. (He should have gotten credit for at least one day in 365 and three hours in 24.x7, but nada.)

Something funny is going on.

Steve
W3HF
-----Original Message-----
From: Jerry N9AVY <n9avy@...>
To: 070Club <070Club@groups.io>
Sent: Mon, Dec 18, 2017 11:51 pm
Subject: Re: [070Club] Awards Checker
A few years ago Matt suggested that when I upload to checker that I separate all non-PSK31 QSOs from the .adif file. With ACLog that is very easy to do and I've been doing that ever since.

I didn't check Mike's logs throughly, I usually just go in and check for sticker related stuff. That's pretty much the xtent of my ventures into files. Had I done anything further into files today it might have been disasterous (today I had a case of "the reverse midas touch". Doing anything technical would have been bad.

Jerry

________________________________________
From: Stephen Melachrinos <melachri@...>
To: 070Club@groups.io
Sent: Monday, December 18, 2017 9:26 PM
Subject: Re: [070Club] Awards Checker

Jerry -

Regardless of whether Mike has more than 1300 QSOs, the checker is showing no credit at all towards any endorsement or award--nothing for WTW, nothing for LONP, nothing towards any endorsement, nothing towards 365 or 24x7. You (and anyone else) can see this by clicking on Mike's callsign. This indicates to me that something is wrong with the current upload.

I tried reading the report that the checker generates, but I can't see anything that would DQ every QSO. There are a lot of non-PSK31 QSOs in the file (a lot of FT8 and some RTTY and SSB), but there are definitely some PSK31. There are some errors that are pervasive (100% of records have a contest field, 99% have a QSLSCB field, 99% have a SPCNUM field, 60% have a QSLRCB field) but I don't know if these are enough to make all the entries unusable. After all, the report also says that 100% of the entries have all the required fields included (Call, Band, Mode, Date, Time_On).

Mike: Have you tried looking at the ADIF yourself (in a text file viewer) to see if it's being properly formed?

Steve
W3HF

-----Original Message-----
From: Jerry N9AVY <n9avy@...>
To: 070Club <070Club@groups.io>
Sent: Mon, Dec 18, 2017 8:46 pm
Subject: Re: [070Club] Awards Checker
Mike:

I see you have about 1300 Q's , did you have more ??? I hope you're uploading your entire log every time you upload.

Otherwise, there may be a glitch some where.


Jerry


________________________________________
From: Mike Besemer <mwbesemer@...>
To: 070Club@groups.io
Sent: Monday, December 18, 2017 6:38 PM
Subject: [070Club] Awards Checker

Anyone else having issues with the Award Checker tonight? I just uploaded my log and it zeroed out all my award totals and shows zero awards in-progress.
The first page shows the correct number of QSOs but the 2nd page shows zero.
Tried numerous uploads and exported the ADIF file several times.
Mike
WM4B
#348

--
Jim,  K5SP #483
Member Services Director

From: 070Club@groups.io [mailto:070Club@groups.io] On Behalf Of Stephen Melachrinos
Sent: Tuesday, December 19, 2017 7:50 PM
To: 070Club@groups.io
Subject: Re: [070Club] Awards Checker

Okay, you guys may not believe this, but Mike has to change his callsign. Yes, I know it's a vanity, and it's his initials, but apparently certain callsigns are rejected by the checker.

Use of uninitialized value $_ in scalar chomp at ../adif-validator/ADIF/Parser.pm line 70, <FILE> chunk 62.

Use of uninitialized value $comments in pattern match (m//) at ../adif-validator/ADIF/Parser.pm line 71, <FILE> line 62.

KJ4IZW ADIF VALIDATOR

        This reviews a AIDF file for warnings/errors using the v3.0.4 spec: http://www.adif.org/304/ADIF_304.htm

Tue Dec 19 09:45:05 EST 2017

==============

ADIF_VER: 

PROGRAMID: W3HF is fooling around

PROGRAMVERSION: 0.1

CREATED_TIMESTAMP: 20171219 032200

Records: 3

==============

Header info

==============

[WARNING: NO_ADIF_VER  x1] Optional ADIF_VER missing from header.

Use of uninitialized value in anonymous hash ({}) at ../adif-validator/adif-validator.pl line 108.

  == 33% of RECORDS == (values:)

==============

FIELDS USED:

        100% (3)       BAND

        100% (3)       CALL

        100% (3)       MODE

        100% (3)       QSO_DATE

        100% (3)       TIME_ON

==============

excluded: BAD_STRING,BAD_MULTILINE_STRING,BAD_MULTILINE_NEWLINE,NO_TYPE,BAD_NUMBER.SRX,BAD_NUMBER.STX,UNKNOWN_SUB_ENUMERATION.CNTY

From: 070Club@groups.io [mailto:070Club@groups.io] On Behalf Of Stephen Melachrinos
Sent: Tuesday, December 19, 2017 7:37 PM
To: 070Club@groups.io
Subject: Re: [070Club] Awards Checker

Okay, new data point. I modified my ultra-simple ADIF: