As astronauts collect data on the Moon, NASA and the worldwide scientific community will be documenting and reviewing the information in real time. Your challenge is to create an application to allow NASA flight controllers and the broader scientific community to collaborate and compare notes on lunar mission data as it is collected.
Summary
Details
Background
During the Artemis lunar missions a very broad community will be following the lunar surface EVAs (Extravehicular Activities) or spacewalks. Throughout these EVAs crewmembers will be taking photographs, audibly describing what they see, and collecting samples to help answer some of the biggest mysteries regarding the Moon, Earth, and our solar system.
Many people on Earth will be involved in documenting and reviewing this information in real time in addition to the post-mission operations debriefs and scientific research. In the current record-keeping approach implemented for human spaceflight, each flight control team member creates and maintains a console log to record the information necessary to support his/her job duties. This console log becomes part of the official record of the mission. (See video for an example excerpt of a console log written from the perspective of EVA TASK when a crew performed a PGT operation.) Using this present-day system, each flight control team member creates a console log in isolation. In other words, there is no way for a flight controller to simultaneously see the live creation of logs by others or to synchronize multiple people's logs to compare notes with different authors during or after a mission.
Objectives
The goal of this challenge is to create an application that can immediately and seamlessly integrate console log information of many users (at least 100+ users on the same network). Such an application could be valuable to real-time mission support and long-term record keeping of future lunar human spaceflight missions for the benefit of scientific communities and the public.
The demonstration of this capability does not require actual mission data; multi-person logging events on any subject can be used to demonstrate your application.
Potential Considerations
Your application should allow:
- Multiple simultaneous users creating their own console logs
- Real-time live editing of logs that are viewable to anyone on the same network
- Users to select which logs to view (on demand)
- A user to see his/her own console intermixed with the logs from others selected, which could be arranged by time, 'entry topic,' author, or other attributes
- Console log metadata that includes (at a minimum) a timestamp for every entry and a text entry (an entry could also include images)
- The ability to input sample type, written information including descriptions, time tags, hardware used, along with upload of supporting files (photo, video, and audio)
- The capability to add future input fields including user name, 'console seat/position,’ or other attributes
- Users to tag/link log entries from other authors to their own logs
- Each user to 'officially approve' his/her log once the user is ready. This action will create a permanent unmodifiable log that becomes the official written record for that user's profile
Your application should prohibit:
- Users from overwriting or deleting other user’s inputs
- Application access from unapproved people
Potential keywords you can search online: Apollo in real time
For data and resources related to this challenge, refer to the Resources tab at the top of the page. More resources may be added before the hackathon begins.
NASA does not endorse any non-U.S. Government entity and is not responsible for information contained on non-U.S. Government websites.