Re: LotW Sent Stuck on "U"
+ AA6YQ comments below After reading and running a few queries, I have a question. Since the beginning of this year I have a total 468 QSO in DXKeeper log. I have received 279 confirmations, and I have 189 records remaining with "U" status in the LOTW Sent drop=down list. Is this the desired behavior? + No. 'U'' means "uploaded to LotW, but not yet reported as accepted by LoTW". + I suggest that you follow the instructions in /g/DXLab/message/227212 73, Dave, AA6YQ
|
Re: LotW Sent Stuck on "U"
After reading and running a few queries, I have a question. Since the beginning of this year I have a total 468 QSO in DXKeeper log. I have received 279 confirmations, and I have 189 records remaining with "U" status in the LOTW Sent drop=down list. Is this the desired behavior? (279 plus 189 matches the total number of QSOs). The QSOs with Status U have all been uploaded to LOTW and I can see them in LOTW online.?
?
Will the status remain as U or should it be Y?
?
73,
Bernd - KB7AK
|
Open Source software development has many virtues:
1. it enables contributions - defect repairs and enhancements -? from multiple developers
2. it enables anyone to examine the source code to see how it works, identify and report defects, and suggest improvements
3. it lowers the acquisition cost to users
The expectation is that modifications to an open source project will be contributed to that project, though such contributions may not be accepted. If the modifications are not accepted, they can still be used by the modification's developer(s) and their organization(s), who take responsibility for the modified project's maintenance. These developers have created a "fork" of the project source code, which they will use and maintain. If enough other developers and organizations learn about the fork and begin using it, the project's leaders may rethink their decision to reject the modifications they were offered and incorporate them into the project, effectively absorbing the fork. The more active forks, the more time the project's leaders must spend monitoring those forks (via their offered contributions) rather than moving the project forward.
In contrast, if another set of developers simply grab an open source project's source code and without discussion begin making significant changes to create their own competitive project, then even if these changes are conveyed to the original project (as is often required by the license under which the source code is made open source), the fork is considered "hostile".?
My understanding is that the developer of JS8 discussed his idea for an "interactive FT8" application with the WSJT-X development team leads, and it was agreed that a separate project made sense; thus JS8 is not a hostile fork. As Joe W4TV pointed out, the various development versions of WSJT-X aren't hostile forks either.
Imagine working flat-out in your spare time for years as part of a team striving to create a new application for the amateur radio community only to discover that someone has taken your team's source code and used it to create a competitive project. Would you still be motivated to continue contributing to open source projects? Me neither. That's why hostile forks are bad for open source software development, and should be discouraged, in my opinion.
? ? ? ?73,
? ? ? ? ? ? ?Dave, AA6YQ
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
Thanks Dave, understood. 73, N0AN
toggle quoted message
Show quoted text
+ AA6YQ comments below
So, any new spot that comes in within 15 minutes of the current spot will not show up on the screen, but right-clicking on the spot and showing sports near XXX should show other stations that have spotted the call.? Depending on whether you spot within 15 minutes or later, you should either see your spot on the screen or in the showing spots near XXX in the popup window.
+ You can't reliably determine whether "your spot" was received via the Source field of an Entry in the Spot Database Display, which is t he callsign of the station that most recently spotted an Entry's station; at the rate spots arrive, another spotter may have gotten there first.
+ If the "Record individual spot information" option is enabled, then you can right-click the Spot Database Entry and select "Display spots of ..." command from the popup window; SpotCollector will then populate a window with all of the spots that "contributed" to the Entry - which should include yours.
+ Otherwise, before issuing an outgoing spot, temporarily uncheck the "Hide" and "Ann/Talk" options for one of your spot sources on the Configuration window's "Spot Sources" tab; SpotCollector will display a "Spot Source" window showing every spot received from that source. Then issue your outgoing spot, which should shortly appear in the spot source window.
? ? ?73,
? ? ? ? ? ?Dave, AA6YQ
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
+ AA6YQ comments below
So, any new spot that comes in within 15 minutes of the current spot will not show up on the screen, but right-clicking on the spot and showing sports near XXX should show other stations that have spotted the call. ?Depending on whether you spot within 15 minutes or later, you should either see your spot on the screen or in the showing spots near XXX in the popup window.
+ You can't reliably determine whether "your spot" was received via the Source field of an Entry in the Spot Database Display, which is t he callsign of the station that most recently spotted an Entry's station; at the rate spots arrive, another spotter may have gotten there first.
+ If the "Record individual spot information" option is enabled, then you can right-click the Spot Database Entry and select "Display spots of ..." command from the popup window; SpotCollector will then populate a window with all of the spots that "contributed" to the Entry - which should include yours.
+ Otherwise, before issuing an outgoing spot, temporarily uncheck the "Hide" and "Ann/Talk" options for one of your spot sources on the Configuration window's "Spot Sources" tab; SpotCollector will display a "Spot Source" window showing every spot received from that source. Then issue your outgoing spot, which should shortly appear in the spot source window.
? ? ?73,
? ? ? ? ? ?Dave, AA6YQ
|
Re: Open Source Sorftware is in Crisis
+ AA6YQ comments belo-w
I guess I am confused.?
?
How does something that someone?else is working on, cost them time and energy?
+ At minimum,
1. protocol compatibility
2. issues raised by users not understanding which "variant" they are running
3. questions from 3rd party developers like me
? ? ? ?73,
? ? ? ? ? ? ?Dave, AA6YQ
|
Re: Open Source Sorftware is in Crisis
I guess I am confused.?
How does something that someone?else is working on, cost them time and energy?
toggle quoted message
Show quoted text
? When he was leading the WSJT-X development team, now SK Bill G4WJS complained on several occasions that the hostile forks of WSJT-X were costing his team significant time and energy. That's why there's no supported interoperation between DXLab and "hostile forks" of WSJT-X.
Another example: HRD - a commercial product - contains open source code from FLDigi.
?????? 73,
????????????? Dave, AA6YQ
|
Re: Open Source Sorftware is in Crisis
On 2025-01-20 11:34 AM, Earl Needham via groups.io wrote: After this post, I uninstalled WSJT-X "Improved" and went back to WSJT-X. I find that I can hardly operate it! WSJTX Improved (a.k.a wsjtx-devel) is hardly a "hostile fork". The developer of WSJTX Improved is a member of the primary WSJTX development team and wsjtx-devel is his "test bed" for items that may be merged into the main development branch in a future release. 73, ... Joe, W4TV On 2025-01-20 11:34 AM, Earl Needham via groups.io wrote: After this post, I uninstalled WSJT-X "Improved" and went back to WSJT-X. I find that I can hardly operate it! I have some learning to do -- but perhaps I've done the right thing. Happy New Year, Dave. Thanks for all your hard work and especially your willingness to answer questions and in general help others. Vy 7 3 Earl / KD5XB DM84 e e Sent with [Proton Mail]() secure email. On Sunday, January 19th, 2025 at 3:28 PM, Dave AA6YQ <aa6yq@...> wrote:
When he was leading the WSJT-X development team, now SK Bill G4WJS complained on several occasions that the hostile forks of WSJT-X were costing his team significant time and energy. That's why there's no supported interoperation between DXLab and "hostile forks" of WSJT-X.
Another example: HRD - a commercial product - contains open source code from FLDigi.
73,
Dave, AA6YQ
|
Re: Open Source Sorftware is in Crisis
Well cool then!? I'll go back.
I guess I should stick to stuff I know -- if I can ever find out what that is...
Thanks, Earl / KD5XB
e e
On Monday, January 20th, 2025 at 9:49 AM, Bruce - K5WBM via groups.io <bruce.mclain@...> wrote:
toggle quoted message
Show quoted text
WSJT-X Improved is not a hostile fork. ?It is written by Uwe DG2YCB who is also on the development team for WSJT-X.
On Jan 20, 2025, at 10:34 AM, Earl Needham via < kd5xb@...> wrote: After this post, I uninstalled WSJT-X "Improved" and went back to WSJT-X.? I find that I can hardly operate it!? I have some learning to do -- but perhaps I've done the right thing.
Happy New Year, Dave.? Thanks for all your hard work and especially your willingness to answer questions and in general help others.
Vy 7 3 Earl / KD5XB DM84
e e
On Sunday, January 19th, 2025 at 3:28 PM, Dave AA6YQ < aa6yq@...> wrote:
?
When he was leading the WSJT-X development team, now SK Bill G4WJS complained on several occasions that the hostile forks of WSJT-X were costing his team significant time and energy. That's why there's no supported interoperation between DXLab and "hostile forks" of WSJT-X.
Another example: HRD - a commercial product - contains open source code from FLDigi.
?????? 73,
????????????? Dave, AA6YQ
|
Re: Open Source Sorftware is in Crisis
WSJT-X Improved is not a hostile fork. ?It is written by Uwe DG2YCB who is also on the development team for WSJT-X.
toggle quoted message
Show quoted text
On Jan 20, 2025, at 10:34 AM, Earl Needham via < kd5xb@...> wrote: After this post, I uninstalled WSJT-X "Improved" and went back to WSJT-X.? I find that I can hardly operate it!? I have some learning to do -- but perhaps I've done the right thing.
Happy New Year, Dave.? Thanks for all your hard work and especially your willingness to answer questions and in general help others.
Vy 7 3 Earl / KD5XB DM84
e e
On Sunday, January 19th, 2025 at 3:28 PM, Dave AA6YQ < aa6yq@...> wrote:
?
When he was leading the WSJT-X development team, now SK Bill G4WJS complained on several occasions that the hostile forks of WSJT-X were costing his team significant time and energy. That's why there's no supported interoperation between DXLab and "hostile forks" of WSJT-X.
Another example: HRD - a commercial product - contains open source code from FLDigi.
?????? 73,
????????????? Dave, AA6YQ
|
Open Source Sorftware is in Crisis
After this post, I uninstalled WSJT-X "Improved" and went back to WSJT-X.? I find that I can hardly operate it!? I have some learning to do -- but perhaps I've done the right thing.
Happy New Year, Dave.? Thanks for all your hard work and especially your willingness to answer questions and in general help others.
Vy 7 3 Earl / KD5XB DM84
e e
On Sunday, January 19th, 2025 at 3:28 PM, Dave AA6YQ <aa6yq@...> wrote:
toggle quoted message
Show quoted text
https://spectrum.ieee.org/open-source-crisis ? When he was leading the WSJT-X development team, now SK Bill G4WJS complained on several occasions that the hostile forks of WSJT-X were costing his team significant time and energy. That's why there's no supported interoperation between DXLab and "hostile forks" of WSJT-X.
Another example: HRD - a commercial product - contains open source code from FLDigi.
?????? 73,
????????????? Dave, AA6YQ
|
Re: Open Source Sorftware is in Crisis
thanks.
73 de Salvatore (I4FYV)
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
Thanks?Tom, I'll check this.?
toggle quoted message
Show quoted text
So, any new spot that comes in within 15 minutes of the current spot will not show up on the screen, but right-clicking on the spot and showing sports near XXX should show other stations that have spotted the call.? Depending on whether you spot within 15 minutes or later, you should either see your spot on the screen or in the showing spots near XXX in the popup window.
Tom-KQ5S On Jan 20, 2025, at 08:15, Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote:
In SpotCollectors configuration, you might see what you have the Maximum separation time set to in the Combination Criteria pane.
Tom-KQ5S On Jan 20, 2025, at 05:51, Hasan Schiers N0AN via ??<hbasri.schiers6= [email protected]> wrote:
Tom, I'll have to wait until a spot from someone else shows up in SC, and I'll try that. Tnx, 73, N0AN If you right-click on the spot for TX7N and then choose "Display spots of TX7N near XXXX" does your call show up there?
Tom-KQ5S On Jan 20, 2025, at 05:26, Hasan Schiers N0AN via ??<hbasri.schiers6= [email protected]> wrote:
I may have found the answer to my own question. It may be because every time I have spotted TX7N it has already been spotted (but I sure don't see it in my list), and therefore SC doesn't display recent spots of the same station on this same mode/freq etc.
As a test, I spotted TX7N on 10m but only locally, and it showed up. I spotted it again and it didn't show up (because of recency).
I then test spotted TX7N on 12m, but to the Cluster (with appropriate apologies and noting it was a test and ignore this), and it displayed.
So it appears a recent spot that did not display (from someone else on the same band/mode/time) was preventing my spot from showing.
If I have misconstrued?what I am seeing, please straighten me out.
73, N0AN On Mon, Jan 20, 2025 at 5:16?AM Hasan Schiers N0AN via ??<hbasri.schiers6= [email protected]> wrote: I see the update in the N6WS connect window when I spot TX7N, but I never see my spot appear in the SC table.?
If other people spot TX7N it appears in the list. ...and yes, I have Big CTY Overrides and TX7N is in it.
What do I? have misconfigured?
--?
Tom-KQ5S
--?
Tom-KQ5S
--
Tom-KQ5S
|
Re: Open Source Sorftware is in Crisis
A "hostile fork" is any branch that fails to follow the the limitations of the original developer and which is not merged back into the primary development map.
<>
In other words, any branch of a software development that stands in opposition to the original/authorized line of development.
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-01-20 5:31 AM, Salvatore Besso via groups.io wrote: hello, Dave, what do you mean with "hostile forks"? Just for sake of curiosity. 73 de Salvatore (I4FYV)
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
So, any new spot that comes in within 15 minutes of the current spot will not show up on the screen, but right-clicking on the spot and showing sports near XXX should show other stations that have spotted the call. ?Depending on whether you spot within 15 minutes or later, you should either see your spot on the screen or in the showing spots near XXX in the popup window.
toggle quoted message
Show quoted text
On Jan 20, 2025, at 08:15, Hasan Schiers N0AN via groups.io <hbasri.schiers6@...> wrote:
In SpotCollectors configuration, you might see what you have the Maximum separation time set to in the Combination Criteria pane.
Tom-KQ5S On Jan 20, 2025, at 05:51, Hasan Schiers N0AN via ??<hbasri.schiers6= [email protected]> wrote:
Tom, I'll have to wait until a spot from someone else shows up in SC, and I'll try that. Tnx, 73, N0AN If you right-click on the spot for TX7N and then choose "Display spots of TX7N near XXXX" does your call show up there?
Tom-KQ5S On Jan 20, 2025, at 05:26, Hasan Schiers N0AN via ??<hbasri.schiers6= [email protected]> wrote:
I may have found the answer to my own question. It may be because every time I have spotted TX7N it has already been spotted (but I sure don't see it in my list), and therefore SC doesn't display recent spots of the same station on this same mode/freq etc.
As a test, I spotted TX7N on 10m but only locally, and it showed up. I spotted it again and it didn't show up (because of recency).
I then test spotted TX7N on 12m, but to the Cluster (with appropriate apologies and noting it was a test and ignore this), and it displayed.
So it appears a recent spot that did not display (from someone else on the same band/mode/time) was preventing my spot from showing.
If I have misconstrued?what I am seeing, please straighten me out.
73, N0AN On Mon, Jan 20, 2025 at 5:16?AM Hasan Schiers N0AN via ??<hbasri.schiers6= [email protected]> wrote: I see the update in the N6WS connect window when I spot TX7N, but I never see my spot appear in the SC table.?
If other people spot TX7N it appears in the list. ...and yes, I have Big CTY Overrides and TX7N is in it.
What do I? have misconfigured?
--?
Tom-KQ5S
--?
Tom-KQ5S
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
toggle quoted message
Show quoted text
In SpotCollectors configuration, you might see what you have the Maximum separation time set to in the Combination Criteria pane.
Tom-KQ5S On Jan 20, 2025, at 05:51, Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote:
Tom, I'll have to wait until a spot from someone else shows up in SC, and I'll try that. Tnx, 73, N0AN If you right-click on the spot for TX7N and then choose "Display spots of TX7N near XXXX" does your call show up there?
Tom-KQ5S On Jan 20, 2025, at 05:26, Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote:
I may have found the answer to my own question. It may be because every time I have spotted TX7N it has already been spotted (but I sure don't see it in my list), and therefore SC doesn't display recent spots of the same station on this same mode/freq etc.
As a test, I spotted TX7N on 10m but only locally, and it showed up. I spotted it again and it didn't show up (because of recency).
I then test spotted TX7N on 12m, but to the Cluster (with appropriate apologies and noting it was a test and ignore this), and it displayed.
So it appears a recent spot that did not display (from someone else on the same band/mode/time) was preventing my spot from showing.
If I have misconstrued?what I am seeing, please straighten me out.
73, N0AN On Mon, Jan 20, 2025 at 5:16?AM Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote: I see the update in the N6WS connect window when I spot TX7N, but I never see my spot appear in the SC table.?
If other people spot TX7N it appears in the list. ...and yes, I have Big CTY Overrides and TX7N is in it.
What do I? have misconfigured?
--
Tom-KQ5S
--
Tom-KQ5S
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
In SpotCollectors configuration, you might see what you have the Maximum separation time set to in the Combination Criteria pane.
toggle quoted message
Show quoted text
On Jan 20, 2025, at 05:51, Hasan Schiers N0AN via groups.io <hbasri.schiers6@...> wrote:
Tom, I'll have to wait until a spot from someone else shows up in SC, and I'll try that. Tnx, 73, N0AN If you right-click on the spot for TX7N and then choose "Display spots of TX7N near XXXX" does your call show up there?
Tom-KQ5S On Jan 20, 2025, at 05:26, Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote:
I may have found the answer to my own question. It may be because every time I have spotted TX7N it has already been spotted (but I sure don't see it in my list), and therefore SC doesn't display recent spots of the same station on this same mode/freq etc.
As a test, I spotted TX7N on 10m but only locally, and it showed up. I spotted it again and it didn't show up (because of recency).
I then test spotted TX7N on 12m, but to the Cluster (with appropriate apologies and noting it was a test and ignore this), and it displayed.
So it appears a recent spot that did not display (from someone else on the same band/mode/time) was preventing my spot from showing.
If I have misconstrued?what I am seeing, please straighten me out.
73, N0AN On Mon, Jan 20, 2025 at 5:16?AM Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote: I see the update in the N6WS connect window when I spot TX7N, but I never see my spot appear in the SC table.?
If other people spot TX7N it appears in the list. ...and yes, I have Big CTY Overrides and TX7N is in it.
What do I? have misconfigured?
--
Tom-KQ5S
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
Tom, I'll have to wait until a spot from someone else shows up in SC, and I'll try that. Tnx, 73, N0AN
toggle quoted message
Show quoted text
If you right-click on the spot for TX7N and then choose "Display spots of TX7N near XXXX" does your call show up there?
Tom-KQ5S On Jan 20, 2025, at 05:26, Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote:
I may have found the answer to my own question. It may be because every time I have spotted TX7N it has already been spotted (but I sure don't see it in my list), and therefore SC doesn't display recent spots of the same station on this same mode/freq etc.
As a test, I spotted TX7N on 10m but only locally, and it showed up. I spotted it again and it didn't show up (because of recency).
I then test spotted TX7N on 12m, but to the Cluster (with appropriate apologies and noting it was a test and ignore this), and it displayed.
So it appears a recent spot that did not display (from someone else on the same band/mode/time) was preventing my spot from showing.
If I have misconstrued?what I am seeing, please straighten me out.
73, N0AN On Mon, Jan 20, 2025 at 5:16?AM Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote: I see the update in the N6WS connect window when I spot TX7N, but I never see my spot appear in the SC table.?
If other people spot TX7N it appears in the list. ...and yes, I have Big CTY Overrides and TX7N is in it.
What do I? have misconfigured?
--
Tom-KQ5S
|
Re: Multiple WSJT-X instances to DXKeeprt
On Mon, Jan 20, 2025 at 12:48 AM, Dave AA6YQ wrote:
I'd appreciate it if you'd enable DXKeeper's "Log debugging info" option during your contests with automatic logging enabled for two or more instances of WSJT-X until we catch the misbehavior in the act.
+ As I mentioned here a few years ago, I once had to debug a floating point processor design whose failures manifested as a Fortran program's sin function returning a result greater than 1 every month or so. Such failures may be infrequent, but they are persistent until corrected.
Will do!
?
My first experience in FORTRAN was on an . Its answer to 1 + 1 was always something like 1.99999998.
?
--
John P. WA2FZW
|
Re: TX7N Not Spotting When I Spot Them on SpotCollector
If you right-click on the spot for TX7N and then choose "Display spots of TX7N near XXXX" does your call show up there?
toggle quoted message
Show quoted text
On Jan 20, 2025, at 05:26, Hasan Schiers N0AN via groups.io <hbasri.schiers6@...> wrote:
I may have found the answer to my own question. It may be because every time I have spotted TX7N it has already been spotted (but I sure don't see it in my list), and therefore SC doesn't display recent spots of the same station on this same mode/freq etc.
As a test, I spotted TX7N on 10m but only locally, and it showed up. I spotted it again and it didn't show up (because of recency).
I then test spotted TX7N on 12m, but to the Cluster (with appropriate apologies and noting it was a test and ignore this), and it displayed.
So it appears a recent spot that did not display (from someone else on the same band/mode/time) was preventing my spot from showing.
If I have misconstrued?what I am seeing, please straighten me out.
73, N0AN On Mon, Jan 20, 2025 at 5:16?AM Hasan Schiers N0AN via <hbasri.schiers6= [email protected]> wrote: I see the update in the N6WS connect window when I spot TX7N, but I never see my spot appear in the SC table.?
If other people spot TX7N it appears in the list. ...and yes, I have Big CTY Overrides and TX7N is in it.
What do I? have misconfigured?
|