pathfinder-for-autonomous-navigation/FlightSoftware

GSW Close Out

Closed this issue · 1 comments

knk38 commented
  • Currently we have all of the layouts set up but they need to be completely filled out with bounds
  • Widgets need to be set up as well
  • Since we added new stuff to GSW lets update that on the docs

Layouts:

  • Meeting must be made to decide what "Green" bounds are for important telem fields (particularly ones with widgets)
  • We also should, as an additional feature, come up with a formula for the mission status as a whole (Ex. Whether everything important is "Green") Which would allow us to have a front page to MCT/GSW with a Green or Red indicator light to indicated if each satellite is nominal. (This is not as critical as other widgets but would make our live's more convenient in end)
  • After meeting I can update the layout json using the OpenMCT editor/GUI

Files needed to be changed:

  1. spreadsheet to organize bounds
  2. Layout .json file using MCT GUI

Documentation:

  • All the new procedures for ground software should be added to the documentation.
    These Should include both:
  1. user-end procedures
  • How to import layout json files
  • how to login to MCT from browser
  • Until browser security/SSL/HSTS issues are fixed, add procedures to complete a bypass
  1. Server-end procedures
  • How to start up each piece of the server stack
  • How to diagnose server issues on scaleway end
  • Once the scripts are made to ease up server procedures, update this as well.

Additionally the following should be added in case of another Scaleway payment failure:

  1. Documentation and/or shell script for Scaleway instance setup
  • Documentation for how to purchase and set up scaleway on scaleway website
  • Documentation for setting up A linux user to make enviorment ready to install FSW repo
  • Documentation for adding ssh key to masterchief github for cloning repo
  • Shell Script for a complete instillation of the Flight Software repo and it's requirements on Ubuntu 20.04 (Also would be useful so we don't have to remember all the random system package requirements need to install everytime we install FSW on a new computer (Ex. libncurses5-dev lol))
    Also: (If it is found useful, someone more knowledgeable with themac side could make a zshell script for mac setup)

Files needed to be changed:

  1. GSW ReadMe's
  2. Relevent Pprocs/Documentation