3 ms·
To amplify your comment, here's a web page with documents from the science definition team -- the panel that decides what exactly the mission will study: https
by mturmon 11y ago
To amplify your comment, here's a web page with documents from the science definition team -- the panel that decides what exactly the mission will study:
https://solarsystem.nasa.gov/europa/sdt2013.cfm https://solarsystem.nasa.gov/europa/sdt2013.cfm
A key document is the very granular "Science Traceability Matrix" which is very focused on "can instruments be made to satisfy these science goals" (zoom in to notice a lot of requirements flow-down from science goals):
https://solarsystem.nasa.gov/europa/docs/Clipper_Trace_Matrix_V2.2_140609.pdf https://solarsystem.nasa.gov/europa/docs/Clipper_Trace_Matri...
And regarding Europa, one particular item of concern has been, can markers of life be detected in a plume as sampled by an orbiter. Here's a recent workshop on the subject:
https://astrobiology.nasa.gov/calendar/europa-plume-workshop/ https://astrobiology.nasa.gov/calendar/europa-plume-workshop...
It's a colossal understatement to say that a standard design plus tailoring isn't really going to lift the burden of figuring out if detecting life in the plume is possible.
But that said, there are re-usable components. Some of the spectral radiometers ("take photos") are largely re-used, also communications devices, etc.
- golergka 11y agoApart from being extremely interesting from space perspective, this matrix seems like a great instrument to help manage a project of this complexity and uncertainty. I wonder what other things software industry can learn from NASA about this stuff.
- fsloth 11y agoWell, NASA did run a software engineering laboratory for 25 years https://www.cs.umd.edu/~basili/publications/proceedings/P94.pdf https://www.cs.umd.edu/~basili/publications/proceedings/P94....
- chii 11y ago> I wonder what other things software industry can learn from NASA they take their software seriously. This is just one shallow article describing their process: https://rhodecode.com/blog/code-review-learn-nasa-codes/ https://rhodecode.com/blog/code-review-learn-nasa-codes/ But i recall reading that they do simulation testing of their rocket firing software - by exhaustively running through all possible input ranges from all their sensors, and add in invalid ranges to boot, and their software _musts_ pass it. Takes days to run i heard.