Forum Replies Created
-
Posts
-
The use of suffixes is governed by your licence – in many countries, the use of use of such suffixes is optional.
However, IMHO, it is good practice to sign /P or /M where appropriate, as this (a) highlights you may be using limited equipment (b) highlights you are giving away some references
After investigations…
Your interactive search shows the bigger number, as it includes BOTH calls
Top Operators matches on the HunterHomeCall – which is obviously different for the two calls.
I’ve updated your Hunts and this should now show the correct number… at least, after tonight’s run!
I’ve also added the mapping of SE5B->SM5CBN during upload, so future Hunts should be correctly allocated
Ah… Ummm… Ooops…
A change I made in August 2023 will have broken VEFF for anyone trying to claim less than 100 references 😮
I’ll try ad fix that!
Sorry…
Regarding deleted areas… there are three reasons why a reference is deleted:
1. It shouldn’t have been a reference in the first place
2. It has been replaced by another reference
3. It was a valid reference, but has ceased to be validQSOs in (1) should be invalid
QSOs in (2) should be moved to the replacement reference
QSOs in (3) are a problem, I agree.If you have included your “home call” as the Operator when activating using your special call, they should all show as SM5CBN in Top Operators
I’ll have a look at your data when I have a moment…
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)
etcNo… this has not been actioned
Issue #97 applies
https://gitlab.com/WWFF/wwff-logsearch/-/issues/97Note: 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.Fixed… the overnight batch job had stopped running for some reason.
You’re now fully attributed 🙂
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?
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
Please 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…
