Search NASA⌕ Search

Engineering topics

Laubach, Sharon

Publications and source records attributed to Laubach, Sharon.

13 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2021

Mission Concept Design for Autonomous Space Missions using Mission-Level Modeling and Simulation

NASA’s Europa Lander mission is to search for biosignatures on Europa based on in-situ science using a lander architecture. This mission presents a set of challenges that requires a high level of autonomy on the lander system, leading to the need for a new operational paradigm that supports better collaboration and coordination between the lander and the ground operations team. M\&S is used for both designing the onboard system-level autonomy and the ground operations paradigm that allows effective and efficient collaboration and coordination between the lander and the ground operations team. In this paper, M\&S as applied to the design of new mission and operational concepts will be discussed. At its current early stage of the mission development for Europa Lander, the M\&S is used to explore different mission concepts and gain insights for design (formative) rather than to verify and validate fully designed mission concepts quantitatively (summative). Organically, we established a new approach to mission and operational concept exploration using high-fidelity modeling and simulation. M\&S has been an integral part of the approach of defining constraints and assertions, designing mission concepts, assessing (i.e., simulating them), and discovering insights, which feeds back to the definition an design steps. This organically-established approach provided important benefits to the project at its early phase of the development by enabling the project team to be able to build shared understanding of impacts from design characteristics, constraints, and their interactions on the mission performance.

Ye, Sean↗
NASA NTRS2020

Communications with Curiosity during solar conjunction

This study examines the methodology for operating and communicating with NASA's Curiosity Rover (MSL) during the 2019 solar conjunction. For MSL, solar conjunction occurs when the viewing angle between the Sun and Mars from Earth's perspective falls below 3 degrees, which occurs roughly every two Earth years and lasts for about two weeks. This presents a challenge for engineers operating a vehicle on Mars because the degraded signal to noise ratio disrupts data flow between Earth and the spacecraft. As a result, operators designate a command moratorium in which no commands are sent to the rover and instead design long-term plans that are uplinked weeks in advance (rather than the nominal case of daily uplinks). Coordinating communications with the rover leading up to and following conjunction requires negotiations with several orbiters, another lander, and the Deep Space Network (DSN) each with their own set of constraints. It is the Strategic Comm Planning T coordination, which acts as a baseline for the conjunction Comm team faced additional complications such as the arrival of two new spacecraft at Mars - Roscosmos ExoMars Trace Gas Orbiter (TGO).

Laubach, Sharon↗
NASA NTRS2019

MSL relay coordination and tactical planning in the era of InSight, MAVEN, and TGO

This study examines an approach for optimizing the scheduling of regular relay communications between the Mars Science Laboratory (MSL) rover and the non-sun-synchronous Mars orbiters MAVEN and TGO as well as the impacts of the approaching InSight landing on MSL relay and tactical planning. Rover operations require knowledge of recently executed activities, termed decisional data, in order to inform tactical activity planning. As a result, timely and routine data return is critical for nominal rover operations. Mars orbiters are used as relay assets to achieve such timeliness.

Thomas, Steven↗
NASA NTRS2014

Calculation of Operations Efficiency Factors for Mars Surface Missions

The duration of a mission--and subsequently, the minimum spacecraft lifetime--is a key component in designing the capabilities of a spacecraft during mission formulation. However, determining the duration is not simply a function of how long it will take the spacecraft to execute the activities needed to achieve mission objectives. Instead, the effects of the interaction between the spacecraft and ground operators must also be taken into account. This paper describes a method, using "operations efficiency factors", to account for these effects for Mars surface missions. Typically, this level of analysis has not been performed until much later in the mission development cycle, and has not been able to influence mission or spacecraft design. Further, the notion of moving to sustainable operations during Prime Mission--and the effect that change would have on operations productivity and mission objective choices--has not been encountered until the most recent rover missions (MSL, the (now-cancelled) joint NASA-ESA 2018 Mars rover, and the proposed rover for Mars 2020). Since MSL had a single control center and sun-synchronous relay assets (like MER), estimates of productivity derived from MER prime and extended missions were used. However, Mars 2018's anticipated complexity (there would have been control centers in California and Italy, and a non-sun-synchronous relay asset) required the development of an explicit model of operations efficiency that could handle these complexities. In the case of the proposed Mars 2018 mission, the model was employed to assess the mission return of competing operations concepts, and as an input to component lifetime requirements. In this paper we provide examples of how to calculate the operations efficiency factor for a given operational configuration, and how to apply the factors to surface mission scenarios. This model can be applied to future missions to enable early effective trades between operations design, science mission planning, and spacecraft design.

Laubach, Sharon↗
NASA NTRS2014

Evolution of the Scope and Capabilities of Uplink Support Software for Mars Surface Operations

In January of 2004 both of the Mars Exploration Rover spacecraft landed safely, initiating daily surface operations at the Jet Propulsion Laboratory for what was anticipated to be approximately three months of mobile exploration. The longevity of this mission, still ongoing after ten years, has provided not only a tremendous return of scientific data but also the opportunity to refine and improve the methodology by which robotic Mars surface missions are commanded. Since the landing of the Mars Science Laboratory spacecraft in August of 2012, this methodology has been successfully applied to operate a Martian rover which is both similar to, and quite different from, its predecessors. For MER and MSL, daily uplink operations can be most broadly viewed as converting the combined interests of both the science and engineering teams into a spacecraft-safe set of transmittable command files. In order to accomplish these ends a discrete set of mission-critical software tools were developed which not only allowed for conformation to established JPL standards and practices but also enabled innovative technologies specific to each mission. Although these primary programs provided the requisite capabilities for meeting the high-level goals of each distinct phase of the uplink process, there was little in the way of secondary software to support the smooth flow of data from one phase to the next. In order to address this shortcoming a suite of small software tools was developed to aid in phase transitions, as well as to automate some of the more laborious and error-prone aspects of uplink operations. This paper describes the evolution of this software suite, from its initial attempts to merely shorten the duration of the operator's shift, to its current role as an indispensable tool enforcing workflow of the uplink operations process and agilely responding to the new and unexpected challenges of missions which can, and have, lasted many years longer than originally anticipated.

CoUGAR↗
NASA NTRS2008

Schema for Spacecraft-Command Dictionary

An Extensible Markup Language (XML) schema was developed as a means of defining and describing a structure for capturing spacecraft command- definition and tracking information in a single location in a form readable by both engineers and software used to generate software for flight and ground systems. A structure defined within this schema is then used as the basis for creating an XML file that contains command definitions.

Laubach, Sharon↗
NASA NTRS2006

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, the pace of this process was never intended to be continued indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5-day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

mission operations↗
NASA NTRS2006

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, there was never an intention of maintaining the pace of this process indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5- day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

Mars exploration↗
NASA NTRS1997

Mars Rovers: July 4, 1997 and Beyond

Planetary scientist have a unique problem when collecting data for their subject: in the absence of an interplanetary manned space program, they must rely upon remote sensing techniques. An invaluable part of their arsenal is spacecraft which can study the region of interest in detail.

remote sensing Mars Pathfinder Sojourner rover↗