On 04/06/2015 02:28, Steven Franke wrote: > Hi Bill, Hi Steve, >> There was some discussion about picking any random band from the users >> configured bands when the scheduled band is not configured. This is >> potentially tricky because the user specified "tune up" is only >> specified for the 10 standard hopping bands. It would perhaps be better >> to specify the "tune up required" flag at the station list level rather >> than in the band hopping setup. That way it could be used for any band >> change in any mode. > I thought that the discussion was about allowing the hopping algorithm to > choose any band that was listed as an active band, whether or not the band in > question was one of the 10 “coordinated” HF bands. > > For example, when I think about fun things to try, one thing I’d like to do > is to hop 10m/6m/2m during sporadic E seasons. Even though only 10m is a > coordinated band, I should still be able to enter “10 6 2” as active bands in > any/all of day/night/etc. On top of that, if it’s not hard to do it might be > interesting to include the flexibility to define any group of bands as a > “coordinated” group, where the coordination is such that the everyone hops > among the bands in the group together. Again, this might provide some > interesting results during sporadic E season. I have just checked in my changes. The call to the hopping subroutine is now encapsulated in a new class WSPRBandHopping which provides a scheduling dialog and provides band change and Tx period information back to the MainWindow class. It still uses a single function (WSPRBandHopping::next_hop()) to do the dual tasks of picking the next band and when to transmit.
What I have done doesn't fit very well with what you are suggesting but that could change. The settings dialog may not expand well to arbitrary bands as it might get quite large if a user had a lot of bands configured. I see what you mean about including non-scheduled bands and that would solve the issue of specifying tune up for a non-coordinated band, but I still feel that should be part of the main station setup as it appears to be relevant to all modes (or possibly not at all). Give it a try and see if you can map your new code into the new class. Obviously ask here or directly if you need any help understanding any of my code or for help with how it might best be extended. > > Steve k9an 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
