Introduction: Our portfolio provides consistently clear, detailed, and extensive documentation of the design process and project and will allow the audience to be able to clearly follow and replicate our process and start off where we have ended.
Problem Statement: NASA wants to send up Nanolab experiments to the ISS but they don’t have enough experience designing labs. These Nanolabs are based on Agriculture, Fungus growth, Fermentation, and Crystal Growth which will provide data that the researchers will have to collect and interpret. NASA started studying biology and biotechnology in microgravity in order to compare it to the growth on Earth and its dangers on the ISS. Since September of 2000, NASA has conducted approximately 3000 experiments on the ISS. Many of the experiments now utilize a graphical user interface, however, require manual operation. With Nanolabs, the experiments will be autonomous and need a main controller. A friendly user interface is needed in order for the researchers to interact with the NASA experiments and collect their data.
Market Research:
Simple and clean interface
Easy to use and clear directions
Colorful and use of pictures and icons
Clear labeling and formatting
Functions that allow a user to perform multiple tasks at once
Automation
Data analysis and visuals
Efficient (data)
Autonomous
Must be simple enough for a 5th grader to use
Must be complex enough for a professor to effectively gather data from
Testing Plan:
Data transfer every 30 min - 48 occurrences
Raspberry Pi
Connect GUI to external screen
Sensors (Camera, CO2, heat)
Developing cross-platform access
Same python package
Multiple interfaces
Preliminary design 1
Preliminary design 2 and 3
Beginner user interface - Code.org
Intermediate user interface - Kivy (Python)
Advanced user interface - Tkinter (Python)
For the final design, our team decided to utilize the Tkinter python package for all three interfaces and and focused on providing the user with a simple interface but also offering raw data. We took the professional recommendations into account and added pictures along with a table for the selected data file to be stored.
Our team wanted to incorporate the data collection and showcase its capabilities. By using code.org, our team was able to provide a sample of what the simple interface that collected data (from the Fungus Nanolab) and the functions with the data. Our GUI would offer a download feature for the raw data and provide the user with the data time/date along with hardware integration (in this case status and measurement).
Our team is still encouraged to focused more on the data collection aspect of the Nanolabs. Our group should work directly with the other Nanolab groups and share hardware and software so all of the designs will be able to work together and ideally simultaneously (this would be done through autonomy). However NASA HUNCH also desires a visually appealing interface that is able the showcase space exploration and the wonders of NASA missions through pictures and designs.
Conclusion: Our team has designed a Nanolab graphical user interface that is successful to the degree of a single user. It was able to switch tabs, have images, and open files through the file directory with Windows 10. It also displayed the selected file on a external pup-up with the file type and name. The interface also provides a data box which the selected file will be recorded.