Thanks Bill and Steve, I noticed the change in format of ALL_WSPR.TXT and so I now know to use the field count of existing ALL_WSPR.TXT files to trigger a WSJT-x upgrade. However this seems a very awkward way to determine the version of wsprd, so if there is another wsprd upgrade, could you add a '-V' command line flag to help us out with this?
You will find all of those fields stored in extended spot record tables contributed by 25 'top spotter' sites to the database at http://wsprdaemon.org/. Also there is a very high performance, SQL queriable clone of the wsprn.org spots database. Both http://wsprd.vk7jj.com/ and the WSPRWatch iPhone app now utilize our clone a deliver results in 2 seconds or less. Thanks for the explanation of the ALL_WSPR.TXT fields and your work on wsprd and I will soon have 4 of the 5 top spotters worldwide running 2.2-1. Rob On Tue, Jun 9, 2020 at 10:20 AM Steven Franke via wsjt-devel < [email protected]> wrote: > On Jun 9, 2020, at 12:09 PM, Bill Somerville <[email protected]> > wrote: > > On 09/06/2020 16:51, Rob Robinett wrote: > > I want sites running my 'wsprdaemon' to benefit from the improved decoding > performance of the V2.2 wsprd decoder, but I am not sure how to determine > which version of wsprd is installed. > > wsprd 2.1.x added '-o ...' to the help printout, but there is no such > difference between 2.1.x and 2.2.x. > > Other than looking at the size of /usr/bin/wsprd, is there a more reliable > way to determine which version is installed? > > Thanks, > > Rob > > -- > Rob Robinett > AI6VN > > Hi Rob, > > there's not much to help you. The ALL_WSPR.TXT file has extra columns > since WSJT-X v2.2.0. > > 73 > Bill > G4WJS. > > Hi Rob and all, > > FYI, here is a summary of the current format of the ALL_WSPR.TXT file as > of v2.2.0 (the table should be viewed with a fixed-width font): > > Sample lines from the ALL_WSPR.TXT file: > > yymmdd hhmm snr dt frequency 22 character message 1 2 3 4 > 5 6 7 8 9 > > ————————————————————————————————————————————————------------------------------------------------- > 180909 1630 -21 0.11 14.0971248 W6IPA CM97 20 0 0.29 2 1 > 0 0 9 1 433 > 180909 1630 -10 0.02 14.0971298 PA0MLC JO31 37 0 0.59 1 1 > 0 0 5 1 571 > 180909 1630 -15 1.39 14.0971346 AA7NM CN86 37 -4 0.47 2 1 > 0 0 5 1 522 > 180909 1630 -9 0.24 14.0971593 LA3JJ JO59 37 0 0.26 3 1 > -16 0 15 406 -78 > 180909 1630 -3 0.19 14.0971755 G0CCL JO02 37 0 0.65 1 1 > 0 0 2 1 602 > 180909 1630 -28 0.11 14.0971990 ON4LUK JO11 23 0 0.19 1 1 > 0 0 29 421 -89 > > Field descriptions: > > 1. drift in Hz over the duration of the WSPR message > 2. sync value [0,1.0] > 3. decoding pass {1,2,3} > 4. block size, in symbols, used for symbol detection, {1,2,3} > 5. dt jitter in samples [-64,64] (multiples of 8 samples) > 6. 0 if the decode was obtained by the Fano decoder, 1 if obtained by OSD > 7. number of bit errors in the received message > 8. Fano iterations-per-bit [1,max_iterations] > 9. Fano cumulative metric [-999,810] > > Example - consider the 4’th message in the ALL_WSPR.TXT lines given above. > The message “LA3JJ JO59 37” was decoded on the 3rd decoding pass. The sync > value was 0.26, and the decode was obtained based on single-symbol > detection, with a dt jitter of -16 samples. Note that dt offsets are tried > in the order 0, -8, 8, -16, 16, -24, 24, etc. up to maximum offsets of +/- > 64 samples. Thus, in this example we can infer that decodes were attempted > at dt offsets of 0, -8, 8 samples before a successful decode was finally > obtained at an offset of -16 samples. Finally, fields 6 through 9 tell us > that the decode was obtained from the Fano decoder, there were 15 hard bit > errors (i.e. sign errors in the soft bit metrics), the Fano decoder > required 406 iterations per bit, and the cumulative Fano metric was -78. > > I hope that this information will be useful to WSPR enthusiasts. > > 73, Steve k9an > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Rob Robinett AI6VN [email protected] mobile: +1 650 218 8896
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
