Skip to content

Mission control frontend

nikalc edited this page May 26, 2021 · 5 revisions

Summary

The frontend website is the centralised part of the project. Whether you want to steer the SmartRover in a particular direction, activate obstacle avoidance or assign a mission task. Either which this is the platform in which all execution starts. In Mission Control the user will be able to assign a mission task and receive accurate, continuous and reliable mission status updates in real time in order to evaluate the progress. A key feature that signifies Milestone 4.

Highlights

  • Assign the SmartRover with mission tasks
  • Construct specialised mission tasks for the SmartRover to complete remotely
  • Receive continuous and relevant updates related to mission task
  • Have access to Livestream where the user can get visual feedback from the SmartRovers camera lens and take snapshots of it's surroundings.

Description

A mission is important to say the least. It is a task expected to be completed. So it comes with set of responsibilities and with some faith. Therefor having the right prerequisites can give you a useful leg up. A helping hand. That is to say that having certain functionalities can not only elevate the user experience but help you in completing the mission task at hand. For instance, having the possibility to view the martian environment through the lens of the SmartRover can help you navigate and foresee. Make the unpredictable environment of Mars slightly more predictable. Not only will the integrated Livestream and camera aid you in getting visual feedback off the environment but it will enable you to take snapshots of the environment. Something that is totally up to you. A camera is a camera. No restrictions.

When undergoing a mission it can come quite in handy to get continuous updates of the mission task in order to evaluate its progress and make accurate estimates with regards to the information being displayed. This information can include distance, obstacles and other relevant variables that can interfere with the mission completion. Also, the mission task is not set in stone. It can be edited and updated by the user so that the user can tailor and customise the experience to a larger degree. Granting them more control.

Functional requirements:

  • The user shall be able to build mission steps and send as a packet
  • The user shall be able to get meaningful feedback regarding the mission result
  • The user shall be able to get visual feedback from the rover and take screen shots

Non-functional requirements:

  • Users shall be able to execute their missions and get mission status update
  • Users shall be able to edit/update mission steps easily