Forum Replies Created
-
AuthorPosts
-
Andrew M0YMA
KeymasterPlease see the news article posted on 6th March
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 400You 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 10 months, 3 weeks ago by
Andrew M0YMA.
Andrew M0YMA
KeymasterHi 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
KeymasterOops… sorry. Fixed ๐
Andrew M0YMA
KeymasterThanks 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
Keymaster@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
KeymasterI’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
KeymasterQuite simply, the quality of logs *after being checked by National Coordinators* is bad enough…
Andrew M0YMA
KeymasterHi Augusto
Logsearch simply processes the data it has… if there are activations showing the wrong year, that suggests that the QSO date is incorrect…
Perhaps HB9CBR can look at his “2010” activations and tell us when they actually were?
Andrew M0YMA
KeymasterPlease advise the required changes… it’s easier than deleting, especially when Hunters have already claimed the point
Andrew M0YMA
KeymasterPlease confirm: ZL7E was the StationCall, and VK5PAS the Operator ?
Andrew M0YMA
KeymasterThanks Gerald…
Sometimes things are so obvious, you see right through them -especially when it was you writing it in the first place.
This has now been fixed ๐
Andrew M0YMA
KeymasterHi Rahul
For reasons I don’t understand, the profile checks were not passing for you…
So I’ve fixed it for you…
Andrew M0YMA
KeymasterWhat do you find “convoluted”?
How would you suggest we improve it?
Andrew M0YMA
KeymasterVolunteers to do (rather than just whinge) are welcome…
Andrew M0YMA
KeymasterThe clue was in your first post:
CALL:6>S58N should be
CALL:4>S58N
`-
This reply was modified 1 year, 8 months ago by
Andrew M0YMA.
-
This reply was modified 10 months, 3 weeks ago by
-
AuthorPosts