Search NASA⌕ Search

SEARCH · Search NASA

Results for “rovers mission operations”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 73 records · Page 4

A preliminary study of Mars rover/sample return missions

The Solar System Exploration Committee (SSEC) of the NASA Advisory Council recommends that a Mars Sample Return mission be undertaken before the year 2000. Comprehensive studies of a Mars Sample Return mission have been ongoing since 1984. The initial focus of these studies was an integrated mission concept with the surface rover and sample return vehicle elements delivered to Mars on a single launch and landed together. This approach, to be carried out as a unilateral U.S. initiative, is still a high priority goal in an Augmented Program of exploration, as the SSEC recommendation clearly states. With this background of a well-understood mission concept, NASA decided to focus its 1986 study effort on a potential opportunity not previously examined; namely, a Mars Rover/Sample Return (MRSR) mission which would involve a significant aspect of international cooperation. As envisioned, responsibility for the various mission operations and hardware elements would be divided in a logical manner with clearly defined and acceptable interfaces. The U.S. and its international partner would carry out separately launched but coordinated missions with the overall goal of accomplishing in situ science and returning several kilograms of surface samples from Mars. Important considerations for implementation of such a plan are minimum technology transfer, maximum sharing of scientific results, and independent credibility of each mission role. Under the guidance and oversight of a Mars Exploration Strategy Advisory Group organized by NASA, a study team was formed in the fall of 1986 to develop a preliminary definition of a flight-separable, cooperative mission. The selected concept assumes that the U.S. would undertake the rover mission with its sample collection operations and our international partner would return the samples to Earth. Although the inverse of these roles is also possible, this study report focuses on the rover functions of MRSR because rover operations have not been studied in as much detail as the sample return functions of the mission.

Source record↗

Photo-realistic Terrain Modeling and Visualization for Mars Exploration Rover Science Operations

Modern NASA planetary exploration missions employ complex systems of hardware and software managed by large teams of. engineers and scientists in order to study remote environments. The most complex and successful of these recent projects is the Mars Exploration Rover mission. The Computational Sciences Division at NASA Ames Research Center delivered a 30 visualization program, Viz, to the MER mission that provides an immersive, interactive environment for science analysis of the remote planetary surface. In addition, Ames provided the Athena Science Team with high-quality terrain reconstructions generated with the Ames Stereo-pipeline. The on-site support team for these software systems responded to unanticipated opportunities to generate 30 terrain models during the primary MER mission. This paper describes Viz, the Stereo-pipeline, and the experiences of the on-site team supporting the scientists at JPL during the primary MER mission.

Edwards, Laurence↗

Prospecting for Polar Volatiles: Results from the Resolve Field

Both the Moon and Mercury evidently host ice and other volatile compounds in cold traps at the planets poles. Determining the form, spatial distribution, and abundance of these volatiles at the lunar poles can help us understand how and when they were delivered and emplaced. This bears directly on the delivery of water and prebiotic compounds to the inner planets over the solar system s history, and also informs plans for utilizing the volatiles as resources for sustained human exploration as well as the commercial development of space. Temperature models and orbital data suggest near-surface volatile concentrations may exist at polar locations not strictly in permanent shadow. Remote operation of a robotic lunar rover mission for the 7-10 days of available sunlight would permit key questions to be answered. But such a short, quick-tempo mission has unique challenges and requires a new concept of operations. Both science and rover operations decisionmaking must be done in real time, requiring immediate situational awareness, data analysis, and decision support tools.

Elphic, Richard C.↗

Overview and Initial Results of SAND-E: Semi-Autonomous Navigation for Detrital Environments

Unmanned aerial systems (UAS) and automated terrain analysis for science and navigation are new technologies for planetary exploration. The Mars Helicopter will fly with the Mars2020 rover, the Dragonfly quadcopter will explore Titan, and Soil Properties and Object Classification (SPOC) software will be used for path planning and navigation on the Mars2020 rover. Using an Argo J5 rover instrumented with stereo cameras and Autonomous Soil Assessment System (ASAS) software, and an off the shelf quadcopter, SAND-E tested the use of automated terrain analysis and UAS data for science operations in a Mars-analog environment in Iceland during July of 2019. Scientifically, we sought to determine changes in the physical and chemical properties of sediments along a glacial-fluvial-aeolian transport pathway. Operationally, we tested rover mission-like scenarios that included UAS images and classified terrain images. Here, we present the initial results for both the operations and science elements of the study. Site Selection: A goal of SAND-E is examine sorting and alteration of sediments in fluvial and aeolian environments in both mineral-dominated and glass-dominated basaltic settings. During the first year of the project we focused on a mineral-dominated environment. Selection of the location was based on prior publications that indicated our selected region had a greater abundance of crystalline sediments than other areas fluvial-aeolian settings in Iceland. Other criteria included the presence of both fluvial and aeolian landforms along a transport pathway such that the sediments in transport could be linked to their source rocks. We chose the Skjaldbreidauhraun glacial outwash plain, which sits at the base of Thórisjökull glacier. The site is 30 km north of Thingvellir National Park and ~2 hours from Reykjavik. The outwash plain is fed by two small catchments that drain from the base of the glacier and cut through hyaloclastite and shield volcano bedrock. The drainage progresses from steep alluvial fans near the glacier into a low-sloping fluvial braidplain that becomes confined by the Skjaldbreidur shield volcano and creates a shallow canyon cut into lava bedrock. The fluvial system was a typical braided alluvial environment composed pebble- and cobble-bedded longitudinal bars and sandy channel beds. The river remained active and fluctuated in response to diurnal runoff cycles near the glacier before disappearing into the sandy substrate downstream. The high concentration of suspended sediment in the river was evident by the cloudy water and the silt and clay-sized sediments that draped the channel beds after abandonment and created playas in the lowest sloping areas of the catchment. The entire fluvial system was affected by the winds generated by frontal systems and katabatic flows descending the glacier. This resulted in the formation of aeolian lag deposits and a wind-deflation plain where the fluvial system was not active. Wind ripples and drifts formed in abandoned fluvial channels from aeolian reworking of the sand-sized fluvial sediments. The silt- and clay-sized sediments found in fluvial channels, bar tops, and playas generated dust plumes during high wind events. Our operation sought to capture the variability in this system by sampling from the range of fluvial and aeolian features 6.3 km (proximal), 11.3 km (medial), and 14.4 km (distal) along the river from its origin at the base of glacier.

Ewing, R. C.↗

Evaluation of Performance, Fatigue and Workload During Real-time, Reactive Telerobotic Mission Control Operations

Real-time, reactive telerobotic mission control operations require personnel to actively operate and manage remotely controlled vehicles or robots in real time. Due to the physical separation of the vehicle from the operator, such operations present many additional factors that can influence fatigue (i.e., degraded mental performance) and workload (i.e., mental and physical cost of task requirements), making it difficult to assess how long an individual can safely and accurately conduct operations. The upcoming Volatiles Investigating Polar Exploration Rover (VIPER) mission involves remotely controlling a lunar vehicle from an Earth-based mission control station. METHODS: In order to determine how long personnel could successfully maintain alertness and performance while operating a rover, we studied seven trained operators (i.e., 5 drivers, 2 real-time scientists) in a simulated mission control environment. We further assessed workload in order to determine whether perceived workload levels would change relative to time on task and by time of day. Operators completed two five-hour simulations in a randomized order, beginning at noon and at midnight. Performance was evaluated every 30 minutes using the psychomotor vigilance task (PVT), Karolinska Sleepiness Scale (KSS), and NASA Task Load Index (NASA-TLX). RESULTS: On average, participants rated themselves as sleepier (5.06 ± 2.28) on the night drives compared to the day drives (3.12 ± 1.44; P < .0001). Workload was rated higher during the day drives (37.93 ± 20.09) compared to night (32.09 ± 21.74; P < .01). Lastly, participants had no change in average reaction time between the two drives. CONCLUSIONS: From the analysis, we observed performance began to degrade after approximately three hours of driving. Our findings suggest that rotating drivers at least every three hours would be prudent to allow for breaks, and to minimize performance degradation, particularly during night shifts.

fatigue↗

Productivity Challenges for Mars Rover Operations

Achieving consistently high levels of productivity for surface exploration missions has been a challenge for Mars missions. While the rovers have made major discoveries and accomplished a large number of objectives, they often require a great deal of effort from the operations teams and achievingobjectives can take longer than anticipated. This paper describes the early stages of a multi-year project to investigate solutions for enhancing surface mission productivity. A primary focus of this early stage is to conduct in-depth studies of Mars Science Laboratory science campaigns to gain a deeper understanding of the factors that impact productivity, and to use this understanding to identify potential changes to flight software and ground operations practices to increase productivity. We present the science campaigns we have selected along with a conceptual model of how surface missions achieve objectives that is used to guide the study. We also provide some early thoughts on the technologies, and their interactions, which we believe will play an important role in addressing surface mission productivity challenges.We are in the early stages of a multi-year project to studyand address productivity challenges of future surface missions. We have identified campaigns from the MSL missionfor study which we believe will yield valuable informationabout the nature of surface mission productivity challenges.Based on preliminary analysis from the data collected weanticipate that the lessons from these case studies will helpdevelop and mature our concepts for changes to flight andground systems to address these challenges.While the focus of our work is on Mars rover missions, webelieve the concepts in the work will be applicable to a variety of in-situ explorers, including Venus, and Titan, as wellas orbital missions, such as the Europa orbiter. These missions will also benefit from the ability to adapt and respondto the latest state of the spacecraft and its environment.

Gaines, Daniel↗

VIPER Lunar Rover Agile Mission Systems

Agile development methods, which have gone from outlier to mainstream in software development, are poised to expand into all aspects of space mission development. Modern software development operates on a principle of continuous deployment, where progress is verified not with conventional metrics, but with a continuous build, available to key stakeholders, enabling direct examination of the state of the code base, and assessment of progress through demonstration of capability. Delivery times are measured in weeks, not months. Stakeholders are part of the process on an ongoing basis. The cost of change is comparatively low and requirements, which often are not precisely defined at the start of a project, may be iteratively refined in a series of agile development cycles. Agile methods are compatible with traditional system engineering methods and may be tailored to the space operations environment. The low cost of change and iterative development cycles of agile enable requirements to be defined as outcomes and constraints, with design details to be refined during the development cycle. We are now at a point where agile methods may be extended beyond software, to Mission Systems, including the Mission Operations System and the Ground Data System. For NASA’s VIPER Lunar Rover Mission, scheduled to land at a lunar pole in late 2023, we are developing the Mission System using agile methods. As in agile software, where the measure of progress is working code, in agile mission system development, the measure of capability is what we can demonstrate. Demonstrations over presentations. We demonstrate mission system capability using simulations. The concept of operations, from commanding, to driving the rover, to how we downlink images for evaluation for a near-real time command cycle, will be tested and proven in simulation, years before we begin the traditional simulation cycle for training. “Say it then simulate it.” We develop and refine our designs using simulations, with an emphasis on new components of the system that are not well known early. For example, the required duration of a mission planning cycle for a lunar surface asset such as VIPER, that operates twenty-four hours a day, seven days a week, with continuous communications and a unique set of constraints based on the physics of the lunar poles and the line of site to Earth, is a unique problem in mission planning that is unlikely to be solved in a series of meetings. A small number of requirements specifying the outcomes may serve as the jumping off point to an agile development cycle, with demonstration in simulations. We have already demonstrated this process with simulations of rover driver decision time. VIPER is driven using near-real time command and control to waypoints. The driver decision time between waypoints is a fundamental enabling unit of productivity to accomplish the mission timeline. We have validated driver decision time in simulations of rover driving at the lunar South Pole, using the prototype mission tools for driving, command and control. The capability to develop and refine designs using simulations as part of agile Mission System development cycle changes the nature of team interactions, creating a focus on doing, rather than analyzing and documenting. Waterfall development cycles were, in part, a product of the significant cost of change in the early days of spaceflight. When the cost of change is high, it is vital to get your requirements right at the outset, because the system will be built to those specifications, and, when change is expensive, you better get it right early. However, modern technology has greatly lowered the cost of change, enabling iterative, rapid development cycles, in which key operations concepts may be tested and refined during development. Extending agile development to the Mission System for VIPER is a significant step in moving agile development methods for space operations beyond software, to the Mission System.

Agile↗

Replication of Segments of STS-94 as a Lunar Surface Mission

The Artemis program established the goal to land the first woman and first person of color on the Moon, but that is only the beginning of the program. Artemis plans to move towards a sustainable phase, with four crew living on the lunar surface for roughly 30-day annual missions, operating from a Pressurized Rover (PR) and a Surface Habitat (SH). The crew will split up – two living and operating from the PR and the others in the SH, perhaps swapping places halfway through the surface mission. There is a significant degree of maturity surrounding PR operations due to the NASA Desert Research and Technology Studies field tests from 2007-2011. However, there is a degree of uncertainty surrounding activity in the SH, with anecdotal speculation among some Artemis lunar surface engineers that the SH crew might not be fully utilized. Contrary to this belief, there is evidence in US human spaceflight history that the SH crew may instead be extremely busy. In particular, portions of the STS-94 Microgravity Science Lab mission demonstrate a science-based use case for crew activity in the SH. Fifteen Spacelab missions (not including STS-83, which was terminated early due to a fuel cell problem and reflown as STS-94) and eight Spacehab missions used the previously mentioned modules as science labs to expand the science capability of shuttle orbital missions, most flown prior to the assembly of the International Space Station. STS-94 is selected as an example of these flights. STS-94 was a 15.7-day mission with a 7-person crew. The crew operated in split 12-hour shifts, enabling 24-hour science operations. STS-94 used the space shuttle Columbia with the Spacelab module and Extended Duration Orbiter pallet in the cargo bay. The STS-94 physical science investigations were intended to explore various physical aspects of microgravity. These same investigations can be conducted on the Moon to explore 1/6 gravity. The Spacelab module was outfitted with several key facilities to enable this research: Large Isothermal Furnace, Combustion Module-1, Droplet Combustion Experiment, EXPRESS Rack, TEMPUS, Gravity Measurement Devices, and Middeck Glovebox. The current reference concept for the SH is a hybrid inflatable in a vertical orientation. Fairly typical of hybrid inflatables, the SH has an aluminum core pressurized section and a larger inflatable volume, in this case attaching to the top of the core. Two crew will live in the SH at a time, though four can briefly occupy the habitat, such as for contingency or handover activities. This paper will discuss use of the STS-94 physical science equipment in the SH and options for the architectural layout of a resulting physics laboratory. It will also discuss how this laboratory may accompany other science facilities such as biology, human research, and geology. The person hours used by the STS-94 crew to conduct physical science research will be estimated and then mapped to a two-person SH crew, making it possible to determine how many days are required in the SH to complete the lunar gravity physical science investigations at varying levels of crew availability.

STS-94↗

Leveraging VIPER Geotechnical and Mobility Insights for Endurance Rover and Traverse Development

A new generation of lunar surface rover exploration is rapidly approaching. This is evidenced by the rise of commercially developed rovers from private companies (e.g., Lunar Outpost’s MAPP) and government agencies, like NASA’s Volatiles Investigating Polar Exploration Rover (VIPER), the Lunar Terrain Vehicle (LTV), and the Endurance/Intrepid rover concepts, and the INSPIRE mission concept. The drive distance requirements for off-world vehicles are also rapidly increasing. For example, LTV driving requirements dictate a 20 km range on a single battery charge, with an overall lifetime requirement of 13,000 km over a minimum 10-year service life. Similarly, NASA's Endurance-A mission concept requires a 2000 km vehicle traverse distance, which is nearly 50 times further than the USSR's Lunokhod 2, the longest lunar rover mission to date. Previous planetary surface missions on the Moon and Mars have revealed harsh mobility conditions: aggressive rocky terrains on Mars severely damaged the Curiosity rover’s wheels, soft lunar regolith caused the Lunokhod 2 rover to sink and NASA’s Apollo 15 LRV (Lunar Roving Vehicle) spun out due to poor traction, which required manual correction. This demonstrates that mobility challenges like wheel degradation and soft soil driving performance must be accounted for in a mission’s design phase to meet increasingly aggressive mission durations and mobility goals. The success of these long duration missions requires highly reliable and durable mobility platforms in conjunction with a more developed understanding of the geotechnical properties of the lunar surface. The VIPER mission is uniquely posed to inform future missions about mobility performance, wheel durability, and lunar surface soil mechanics of sunlit and shadowed regions through use of data streams that already exist for other mission purposes. VIPER’s mission to the lunar south pole will provide a new perspective into off-world mobility challenges including traversal into permanently shadowed regions. Mobility data from VIPER’s mission will represent a first glimpse into the surface mobility challenges of the lunar South Pole. Utilization of VIPER’s existing capabilities including cameras, inertial measurement unit (IMU) data, motor currents/torque, drill data, and the rover’s suspension state and kinematics provide the opportunity to determine potentially useful information for future rover and traverse designs, as well as on-Earth testing practices. Data products collected during VIPER’s mission could inform design considerations for the Endurance rover much earlier than NASA’s standard “lessons learned” approach as VIPER has a highly tactical mission operations structure. This work outlines the specific links between possible data products from the VIPER mission and their potential impact on the Endurance/Intrepid mission concepts in their early design phases. From VIPER, we will also gain insights for future development of onboard mobility software as VIPER is a way-point driven rover which requires more constant human operation on Earth than some other rover missions (non-lunar surface). Primary VIPER data products and insights of interest include wheel sinkage, wheel slip, wheel degradation, surface soil shear strength, and terrain slope estimation. VIPER data products will be made available via the Planetary Data System’s Geosciences and Cartography and Imaging Sciences nodes, conforming to the PDS4 standard.

mobility↗

The Rover Software of the VIPER Mission

The VIPER mission exhibits a unique set of operational and environmental constraints, which provide opportunities as well as impose unique challenges for a robotic surface mission.VIPER Rover Software architecture and design targets these constraints in innovative ways to meet the mission’s technical and operational requirements. In this presentation we describe the design of VIPER’s rover software and present early results from its realization.

Flight software↗

MAPGEN Planner: Mixed-Initiative Activity Planning for the Mars Exploration Rover Mission

This document describes the Mixed-initiative Activity Plan Generation system MAPGEN. The system is be- ing developed as one of the tools to be used during surface operations of NASA's Mars Exploration Rover mission (MER). However, the core technology is general and can be adapted to different missions and applications. The motivation for the system is to better support users that need to rapidly build activity plans that have to satisfy complex rules and fit within resource limits. The system therefore combines an existing tool for activity plan editing and resource modeling, with an advanced constraint-based reasoning and planning framework. The demonstration will show the key capabilities of the automated reasoning and planning component of the system, with emphasis on how these capabilities will be used during surface operations of the MER mission.

Ai-Chang, Mitch↗

Remote Diagnosis and Operational Response to an In-Flight Failure of the Drill Feed Mechanism Onboard the Mars Science Laboratory Rover

On November 30th, 2016 (Sol 1536 of the mission), the Mars Science Laboratory (MSL) flight operations team commanded the Curiosity rover to drill into a Martian rock to acquire the mission’s 16th rock powder sample. The drilling operation was halted when the drill feed mechanism unexpectedly stalled shortly after disengaging its magnetically-actuated friction brake at the start of a long move to extend the drill bit into contact with the target rock. The drilling campaign was put on hold and later abandoned as diagnostic experimentation revealed a tendency for the actuator to transition in and out of a high-drag state in which the mechanism could not actuate. In the subsequent months, the team conducted a variety of in-flight and ground-based investigations to determine root cause and identify mitigation strategies for continued operation. Mechanism reliability continued to degrade and by June 2017, it became clear that the mechanism could not be relied upon to support drilling operations. The team succeeded in fully extending the feed, enabling the development of new sampling techniques that would not rely on the feed mechanism. The first feed-extended drilling sample was successfully collected on Sol 2057, 521 sols after the initial feed stall. This paper discusses the anomaly investigation process, failure analysis, and feed mechanism operation mitigation strategies. It concludes with key lessons learned about mechanism design, mission architecture, and operational best practices.

Lin, Megan Richardson↗

Rover Flight Software for the VIPER Mission

The VIPER mission exhibits a unique set of operational and environmental constraints, which provide opportunities as well as impose unique challenges for a robotic surface mission.VIPER Rover Software architecture and design targets these constraints in innovative ways to meet the mission’s technical and operational requirements.In this presentation we describe the design of VIPER’s rover software and present early results from its realization.

Flight Software↗

Rover Flight Software for the VIPER Mission

The VIPER mission exhibits a unique set of operational and environmental constraints, which provide opportunities as well as impose unique challenges for a robotic surface mission.VIPER Rover Software architecture and design targets these constraints in innovative ways to meet the mission’s technical and operational requirements.In this presentation we describe the design of VIPER’s rover software and present early results from its realization.

Flight Software↗

A New Architecture for Visualization: Open Mission Control Technologies

Open Mission Control Technologies (MCT) is a new architecture for visualisation of mission data. Driven by requirements for new mission capabilities, including distributed mission operations, access to data anywhere, customization by users, synthesis of multiple data sources, and flexibility for multi-mission adaptation, Open MCT provides users with an integrated customizable environment. Developed at NASAs Ames Research Center (ARC), in collaboration with NASAs Advanced Multimission Operations System (AMMOS) and NASAs Jet Propulsion Laboratory (JPL), Open MCT is getting its first mission use on the Jason 3 Mission, and is also available in the testbed for the Mars 2020 Rover and for development use for NASAs Resource Prospector Lunar Rover. The open source nature of the project provides for use outside of space missions, including open source contributions from a community of users. The defining features of Open MCT for mission users are data integration, end user composition and multiple views. Data integration provides access to mission data across domains in one place, making data such as activities, timelines, telemetry, imagery, event timers and procedures available in one place, without application switching. End user composition provides users with layouts, which act as a canvas to assemble visualisations. Multiple views provide the capability to view the same data in different ways, with live switching of data views in place. Open MCT is browser based, and works on the desktop as well as tablets and phones, providing access to data anywhere. An early use case for mobile data access took place on the Resource Prospector (RP) Mission Distributed Operations Test, in which rover engineers in the field were able to view telemetry on their phones. We envision this capability providing decision support to on console operators from off duty personnel. The plug-in architecture also allows for adaptation for different mission capabilities. Different data types and capabilities may be added or removed using plugins. An API provides a means to write new capabilities and to create data adaptors. Data plugins exist for mission data sources for NASA missions. Adaptors have been written by international and commercial users. Open MCT is open source. Open source enables collaborative development across organizations and also makes the product available outside of the space community, providing a potential source of usage and ideas to drive product design and development. The combination of open source with an Apache 2 license, and distribution on GitHub, has enabled an active community of users and contributors. The spectrum of users for Open MCT is, to our knowledge, unprecedented for mission software. In addition to our NASA users, we have, through open source, had users and inquires on projects ranging from Internet of Things, to radio hobbyists, to farming projects. We have an active community of contributors, enabling a flow of ideas inside and outside of the space community.

Trimble, Jay↗

Targeting and Localization for Mars Rover Operations

In this work we discuss how the quality of localization knowledge impacts the remote operation of rovers on the surface of Mars. We look at the techniques of localization estimation used in the Mars Pathfinder and Mars Exploration Rover missions. We examine the motivation behind the modes of targeting for different types of activities, such as navigation, remote science, and in situ science. We discuss the virtues and shortcomings of existing approaches and new improvements in the latest operations tools used to support the Mars Exploration Rover missions and rover technology development tasks at the Jet Propulsion Laboratory. We conclude with future directions we plan to explore in improving the localization knowledge available for operations and more effective targeting of rovers and their instrument payloads.

remote rover operations↗

Surface Telerobotics: Development and Testing of a Crew Controlled Planetary Rover System

During Summer 2013, we conducted a series of tests to examine how astronauts in the In- ternational Space Station (ISS) can remotely operate a planetary rover. The tests simulated portions of a proposed mission, in which an astronaut in lunar orbit remotely operates a planetary rover to deploy a radio telescope on the lunar farside. In this paper, we present the design, implementation, and preliminary test results.

Fong, Terry↗

Field Experiments with Planetary Surface Rovers: Lessons for Mars Mission Architecture

Over the last decade, a variety of field experiments have been performed that simulate operations of a rover on Mars. These, in combination with the Pathfinder experience, lead to a realistic assessment of rover mission capabilities and to recommendations for rover technology and mission architecture to improve the science return of Mars exploration. A table summarizes field experiments that represent a range of possible mission designs and operational strategies. The experiments varied by the type and quality of imaging systems and other instrumentation, the use of orbital and aerial imaging and spectroscopy, the communcation bandwidth and command strategy, and the distance traveled. All mission simulations were blind field tests operated by science teams whose interpretations were compared to field ground truth providing an assessment of the accuracy of remote science interpretations and a better understanding of where improvements are needed.

Stoker, Carol↗