Dave --
All understood. Rest assured, we have already spent plenty of time
thinking about -- and testing -- the sort of complications you describe.
No doubt we will still have some surprises. Some will be ones we have
foreseen, others probably not. That's precisely why we are doing more
testing!
-- 73, Joe, K1JT
On 3/5/2018 3:33 PM, David Fisher wrote:
Jim has made the point I was heading towards. Even when 1.9 is released
publically, there will be plenty of users of older versions and some
will jump into fray. In a test, it’s not very likely there will be much
QRM. In the real world, when a rare DX is at stake, I expect it could
be quite a mess. Some will be transmitting on the DX frequency, some
will be transmitting into the 300-900 Hz space, etc. I’m simply trying
to stimulate a little brainstorming about how this could go wrong and
what could be done to mitigate it. We’ve already seen lots of examples
of people running old versions of the code, running RCs past their
expiration date, etc.
I’m not a purveyor of gloom and doom, far from it. But it’s difficult
to roll out a dramatically different version of the program once so many
are running an older incompatible version. And, even if they are
running 1.9, how will they get the experience to use the new mode
effectively?
Dave / NX6D
------------------------------------------------------------------------
*From:* James Shaver <n2...@windstream.net>
*Sent:* Monday, March 5, 2018 11:09:37 AM
*To:* 'WSJT software development'
*Subject:* Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7
It also might not be a bad thing if some well-meaning but otherwise
uninformed ops running 1.8 wander into the "pileup" as it may help simulate
real-world conditions where this may also happen with more frequency.
Though they may not decode the "fox" I've seen any number of times where
people will start calling a "DX" even though they can't hear them so I'd
expect this will happen during the public test as word spreads. It'll help
add legitimacy to real-world QRM.
Just my 2 cents, feel free to keep the change :)
Jim S.
N2ADV
-----Original Message-----
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Monday, March 5, 2018 2:02 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7
On 3/4/2018 8:12 PM, David Fisher NX6D wrote:
I’m curious to know what will happen when someone wanders into these
tests, without RC2, and tries to send one of the messages not used in
these abbreviated sequences. Will those callers be ignored?
Only Fox sends a new type of message -- that is, one not supported in WSJT-X
v1.8.0.
I hope it's clear in the FT8 DXpedition Mode User Guide
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fphysics.princeton.edu%2Fpulsar%2Fk1jt%2FFT8_DXpedition_Mode.pdf&data=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636558738863273348&sdata=Fv8YsdwGWJtpSR6%2FWEfmU20p4YKCftMbHMR1DPSlWWk%3D&reserved=0
... that Fox will respond only to
1. Initial calls like line 2 in the User Guide's example sequence (top of
page 2). These messages must be received above 1000 Hz; and
2. Messages like lines 4 and 6, from stations to whom Fox has already sent a
signal report. These must be received between 300 and 900 Hz.
-- 73, Joe, K1JT
----------------------------------------------------------------------------
--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org!
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636558738863273348&sdata=xGQwTM3BgptdcOi46oTsiKW94MZx7uTgvEU0CQhngRo%3D&reserved=0
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636558738863273348&sdata=IpyYm%2Fvh7eTF9ROKzkA4vD%2Fap0Q8FKMMfNoc8EpC8aI%3D&reserved=0
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636558738863273348&sdata=xGQwTM3BgptdcOi46oTsiKW94MZx7uTgvEU0CQhngRo%3D&reserved=0
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636558738863273348&sdata=IpyYm%2Fvh7eTF9ROKzkA4vD%2Fap0Q8FKMMfNoc8EpC8aI%3D&reserved=0
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
