Multiple Spacecraft GSW

Sub-Issue/Successor Issue to nos3#196, focused on the best solution for allowing effective command of all spacecraft in multiple spacecraft configurations. Here are some of our current ideas:

Run separate instances of COSMOS 4 for each spacecraft, linking one instance to each network. This could be inefficient, and could complicate coordinated command of all spacecraft with one script, however, it would allow better independent control of each spacecraft without as much clutter (which will be covered in other proposed solutions)
Run one instance of COSMOS 4 for all spacecraft, with separate interfaces for each spacecraft, and separate targets for each app on each spacecraft. This would allow one script to control all the spacecraft, while still allowing independent control, and would be more efficient, but would require far more clutter in the interface (2 interfaces and ~15+ targets for each spacecraft added), and thus would be very inefficient for non-scripted control. Also may be difficult to set up properly without confusion between interfaces.
Run one instance of COSMOS 4 which commands all spacecraft. It will command one spacecraft, which will then pass commands along to each subsequent spacecraft through a daisy chain. This would decrease complexity and allow each spacecraft to simply be linked in a chain, however it removes independent control, which may be important for a lot of missions. It also may not work well for distributed, if they are chained in one chain opposed to having the master command all worker spacecraft. We have also attempted this in current versions, though it does not work at present.
Run one instance of COSMOS 4, which controls the master, and then the master has links to all worker spacecraft, and each worker is commanded directly from the master. This could work fairly well for coordinated clusters, but still decreases independence of each satellite.
Run COSMOS 5 and have multiple targets set in it. COSMOS 5 seems to have some amount of multiple spacecraft support out of the box, however it seems it may be a premium feature, thus requiring expensive licenses to use, eliminating it as a real option due to the FOSS nature of this project. Also has large performance impacts, hence our switch back towards COSMOS 4 as our primary GSW in our newest versions.

While these are our main ideas at the moment, a hybrid solution may be best (possibly configure between a master-worker configuration with unified control for clusters, and a more independent control with one instance of COSMOS per spacecraft for other applications). We also appreciate more ideas and brainstorming as we work on this, so that we can come to a good, robust solution that works for DSM and standard applications.

nasa / nos3

Multiple Spacecraft GSW #287