Search NASA⌕ Search

Engineering topics

Atha, D.

Publications and source records attributed to Atha, D..

Lunar Rover Localization Using Craters as Landmarks

Onboard localization capabilities for planetary rovers to date have used relative navigation, by integrating combinations of wheel odometry, visual odometry, and inertial measurements during each drive to track position relative to the start of each drive. At the end of each drive, a “ground-in-the-loop” (GITL) interaction is used to get a position update from human operators in a more global reference frame, such as a map frame defined by orbital reconnaissance imaging of a large region around the rover’s current position. For Mars rovers, this typically has involved downlinking imagery from the rover mast cameras and using interactive visualization tools on Earth to register such images to the orbital reconnaissance images. For safety purposes, rover mission operations typically specify “keep out zones”, which human operators recognize as being unsafe in the orbital images. Autonomous rover drives are limited in distance so that accumulated relative navigation error does not risk the possibility of the rover driving into a keep out zone. The allowable autonomous drive distance in this mode of operation depends on the distribution of keep out zones and the accuracy of relative navigation; in practice, drive limits of a few hundred meters between GITL cycles are to be expected. Several rover mission concepts have recently been studied that require much longer drives between GITL cycles, particularly for the Moon. This includes lunar rover mission concepts that involve (1) driving mostly in sunlight at low latitudes, (2) driving in permanently shadowed regions near the south pole, and (3) a mixture of day and night driving in mid-latitudes. These concepts include total traverse distance requirements of up to 1,800 km in 4 Earth years, with individual drives of several kilometers between stops for downlink. These concepts require greater autonomy to minimize GITL cycles to enable such large range; onboard global localization is a key element of such autonomy. Multiple techniques have been studied in the past for onboard rover global localization, including radio navigation aiding from an orbiter, recognizing horizon landmarks that are known in a regional elevation map, and correlating a local elevation map created onboard the rover with a regional elevation map. These techniques all have drawbacks, including requiring an expensive extra mission element (navigation orbiter), unavailability of sufficient regional elevation map data, or limited accuracy in resulting position estimates (e.g. a few hundred meters with horizon landmarks). For the Moon, the ubiquitous craters offer another possibility, which involves mapping craters from orbit, then recognizing crater landmarks with cameras and/or a lidar onboard the rover. This approach is applicable everywhere on the Moon, does not require high resolution stereo imaging from orbit as some other approaches do, and has potential to enable position knowledge with order of 10 m accuracy at all times. This paper will provide more detail on our technical approach to crater-based lunar rover localization and will present initial results on crater detection using 3-D point cloud data from onboard lidar or stereo cameras and using shading cues in monocular onboard imagery.

Ono, M.↗

New Rover Conops with High-Performance Onboard Computing: Give Up Raw Data to Reduce Ops Cost and Do More Science

A major portion of time during the tactical operation of Mars rovers is spent for selecting, prioritizing, and coordinating sciences and engineering activities such that they fit within resource constraints, including the downlink data volume, energy, and time. In particular, the downlink data volume constraint is getting particularly tighter in recent missions because modern instruments produce increasingly high data volume while the communication bandwidth is essentially bounded by the law of physics. Tactical operation would be substantially simplified, hence the operation cost could be reduced, if the data volume constraint is relaxed or even removed. In this abstract, we propose a new operation paradigm for achieving this goal. The key observation is that, both in science and engineering applications, the bit size of raw data is typically much greater than the volume of processed information that is needed for scientific or engineering analysis. For example, a full-resolution image from Mastcam-Z, the main science camera on Perseverance, is about 700 kB in volume and we downlinked 29,685 images up to Sol 243, totaling ~20 GB of data. But of course, scientists do not use every pixel of these images; what they really look for in the images are geological features, typically represented by specific geometric configurations or textures. An end product after processing hundreds of Mascam-Z images could be a single geological map summarizing the spatial distribution of the features. For another example, a 100-meter drive of Perseverance produces 7-12 MB of drive telemetry, which records every detail of the rover's motion at 8 Hz, including position, attitude, steering angles, encoder readings, motor currents and many other information. But what the ground engineers eventually pay attention to is the signs of anomaly, such as excessive motor currents or high slip; if a drive is nominal, the vast majority of this data is unused. What if, then, we process the raw data onboard and only downlink the processed data that is relevant to scientific or engineering analyses, such as a list of detected science features (with cropped images) or a list of potential signs of anomaly while driving? A major roadblock for such onboard, high-level information processing has been the onboard computational resource. RAD750, the main onboard computer of Perseverance, is obviously not sufficient for performing complex image or signal processing such as object detection, semantic segmentation, or anomaly detection. Interestingly, RAD750 is not the best processor that Perseverance has; Qualcomm's Snapdragon 801, a modern mobile processor, is on her Heli Base Station, a device for communicating with Mars Helicopter Ingenuity; also, Intel's Atom E3845 processors are on engineering cameras. In the reminder of this paper, we will introduce two particular uses cases of these high-performance co-processors (meaning auxiliary CPU, GPU, or other types of processors that are separate from the main processor that runs the main flight software) for lowering operation cost and accommodating more science activities for a given communication constraint.

Didier, A.↗