This project addresses the challenge of Earth to Mars communication. The physical limitations force us to work around the problem of delayed communication. Currently, the NASA mission commands are loaded in advance and the spacecrafts have a high degree of autonomy. For example, the Curiosity Rover was on autopilot for its landing and this was the safest way to do it. However, if you fast-forward into the future, when we will make our first colonisation attempts, the needs will shift and we will seek coordination and more flexibility.
Tandem is a management system for missions in outer space. It builds decision trees and allows for visualisation of the events that occur during the mission. Time is a crucial factor in these missions and influence decisions, so it is also represented in the graph. Furthermore, there is a mission log, that records all the events that happen during a mission and allow for continuous monitoring of missions. Data that can be leveraged for post-mission evaluation. Our app allows for agile coordination of assets, mission guidance, problem reporting, documenting and data visualisation. It takes into account the time delay between Earth and Mars, the data rate and the relay which is transmitting to you and indicates the earliest moment that the field worker can receive instructions. On the receiving end, the person or machine doing the field work, is guided by standard protocols and can exchange events and event sets with mission control, that can represent a protocol or a problem, for example.
There are a multitude of applications for our system. Firstly, in the near future, we can see this system being used to practice missions and to explore the challenges that arise in a delayed communication scenario. The actor can be a person or a machine doing a specific task on Mars. The conclusions of these practices can be used for training of AI-based decision making systems and people alike.In the future, when we will begin terraforming and colonising Mars, the system will serve as a planning and reporting tool to coordinate collective efforts. The decision trees will serve as guidelines for the actors on Mars and mission control can monitor the progress, assign issues and intervene in extraordinary situations. This application will fast-track the learning curve and optimise the processes on the journey of colonising Mars.
The objective was to design an interactive app to explore the communication challenges between Earth and astronauts on Mars. Based on the research conducted we made some assumptions and we showcased some aspects of this challenges.
Showcase:
Assumptions:
The web app represents mission control and it has an overview of all active actors on Mars, the activities that they are doing and the events that happen during these activities. These activities and events are represented as decision trees in the system. When monitoring or intervening in a case the operator has a clear visual time-centric representation of all the decisions in the respective set and he can send additional instructions in the node where he can extend or modify the protocol. Possible actions: assign activity to worker, monitor progress in the active decision trees, send decision tree extension, send absolute decision path, receive media, inspect mission log, see mission metadata, etc.The mobile app is the actor from Mars, who will receive his activities from mission control. This will act as his guide for the mission. In the ideal case, the AI system will have been already trained to suggest the optimal decisions. Other possible actions: see mission metadata, see personal activity log, construct new protocol, send media, call support, etc.
Before the start of development, we discussed multiple challenges and took a deeper dive into the real life solutions and challenges of each one. We are very passionate about space travel and we are actively interested in the topic of colonising Mars, so this was one of our finalist ideas. We have experience in the industry, having programmed challenging business scenarios in production and maintenance systems for production factories. We thought, that an interactive app that showcases the dynamics between mission control and an actor would highlight the challenge in delayed communication.
After deciding, we created the complete concept for our solution. The next step was to divide the tasks based on our individual skillsets. We used an agile methodology for project management. The main collaboration tool was a physical whiteboard (Kanban) with post-its in the kitchen.
We also used continuous integration and development strategies, having committed every other 15 minutes.
Our solution includes two components: a web client and an Android app.
As mentioned earlier, the web client is the tool used by the mission control back on earth and the app will be used by the astronauts/mars workers.
Our preferred IDEs are IntelliJ and Android Studio.The web client and the backend are developed using JAVA 14, JSF, Hibernate, Spring and others, while the Android is written in Kotlin and uses libraries such as Room, Retrofit 2.0, Coroutines and others. For demonstration purposes the app communicates with the backend via a REST-API, but the existing communication delay between Mars and Earth is computed using DSN data from eye.nasa.gov/dsn/dsn.html and “simulated” into our system.We deployed our solution using Docker, on a self-hosted server.
The biggest problem we faced was finding the right documentation of the Nasa data sources. We found no API to help us with the delay time so this was a challenge to get creative and get it from an alternative source.
Furthermore, we are more backend-oriented, we had some difficulties implementing some frontend features.
On the mobile app part, we encountered several issues with the database synchronisation.
We are very satisfied with our incremental, small task-related achievements, which in the end, added up to form a fully functional proof of concept for our solution, using some very cool Nasa datasources.
Link to live WEB APP: https://tandem.unraid.hibyte.ro/api/spaceapp/init
App APK can be found in the google drive folder: https://drive.google.com/drive/u/1/folders/1PXaDA149CLsrmgsvd_NESlgEMyXjiSKj
*You can authenticate and sync with the web app, by introducing the code generated in the link.
DSN - The Deep Space Network - is NASA’s international array of giant radio antennas that supports interplanetary spacecraft missions, plus a few that orbit Earth. We extracted from their website valuable information, like the communication delay between Earth and Mars and the data transfer speed. We used these information in the implementation of our app.
TDRS - Tracking and Data Relay Satellites - lets the International Space Station contact one of the satellites from anywhere in its orbit. As the communications satellites travel around Earth, they stay above the same relative point on the ground as the planet rotates. TDRS handles voice, video and science data in real time. This was an assumption that we carried over to validate our concept of the martian communication system.
DSOC - Deep Space Optical Communications - will deliver a flight-ready, deep space optical platform assembly and ground data system comprised of a ground laser receiver and transmitter that use existing ground assets. Communications will employ novel, advanced lasers in the near-infrared region of the electromagnetic spectrum. These systems will be capable of delivering information rates at least 10 times faster than conventional systems that use comparable mass and power. This is another assumption made in our concept, that the data transmission rates will be higher.
ESA blog entry about the Curiosity mission landing. This particular blog entry helped us clarify aspects about mission workflows.The Radio Wave Propagation Handbook for Communication on and Around Mars JPL publication helped us in clarifying if the current communication systems will work on Mars.
Mars24 Sunclock provided us with insights into the time calculation on Mars and how to determine the night and the day (day and night time seem to influence communication the most).
We used the Insight: Mars Weather Service API to fetch meta data as demonstration for a possible mars location. The metadata is displayed for the mission control to better inform it about the on the ground situation.
Link to our google drive: https://drive.google.com/drive/u/1/folders/1PXaDA149CLsrmgsvd_NESlgEMyXjiSKj
See presentation, video and mobile app APK.
*You can authenticate and sync with the web app, by introducing the code generated in the link.
DSN - https://eyes.nasa.gov/dsn/dsn.html
TDRS - https://www.nasa.gov/audience/foreducators/stem-on-station/downlinks-scan.html
DSOC- https://www.nasa.gov/mission_pages/tdm/dsoc/index.html
ESA - https://blogs.esa.int/mex/2012/08/05/time-delay-between-mars-and-earth/
Radio Wave Propagation Handbook - https://descanso.jpl.nasa.gov/propagation/mars/MarsPub020318.pdf
Mars24 - https://www.giss.nasa.gov/tools/mars24/
Mars Website - https://mars.nasa.gov
Insight: Mars Weather Service API - https://mars.nasa.gov/insight/weather/