NASA's Lunar Polar Ice Prospector, RESOLVE: Mission Rehearsal in Apollo Valley
Bibliographic record
Abstract
After the completion of the Apollo Program, space agencies didn't visit the moon for many years. But then in the 90's, the Clementine and Lunar Prospector missions returned and showed evidence of water ice at the poles. Then in 2009 the Lunar Crater Observation and Sensing Satellite indisputably showed that the Cabeus crater contained water ice and other useful volatiles. Furthermore, instruments aboard the Lunar Reconnaissance Orbiter (LRO) show evidence that the water ice may also be present in areas that receive several days of continuous sunlight each month. However, before we can factor this resource into our mission designs, we must understand the distribution and quantity of ice or other volatiles at the poles and whether it can be reasonably harvested for use as propellant or mission consumables. NASA, in partnership with the Canadian Space Agency (CSA), has been developing a payload to answer these questions. The payload is named RESOLVE. RESOLVE is on a development path that will deliver a tested flight design by the end of 2014. The team has developed a Design Reference Mission using LRO data that has RESOLVE landing near Cabeus Crater in May of2016. One of the toughest obstacles for RESOLVE's solar powered mission is its tight timeline. RESOLVE must be able to complete its objectives in the 5-7 days of available sunlight. The RESOLVE team must be able to work around obstacles to the mission timeline in real time. They can't afford to take a day off to replan as other planetary missions have done. To insure that this mission can be executed as planned, a prototype version of RESOLVE was developed this year and tested at a lunar analog site on Hawaii, known as Apollo Valley, which was once used to train the Apollo astronauts. The RESOLVE team planned the mission with the same type of orbital imagery that would be available from LRO. The simulation team prepositioned a Lander in Apollo Valley with RESOLVE on top mounted on its CSA rover. Then the mission simulation began as the operations team's consoles came alive with data and images. They executed the mission just like the real mission with lunar communications delays and limited bandwidth and a realistic remote mission control room. This paper will describe the RESOLVE payload in detail and describe the results of the mission simulation in Hawaii.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.006 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".