On 07/02/2017 14:16, ANDY DURBIN wrote:
Any code that attempts to derive a QSO start time should also include a reasonableness test on QSO duration.
HI Andy, what could that reasonable test be?For example a pair EME operators with marginal conditions and mid level equipment might expect to have a QSO as long as the time they both have the Moon above the horizon which could be several hours. A pair of operators using MS on a poor day for rocks may spend many hours completing a single QSO for a new square of DXCC entity.
Don't assume everyone is shooting fish in that barrel that is HF JT9 or JT65 operation below the critical frequency. The prime motivation for the JT modes is to allow modestly equipped stations to make QSOs on marginal paths that were not usable before the software was designed and written.
I believe that any attempt to second guess start, end or duration of QSOs is futile. A simple definitive record that can be documented and justified based on first call to a station and manual completion fits that bill and for edge cases when the operator doing the logging realizes the times are incorrect; they can be adjusted before clicking the Ok to log button.
73 Bill G4WJS.
------------------------------------------------------------------------------ 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
