[Andrew M0YMA]

Hi Grant

The P2P score reflects unique reference combinations… so two confirmed contacts between the same references only counts as one point.

eg:
you in VKFF-1660 and VKFF-0063 (two contacts, one point)
you in VKFF-1663 and VKFF-0139 (two contacts, one point)
etc

[Andrew M0YMA]

No… this has not been actioned

Issue #97 applies
https://gitlab.com/WWFF/wwff-logsearch/-/issues/97

[Andrew M0YMA]

Note: there is no need to list /P variations as associated call-signs…

If a STATION_CALLSIGN is callsign/P the OPERATOR is automatically populated as callsign

—
The requested change is noted, and will be actioned by the Team in due course.

[Andrew M0YMA]

Fixed… the overnight batch job had stopped running for some reason.

You’re now fully attributed 🙂

[Andrew M0YMA]

It’s a good question… on a very quick first glance, the data appears correct.

QRX 🙂

[Andrew M0YMA]

Hi Paul

It’s not so much the maximum number of QSOs but on the size of the file – from memory, that is 2GB

However, depending on how complex the QSOs are, and whatever else if going on on the server, upload and processing may exceed server time-limits – when you get a 500 or 503 error

We have a lot of logs with 10,000+ QSOs, so that sort of number shouldn’t be a problem

How big are you thinking?

[Andrew M0YMA]

Hi Paul

Could you confirm under which callsigns the activations were undertaken?

If using a special-call, did you specify VK5PAS as the Operator?

Let me have details, and I’ll check the data

[Andrew M0YMA]

Hi Rob

On each page of Logsearch, you can CTRL-P

• This reply was modified 3 months ago by Andrew M0YMA.

[Andrew M0YMA]

Please see the news article posted on 6th March

Changes to WWFF Awards

Effective from that date, WWFF-H hunter awards are issued:

* Entry level at 10 references worked or points earned (unchanged)
* Between 44 and 444, in steps of 44 (unchanged)
* Between 444 and 4444, in steps of 100 (unchanged)
* Between 4,444 and 8,444, in steps of 200
* Above 8,444, in steps of 400

You have the 14,444 award – your next award will be 14,844

The roll-over text on the WWFF-H award needs correcting…

• This reply was modified 4 months, 1 week ago by Andrew M0YMA.

[Andrew M0YMA]

Hi Peter

My guess is that the server was busy doing the “overnight” (UK-time) magic…

The simple solution is to upload the remaining QSOs using a slightly renamed log-file

[Andrew M0YMA]

Oops… sorry. Fixed 🙂

[Andrew M0YMA]

Thanks for posting… it seems there is a concerted effort to draw this to our attention, given the large number of emails, messages etc received.

I’ve checked, and the references listed were created in late 2014… so it has taken people nearly 10 years to spot.

However, given that WWFF operates in accordance with ITU principles, these references should not have been approved, and as such have been removed (retrospectively)

[Andrew M0YMA]

@Paul – the upload checks catch obvious errors in the ADIF, but cannot trap (eg) wrong date(s), wrong activated reference(s), wrong station/operator callsign(s)…

I fully accept that a Log Manager ius unlikely to detect the various wrong bands, wrong hunter references, wrong hunter callsigns…

Fundamentally, activators need to be more careful in their logging!

[Andrew M0YMA]

I’m sorry you feel that way, KI6BTY…

On the other hand, a quick look in the Log Corrections sub-forum will show the number of errors that get uploaded after being checked by the Log Manager.

Various improvements are on the drawing board, but are mostly constrained by the simple fact that I don’t have the spare time, and other volunteers are few (while acknowledging the few that are assisting!).

[Andrew M0YMA]

Quite simply, the quality of logs *after being checked by National Coordinators* is bad enough…

[Author]

Posts