Forum Replies Created
-
Posts
-
Yes it is required.
The Rules for the award are quite clear… if neither log has a SIG/SIG_INFO tag, then the P2P will not be confirmed.
If one log has them, then it will (probably) be confirmed. Florian was fortunate in that his P2P contacts had CORRECTLY submitted their log.
We have over 12 million QSOs in the database (2019-04-05 05:30utc = 12,227,942)… we do not have the processing power to regularly run 12 million database queries looking for a match.
No progress…
The usual situation… I’ve not had much spare time, and no-one else has come forward.
However, I’ve added it to the Issue Tracker as #00019
https://gitlab.com/WWFF/wwff-logsearch/issues/19The “interactive” (search) pages use whatever callsigns you have specified in your profile
The “batch” generated pages (eg top operators) match solely against the operator fields.
So if you operate using a special call, or other callsign, it is imperative that you specify your home-call as the operator.
(see the FAQ at https://wwff.co/rules-faq/confirming-and-sending-log/)Looking at the code, I see no reason why you’re getting bad requests 🙁
I’m still looking into this…
Point 1: Do you mean like this: https://wwff.co/logsearch/latest-logs/
Point 2: a good suggestion. You can track this one here: https://gitlab.com/WWFF/wwff-logsearch/issues/17
The reason why SMFF awards were pulled from Logsearch was two-fold:
1. Two competing programs
2. Logs being uploaded multiply, where a reference was in a bigger reference, logs were loaded for both (or in some cases several times!)There is also the question of program integrity – the top activators (according to logs uploaded) do not appear in many non-SMFF logs 🙁
The source of the problem seems to be the narrow mind of a man who does not allow the possibility of working at a club station under a special sign, and applies any regulations nowhere saved.
Assuming that “narrow mind” belongs to me, you are mistaken.
The reason that Club calls are not currently recognized is that I have not found a way of adding the necessary flags into the WordPress database in such a way that they can be queried correctly.
The source code is Open (see https://gitlab.com/WWFF/wwff-logsearch) and if anyone has a suggestion, they are welcome to propose the appropriate changes.
At some point, either when I (or someone else) has a solution, the Club table entries will be reinstated – if I had no plans to do so, I’d have deleted the columns by now! Meanwhile, if you put both the club call and the operator into the log-file the data is there for future aggregation.
This error means that you have already uploaded that log, or a log with the same name
Please be reminded of the (recommended) naming convention for logs:
Callsign_@_reference_date
eg
M0MYMA-P @ GFF-0123 2018-12-11.adi
