hint65.f90 currently has "MAXMSG=2*MAXCALLS + 2 + MAXRPT" and generates thousands of hypothetical messages of the form:
msg=mycall//' '//call2(i)//' '//grid2(i) msg='CQ '//call2(i)//' '//grid2(i) These aren't as helpful when chasing an EME DXpedition. Is there interest in an increase to "MAXMSG=3*MAXCALLS + 2 + MAXRPT" to add: msg=call2(i)//' '//hiscall//' '//hisgrid(1:4) ? The goal is to make Deep Search effective during decoding of all "ChaserCallsign DXpeditionCallsign DXpeditionGrid OOO" messages, to help each chaser track a DXpedition's responses to other chasers. A few dB more sensitivity for these OOO messages could be useful in evaluating EME station performance or in choosing an operating strategy. This addition is computationally much cheaper than for the general non-EME case, which might require dozens of hypothetical messages (e.g., one for each possible numerical report) per callsign. Matt, KA1R ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
