Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “End Date”

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 361 records · Page 20

Initial Trade Study for In-line Silver Sensor for Spacecraft Potable Water Systems

Ionic silver is currently baselined as the biocide for microbial control in potable water systems for future space exploration missions. In-line monitoring of silver ion concentration is desired for system feedback control to introduce and maintain sufficient and safe levels of biocide in the water. To date, NASA testing of silver biocide system prototypes has made use of an Ion-Selective Electrode (ISE) for in-line silver concentration measurements. However, known issues with ISE technology have continued to motivate a search for alternate sensor systems. Although devices capable of detecting silver are available for terrestrial applications, these systems are generally not well-suited for the unique demands of spaceflight. Desired attributes include: low weight, volume, and power consumption; stable, autonomous, and in-line measurement capability; long calibration lifetime; and limited maintenance requirements. This paper provides the results from a preliminary trade study conducted on three candidate silver sensor technologies: ISEs, Anodic Stripping Voltammetry (ASV), and Fiber Optic Chemical Sensors (FOCS). The review of these technologies includes the rationale for their selection, an overview of the principles of their operation, and a detailed assessment of their strengths and weaknesses relative to the anticipated requirements of future spacecraft applications. The study concluded that none of the currently-available versions of these technologies is suitable for immediate application to spacecraft systems; further technology development should be considered. To that end, recommendations for forward development work have been proposed and provided herein.

Potable Water↗

CubeSub

This presentation introduces and discusses the development of the CubeSub submersible concept, an Autonomous Underwater Vehicle (AUV) designed around the CubeSat satellite form factor. The presented work is part of the author's MSc thesis in Aerospace Engineering at the Royal Institute of Technology, Stockholm, Sweden, and was performed during an internship at the Mission Design Division of the NASA Ames Research Center, Moffett Field, CA. Still in the early stages of its development, the CubeSub is to become a submersible test-bed for technology qualified for underwater and space environments. With the long-term goal of exploring the underwater environments in outer space, such as the alleged subsurface ocean of Jupiter's moon Europa, a number of technology and operational procedures must be developed and matured. To assist in this, the CubeSub platform is introduced as a tool to allow engineers and scientists to easily test qualified technology underwater. A CubeSat is a class of miniaturized satellite built to a standardized size. The base size is 1U (U for unit), corresponding to a 100 x 100 x 113.5 cu mm cube. A 1U CubeSat can in other words easily be held in one hand. Stacking units give larger satellite sizes such as the also commonly used 1.5U, 2U and 3U. The CubeSat standard is in itself already well established and hundreds of CubeSats have to date been launched into space. Compatible technology is readily available and the know-how exists in the space industry, all of which makes it a firm ground to stand on for the CubeSub. The rationale behind using the CubeSat form factor is to make use of this pre-existing foundation, making the CubeSub easy to develop, modular and readily available. It will thereby aid in the process of maturing the concept of a fully space qualified submersible headed for outer space. As a further clarification, the CubeSub is itself not meant for outer space, but to facilitate development of such a vessel. Along with its uses as a testbed, the CubeSub also holds the potential to become a useful tool for exploration and experimentation here on Earth. A highly standardized system utilizing well-known hardware can reduce the cost and required work load for researchers wishing to perform experiments and exploration. Users could design sensors and experiments to comply with the already well established CubeSat standard, which are then carried by the CubeSub to the region of interest. This in turn means that the end users can focus more on formulating the experiment itself and less about how to get it where they want it. The CubeSub is designed to be built up by modules, which can be assembled in different configurations to fulfill different needs. Each module will be powered individually and intermodular communication will be wireless, removing the need for wiring. The inside of the cylindrical hull will be flooded with ambient water to enhance the interaction between payloads and surrounding environment. The overall torpedo-like shape is similar to that of a conventional AUV, slender and smooth. This is to make for a low drag, reduce the risk of snagging on surrounding objects and make it possible to deploy through an ice sheet via a narrow borehole or navigate in tight areas. To keep costs low and further accelerate development, rapid prototyping is utilized wherever possible. Full-scale prototypes are being constructed through 3D-printing and using COTS (Commercial Off-The-Shelf) components. 3D-printing is used both for the largest hull components and the relatively small and delicate propellers. Arduino boards are used for control and internal communication

AUV↗

Rising Above the Cloud - Toward High-Rate Delay-Tolerant Networking in Low-Earth Orbit

The High Data Rate Architecture (HiDRA) project is implementing a High-rate Delay Tolerant Networking (HDTN) capability that can support Low Earth Orbit (LEO) applications and environments. The present state of the effort, future work, and other elements of the work to date are described in this paper. This implementation is intended to support applications that run at 1+ Gbps, per the requirements of modern optical and high-frequency RF links. Uniquely, this implementation is also tuned to support relay and data trunking applications, which might require support for large numbers of small bundles per second. The design for this platform is based entirely on commercial-off-the-shelf (COTS) components, and possesses buffering capabilities in the 5 TB range. This document takes results from previous individual tests and integrates them to demonstrate results in the presence of a coherent use-case: consider a network aboard the ISS which intends to utilize an upcoming optical communications capability. For this use-case, orbital analysis software is used to analyze orbital dynamics, from which a list of access times are generated that might take in to account weather, schedule competition, etc. A variant of Contact Graph Routing (CGR) is applied to these windows to determine an optimal schedule. This schedule is then loaded into the HDTN prototype and, in conjunction with various measurement tools, a complete end-to-end analysis of HDTN's performance is conducted. Various bottlenecks (including storage) are identified: these bottlenecks are expected to help us focus our future work on the elements of the system that are most likely to present issues moving forward. Finally, we discuss possible paths for evolution beyond the present rates supported by the system, including (but not limited to) hardware acceleration.

Hylton, Alan↗

Automation of the Uncertainty Quantification Process Based on Probability Boxes with DAKOTA

To date, while the use of CFD is prevalent, very few efforts have been undertaken that truly attempt to document all (or even most) of the sources of uncertainty in the simulations. Instead, the current state-of-the-art relies heavily on the experience of the CFD practitioner to estimate the uncertainty associated with their simulations through simple sensitivity studies or subject matter expertise. This practice will have to be replaced with a formal uncertainty quantification (UQ) process if CFD is to play an expanded role in the design research and engineering community, test and evaluation community, and ultimately certification for flight. This is especially true for hypersonic air-breathing propulsion systems due to the environment, scale, and duration limitations of ground test facilities. Accounting for uncertainties in a formal manner is a tedious process. Moreover, the typical CFD practitioner is not likely to be familiar with formal UQ methods. Hence, a major obstacle that has prevented the adoption of UQ methods for engineering design and development work is the lack of a tool set to automate most (if not all) of the UQ workflow. Towards this end, the SANDIA package DAKOTA (which has been developed to drive both UQ and optimization processes) will be tightly wrapped around the VULCAN-CFD code to automate the uncertainty quantification process. The automated process will be applied to an isolator turbulence model validation exercise that has previously been documented using a manual approach to the UQ process. Hence, the focus of this paper will be documenting the level to which automation can hide the UQ process details from the CFD practitioner rather than the UQ method itself.

CFD↗

The Center Master Plan For NASA Glenn Research Center

The Center Master Plan for NASA Glenn Research Center is a comprehensive survey of NASA Glenn's current facility assets and a vision of how we see the facilities will change over the next 20 years in order to support the changing NASA Mission. This Center Master Plan is a vital management tool used by all organizations for making near term decisions and in future planning. During the summer of 2004, I worked with Joseph Morris, the Chief Architect in the Facilities Division, on beginning this Center Master Planning Process. The previous Master Plan was completed by the Center in 1985 and contained general information on the background of the facility as well as maps detailing environmental and historic records, land use, utilities, etc. The new Master Plan is required for the Center by NASA headquarters and will include similar types of information as used in the past. The new study will provide additional features including showing how individual buildings are linked to the programs and missions that they serve. The Master Plan will show practical future options for the facility s assets with a twenty year look ahead. The Plan will be electronically retrievable so that it becomes a communications tool for Center personnel. A Center Master Plan, although required, is very beneficial to NASA Glenn Research Center in aiding management with the future direction of the campus. Keeping up-to-date information and future plans readily available to all of NASA Glenn will insure that future real property development efficiently and effectively supports the missions camed out and supported by the Center. A Center Master Plan will also facilitate coordination with Center supported programs, stakeholders, and customers. In addition, it will provide a basis for cooperative planning with local and other governmental organizations and ultimately ensure that future budgets include the Center program needs described in the plan. This will ensure that development plans are safe, practical, and cost effective. To properly formulate any future plans, background information and research are required. Before bringing in a consultant to tackle the three year process anticipated to prepare a Center Master Plan, my job was to gather information on different organizations contributions to the NASA mission, their facility needs, consistent trends they observe, etc. I conducted numerous interviews with personnel such as Directorate Representatives, Division Chiefs, Branch Chiefs, System Managers and Building Managers. I documented the information I received from them for future use. I used the information to create various color-coded maps layering the different data. This was done with the ending objective being to collect the information and place it in a database that will be linked with Aperture (a computer program that generates color-coded map layers from database information) and made electronically retrievable to the Planning Consultant, NASA personnel, program stakeholders, and other governmental agencies. My goal this summer was to gather information and ideas appropriate for use in NASA Glenn Research Center s Master Plan and organize them for future application by the Planning Consultant. By the end of the summer, after completion of my goal, I will utilize my knowledge and create an array of preliminary future plans for the facility that can be passed along as a guidance tool.

Bigach, Kristin M.↗

The Panther Mountain circular structure, a possible buried meteorite crater

Panther Mountain, located near Phoenicia, New York, is part of the Catskill Mountains, which form the eastern end of the Allegheny Plateau in New York. It is a circular mass defined physiographically by an anomalous circular drainage pattern produced by Esopus Creek and its tributary Woodland Creek. The circular valley that rings the mountain is fracture-controlled; where bedrock is exposed, it shows a joint density 5 to 10 times greater than that on either side of the valley. Where obscured by alluvial valley fill, the bedrock's low seismic velocity suggests that this anomalous fracturing is continuous in the bedrock underlying the rim valley. North-south and east-west gravity and magnetic profiles were made across the structure. Terrane-corrected, residual gravity profiles show an 18-mgal negative anomaly, and very steep gradients indicate a near-surface source. Several possible explanations of the gravity data were modeled. We conclude that the Panther Mountain circular structure is probably a buried meteorite crater that formed contemporaneously with marine or fluvial sedimentation during Silurian or Devonian time. An examination of drill core and cuttings in the region is underway to search for ejecta deposits and possible seismic and tsunami effects in the sedimentary section. Success would result in both dating the impact and furnishing a chronostratigraphic marker horizon.

Isachsen, Y. W.↗

Ares I-X Flight Test Vehicle Similitude to the Ares I Crew Launch Vehicle

The Ares I-X Flight Test Vehicle is the first in a series of flight test vehicles that will take the Ares I Crew Launch Vehicle design from development to operational capability. Ares I-X is scheduled for a 2009 flight date, early enough in the Ares I design and development process so that data obtained from the flight can impact the design of Ares I before its Critical Design Review. Decisions on Ares I-X scope, flight test objectives, and FTV fidelity were made prior to the Ares I systems requirements being baselined. This was necessary in order to achieve a development flight test to impact the Ares I design. Differences between the Ares I-X and the Ares I configurations are artifacts of formulating this experimental project at an early stage and the natural maturation of the Ares I design process. This paper describes the similarities and differences between the Ares I-X Flight Test Vehicle and the Ares I Crew Launch Vehicle. Areas of comparison include the outer mold line geometry, aerosciences, trajectory, structural modes, flight control architecture, separation sequence, and relevant element differences. Most of the outer mold line differences present between Ares I and Ares I-X are minor and will not have a significant effect on overall vehicle performance. The most significant impacts are related to the geometric differences in Orion Crew Exploration Vehicle at the forward end of the stack. These physical differences will cause differences in the flow physics in these areas. Even with these differences, the Ares I-X flight test is poised to meet all five primary objectives and six secondary objectives. Knowledge of what the Ares I-X flight test will provide in similitude to Ares I - as well as what the test will not provide - is important in the continued execution of the Ares I-X mission leading to its flight and the continued design and development of Ares I.

Huebner, Lawrence D.↗

Modeling Constellation Virtual Missions Using the Vdot(Trademark) Process Management Tool

The authors have identified a software tool suite that will support NASA's Virtual Mission (VM) effort. This is accomplished by transforming a spreadsheet database of mission events, task inputs and outputs, timelines, and organizations into process visualization tools and a Vdot process management model that includes embedded analysis software as well as requirements and information related to data manipulation and transfer. This paper describes the progress to date, and the application of the Virtual Mission to not only Constellation but to other architectures, and the pertinence to other aerospace applications. Vdot s intuitive visual interface brings VMs to life by turning static, paper-based processes into active, electronic processes that can be deployed, executed, managed, verified, and continuously improved. A VM can be executed using a computer-based, human-in-the-loop, real-time format, under the direction and control of the NASA VM Manager. Engineers in the various disciplines will not have to be Vdot-proficient but rather can fill out on-line, Excel-type databases with the mission information discussed above. The author s tool suite converts this database into several process visualization tools for review and into Microsoft Project, which can be imported directly into Vdot. Many tools can be embedded directly into Vdot, and when the necessary data/information is received from a preceding task, the analysis can be initiated automatically. Other NASA analysis tools are too complex for this process but Vdot automatically notifies the tool user that the data has been received and analysis can begin. The VM can be simulated from end-to-end using the author s tool suite. The planned approach for the Vdot-based process simulation is to generate the process model from a database; other advantages of this semi-automated approach are the participants can be geographically remote and after refining the process models via the human-in-the-loop simulation, the system can evolve into a process management server for the actual process.

Hardy, Roger↗

From Pixels to Planets

The Kepler Mission was launched in 2009 as NASAs first mission capable of finding Earth-size planets in the habitable zone of Sun-like stars. Its telescope consists of a 1.5-m primary mirror and a 0.95-m aperture. The 42 charge-coupled devices in its focal plane are read out every half hour, compressed, and then downlinked monthly. After four years, the second of four reaction wheels failed, ending the original mission. Back on earth, the Science Operations Center developed the Science Pipeline to analyze about 200,000 target stars in Keplers field of view, looking for evidence of periodic dimming suggesting that one or more planets had crossed the face of its host star. The Pipeline comprises several steps, from pixel-level calibration, through noise and artifact removal, to detection of transit-like signals and the construction of a suite of diagnostic tests to guard against false positives. The Kepler Science Pipeline consists of a pipeline infrastructure written in the Java programming language, which marshals data input to and output from MATLAB applications that are executed as external processes. The pipeline modules, which underwent continuous development and refinement even after data started arriving, employ several analytic techniques, many developed for the Kepler Project. Because of the large number of targets, the large amount of data per target and the complexity of the pipeline algorithms, the processing demands are daunting. Some pipeline modules require days to weeks to process all of their targets, even when run on NASA's 128-node Pleiades supercomputer. The software developers are still seeking ways to increase the throughput. To date, the Kepler project has discovered more than 4000 planetary candidates, of which more than 1000 have been independently confirmed or validated to be exoplanets. Funding for this mission is provided by NASAs Science Mission Directorate.

supercomputers↗

Analysis of Data from the Transient Gamma-Ray Spectrometer Experiment on the GGS/Wind Spacecraft

The data analysis from the TGRS experiment is continuing, although the UC Berkeley PI, K. Hurley, is no longer funded for this effort. This experiment has been returning data on the energy spectra and time histories of cosmic gamma-ray bursts since November 1994, and continues to operate in good health. Over a 3 year period ending in November 1997, 41 bursts have been detected simultaneously by TGRS and Dr. Hurley's Ulysses gamma-ray burst experiment. By comparing the times of arrival of a burst at Ulysses and TGRS, we can obtain an annulus of arrival directions for the event. Typical 3sigma annulus widths range from several arcminutes to tens of arcminutes. Because the WIND spacecraft is as far as several light-seconds from Earth, it is sometimes possible to obtain a second annulus using the Burst and Transient Source Experiment (BATSE) aboard the GRO spacecraft. 23 of the 41 bursts were also observed by this experiment. Generally, the two annuli intersect at grazing incidence, leading to a long, narrow error box which reduces somewhat the error circles obtained from BATSE alone. Table 1 summarizes the burst data from TGRS. We plan to defer the publication of these locations until a larger number of events has been accumulated. Measuring the energy spectra of cosmic gamma-ray bursts to search for line emission is one of the prime objectives of this experiment. However, an intense gamma-ray burst is required, or the statistics become too weak to draw meaningful conclusions. One such event has occurred to date, on August 22, 1995, and we have examined it in detail. The spectrum shows no evidence for lines, however.

Hurley, K.↗

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and Their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative a requirement to standardize and control the naming conventions of very disparate systems and technologies are emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation Initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation Initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and birds of a feather activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another

Bradford, Robert N.↗

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative, a requirement to standardize and control the naming conventions of very disparate systems and technologies is emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and Birds of a Feather (BoF) activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another standards body or technologies that are currently not standardized. For activities one through three, we will provide the analysis by either discipline or technology with rationale, identification and brief description of requirements and precedence. For activity four, we will provide a list of current standards bodies e.g. IETF and a list of potential candidates.

Bradford, Robert N.↗

Preserving NASA Historic and Current Mission Data and Adding Value to These for Future Researchers

The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC) has been actively involved in many aspects of ensuring the long-term preservation of NASA earth science data and knowledge. This involves both the recovery and preservation of early NASA meteorological and other earth observation data, as well as preserving the more recent Earth Observation System (EOS) mission data sets which continue or have reached their end of lifetime. The GES DISC adds value to these preserved data by adding metadata and making the data available online to future researchers. The early NASA meteorological and earth observation data sets from the 1960s and 70s were originally archived on magnetic tapes, and visualizations of these data were preserved on 70-mm film. As these media have aged, their contents have been at risk of permanent loss. NASA has given the task of preserving these early data sets to the GES DISC and making these data sets easily available to the public. The data from these early missions are potentially useful to climate researchers as these are some of the only global measurements made at their time. These old data on magnetic tapes and film strips do not contain easily readable metadata, and so to add value the GES DISC has added digital metadata to them so that the data are searchable and findable. The GES DISC is also involved in preserving the data and knowledge from the EOS era missions. The GES DISC follows the guidelines developed for the preservation of data as specified in the NASA EOS Data and Information System (EOSDIS) Earth Science Data Preservation Content Specification (423-SPEC-001) document. To date, the GES DISC has consulted with the data science teams from the following missions: UARS, Earth Probe TOMS, Aura HIRDLS, and SORCE, in order to properly preserve their data and accompanying documentation. The GES DISC is also currently working with the EOS science teams from TRMM, AIRS, MLS, OMI and additional missions to ensure that the relevant documents and data sets are properly archived for future researchers. A standardized procedure for mission data preservation following 423-SPEC-001 makes preservation among the many NASA EOSDIS data centers uniform, so that these could be transitioned easily to a common EOSDIS preservation repository. This presentation will give an overview of the preservation and recovery of the old NASA historical data sets archived at the GES DISC, as well as the data and documentation preservation efforts of the EOS era missions.

James Johnson↗

Autonomous Ocean World Exploration: Advancement of a Virtual Testbed

The search for life (extinct or extant) and potentially habitable bodies in our solar system and beyond is one of the 12 priority science questions outlined in the National Acadamies’ 2022 decadal survey [5]. Extraterrestrial destinations containing liquid water present an opportunity to search for life as we know it, and in recent years an increasing number of such locations have been discovered within our solar system. Several Jovian moons—Europa, Ganymede, and Callisto [10]—and the Saturnian moons Enceladus [8] and Titan [9] are known or suspected to harbor massive subsurface oceans. Of these "ocean worlds", Europa is the focus of at least one planned NASA orbiter mission, Europa Clipper [4], and an early lander mission concept, the Europa Lander [2, 3]. Whereas most robotic missions to the Moon and Mars (e.g. orbiters, rovers, landers) to date have had ground controllers on Earth tightly involved in mission operations, missions to more distant worlds will require a high degree of onboard autonomy due to long communication lags and blackouts, harsh environments (radiation, cold), and more limited battery and hardware life. The past decade has seen great advances in both AI technologies and computing scalability and performance that offer promising solutions for spacecraft autonomy and motivate the software system and research programs described in this paper. The Ocean Worlds Autonomy Testbed for Exploration, Research, and Simulation (OceanWATERS) [1], which has been in development at the NASA Ames Research Center since 2018, is a virtual environment for testing lander autonomy solutions. It is built on the Robot Operating System (ROS), runs on consumer-grade Linux workstations, and was released as open source in 2020. OceanWATERS provides a physical and visual simulation of a prototypical lander in a Europa-like environment (Figure 1). The lander was modeled after requirements and specifications made in JPL’s Europa Lander Study of 2016 [3]. Simulated lander systems include stereo cameras and spotlights mounted on an antenna mast that pans and tilts, a 6 degrees of freedom (DoF) robotic arm with a force-torque sensor and two interchangeable end effectors, and a battery pack power system. The environment consists of multiple terrain models including a highly detailed model sourced from the FROST dataset [11], simulation of surrounding planetary bodies based on an ephemeris model, and lighting from the sun with associated surface illumination, reflectance, and shadows. Operations supported by OceanWATERS include panoramic and directed imaging of the environment and lander workspace, Cartesian and joint-level arm commanding, grinding of the terrain surface (e.g. digging a trench), and scooping of ground material (Figure 2) which can be discarded or collected as science samples in a receptacle that can be emptied (science operations themselves are not simulated). These operations are realized as ROS Actions and are complimented by a wide selection of telemetry that is continually produced by each lander subsystem. The power system model is driven by the open-source Generic Software Architecture for Prognostics (GSAP) [11] that predicts the battery’s remaining useful life and other characteristics. As a testbed for high-level autonomy, OceanWATERS provides an execution framework based on PLEXIL [12], an open-source plan specification language and execution engine developed largely at Ames. NASA's initial development of OceanWATERS, as well the Ocean Worlds Lander Autonomy Testbed (OWLAT) [6], a complimentary physical testbed developed at JPL, was the first step in a plan for realizing candidate onboard autonomy solutions for such planetary landers. In 2020 NASA solicited applications for its Autonomous Robotics Research for Ocean Worlds (ARROW) program, and in 2021 the similar Concepts for Ocean worlds Life Detection Technology (COLDTech) program. Collectively six research teams, based in universities and companies across the United States, were awarded grants to develop and demonstrate autonomy solutions on OceanWATERS and OWLAT. These 1–2-year projects have now finished or are nearing completion, and a wide variety of autonomy challenges in ocean world surface missions were addressed. Prototyped and demonstrated solutions have included autonomous discovery, response and adaptation to system faults and unexpected environmental events, world model synthesis through perception, plan synthesis using learned models, methods to optimize sample target selection and prioritize science data transmission, extension of PLEXIL for stochastic decision-making, and an integration of a model of JPL’s mission-ready COLDArm [7]. Technologies used in these projects include many forms of machine learning, causal reasoning, automated planning, Markov decision processes, formal methods, and other advanced techniques. A more detailed summary of the ARROW and COLDTech projects is given herein. OceanWATERS has had significant enhancements since its open-source release in 2020. Many of its new features were driven or shaped by feedback from the ARROW and COLDTech teams and requirements of their projects. In support of enabling autonomous adaptation to spacecraft faults (a specific capability solicited by both programs), a fault injection and detection framework was developed that supports a wide and growing range of fault types such as locked joints, image loss, and battery failures. The power system model was completed and integrated into the simulator, starting as a single-cell battery model and later upgraded to a multi-cell model with associated faults such as cell disconnection. Arm/terrain interaction was improved by adding a force-torque sensor and associated faults, and an analytic dig force model based on the Balovnev bucket force equations. Environment fidelity was increased by modeling terrain deformation resulting from digging and scooping; visual improvements were made in textures, lighting, and shadows. To facilitate interoperation with OWLAT, a unified command and telemetry interface between the testbeds was developed at the ROS level, along with a PLEXIL interface. The number of lander operations was greatly expanded (e.g. with Cartesian-based arm and antenna movement), and a framework was designed for users to build their own lander actions. A GUI for PLEXIL plan selection was created (Figure 3), and an expansive set of plans were added, such as those that illustrate patterns for fault handling. This paper provides a self-contained high-level description of OceanWATERS, focusing on more detailed coverage of the aforementioned enhancements. It provides a high-level summary of the projects undertaken by participants in the ARROW and COLDTech programs and how these efforts have helped shape OceanWATERS. Finally, potential future work and directions for the testbed are listed, as likely informed by the recent planetary science decadal survey [5].

K Michael Dalal↗

Using NASA Environmental Data to Enhance Public Health Decision Making

The Universities Space Research Association at the NASA Marshall Space Flight Center is collaborating with the University of Alabama at Birmingham (UAB) School of Public Health and the Centers for Disease Control and Prevention (CDC) to address issues of environmental health and enhance public health decision making by utilizing NASA remotely sensed data and products. The objectives of this collaboration are to develop high-quality spatial data sets of environmental variables, and deliver the data sets and associated analyses to local, state and federal end-user groups. These data can be linked spatially and temporally to public health data, such as mortality and disease morbidity, for further analysis and decision making. Three daily environmental data sets have been developed for the conterminous U.S. on different spatial resolutions for the time period 2003-2008: (1) spatial surfaces of estimated fine particulate matter (PM2.5) exposures on a 10-km grid utilizing the US Environmental Protection Agency (EPA) ground observations and NASA s MODerate-resolution Imaging Spectroradiometer (MODIS) data; (2) a 1-km grid of Land Surface Temperature (LST) using MODIS data; and (3) a 12-km grid of daily Solar Insolation (SI) and maximum and minimum air temperature using the North American Land Data Assimilation System (NLDAS) forcing data. These environmental data sets will be linked with public health data from the UAB REasons for Geographic And Racial Differences in Stroke (REGARDS) national cohort study to determine whether exposures to these environmental risk factors are related to cognitive decline and other health outcomes. These environmental datasets and public health linkage analyses will be made available to public health professionals, researchers and the general public through the CDC Wide-ranging Online Data for Epidemiologic Research (WONDER) system and through peer reviewed publications. To date, two of the data sets have been released to the public in CDC WONDER, Daily Air Temperature and Heat Index for years 1979-2010, and Daily Fine Particulate Matter (PM2.5) air quality measures for years 2003-2008. These data in CDC WONDER can be aggregated to the county-level, state-level, or regional-level as per users need and downloaded in tabular, graphical, and map formats. The summary statistical output are available to web and app developers via the WONDER Application Programming Interface (API). The linkage of these data with the CDC WONDER system provides a significant addition to CDC WONDER, allowing public health researchers and policy makers to better include environmental exposure data in the context of other health data available in CDC WONDER online system. It also substantially expands public access to NASA environmental data, making their use by a wide range of decision makers feasible.

Al-Hamdan, Mohammad↗

Multijunction Solar Cell Development and Production at Spectrolab

Development of multijunction space solar cells is much like that for any high technology product. New products face two major pressures from the market: improving performance while maintaining heritage. This duality of purpose is not new and has been represented since ancient times by the Roman god Janus.[1] This deity was typically represented as two faces on a single head: one facing forward and the other to the rear. The image of Janus has been used as symbolism for many combined forces of dual purpose, such as the balance in life between beginnings and endings, or between art and science. For our purposes, Janus represents our design philosophy balance between looking to the future for improvement while simultaneously blending past heritage. In the space photovoltaics industry there are good reasons for both purposes. Looking to the past, a product must have a space flight heritage to gain widespread use. The main reason being that this is an unforgiving business. Spacecraft are expensive to build, launch and operate. Typically once a satellite is launched, in-field service for a power systems problem is near impossible.[2Balanced with this is looking forward. New missions typically require more power than previous programs or attempt new objectives such as a new orbit. And there is always the cost pressure for both the satellite itself as well as the launch costs. Both of which push solar technology to improve power density at a lower cost. The consequence of this balance in a high-risk environment is that space PV develops as a series of infrequent large technology steps or generational changes interspersed with more frequent small technology steps or evolutionary changes. Figure 1 gives a bit of clarification on this point. It depicts the historical progress in space solar cells tracked by efficiency against first launch date for most major products introduced by Spectrolab. The first generation is the Si-based technology reaching a peak values near 15% AM0 (herein denoted for max. power, AM0, 1.353 W/cm2, 28 C). The GaAs single junction device generation supplanted this technology with first flight of GaAs on GaAs substrate in 1982.[3] More recently this generation has been supplanted by the multijunction solar cell GaInP/GaAs/Ge generation. The first launch of a commercial satellite powered by multijunction technology was in 1997 (Hughes HS 601HP) using solar arrays based on Spectrolab s dual junction (DJ) cells. The cells at that time were an impressive 21.5% efficient at beginning-of-life (BOL).[4] Eight years later, the multijunction device has evolved through several versions. The incorporation of an active Ge subcell formed the Triple Junction (TJ) product line at 25.1% efficient, on orbit since November 2001. The evolution of the TJ into the Improved Triple Junction (ITJ) at 26.8% efficient has been on orbit since June of 2002.[5]

Fetzer, Chris↗

Validation of Multisystem Countermeasures Protocol for Spaceflight during Antarctica Winter-over at Palmer Station (Palmer Countermeasures)

Exploration-class missions beyond the Van Allen belt to the Moon and then Mars will begin soon. Low-Earth orbital spaceflight results in the persistent perturbation of the human immune system, characterized by reductions in T and NK cell function, altered cytokine profiles, and the reactivation of latent herpesviruses. While these alterations have not caused widespread clinical issues, some crewmembers experience immune-related adverse events, including manifestations of symptomatic herpes viral reactivation, allergy, and respiratory distress. Because future deep-space exploration missions will be of unprecedented duration, it is reasonable to hypothesize that the immune perturbations observed aboard International Space Station (ISS) will intensify during longer missions in deep space, thereby placing crewmembers at elevated clinical risk. Thus, it is imperative to preserve the immune vigilance of astronauts by developing a countermeasure strategy. Of all the Earth analogs studied to date, an Antarctica winter-over (AWO) mission most closely reproduces the spaceflight experience: prolonged deployment, extreme environment, circadian misalignment, isolation, station lifestyle, and personal risk. The US maintains three primary stations in Antarctica: South Pole Station, McMurdo, and Palmer. Previous studies suggest that stations located near the interior of Antarctica (South Pole, McMurdo) have confounding effects on the immune system due to persistent hypobaric hypoxia. Thus, it was hypothesized that winter-over at a coastal station (Palmer) would be more akin to spaceflight due to its normoxic but still extreme environment. Therefore, AWO at Palmer Station was chosen as the platform for testing and validating the effectiveness of a NASA multi-system countermeasures protocol designed for deep space missions. The array of countermeasure protocols and monitoring methods deployed for each AWO will consist of diet modifications, nutritional supplementation, prescribed aerobic and resistive exercise, and a protocol of stress relieving virtual reality exercises. A multitude of biological sample types, including blood, saliva, and hair will be collected in tandem with the countermeasures in order to examine the combined effectiveness of the countermeasures. Samples and logs from subjects will be transported from Palmer Station to Johnson Space Center for further processing and distribution to co-investigators at the end of each winter-over. Extracted samples will be analyzed by appropriate testing platforms (Multiplex, qPCR, ELISA, etc.) to monitor alterations in leukocyte distribution, T cell and NK function, cytokine profiles, reactivation of latent herpesviruses, and nutritional factors. The data collected will be compared to a control year in which no countermeasures were deployed to evaluate the overall effectiveness of the analog and to validate the candidate immune countermeasure strategy. With the completion of the Antarctica Winter-Over (WO) 2022 control year, samples for 13 subjects have been successfully returned from Antarctica to NASA/JSC for further processing and distribution to Co-Investigators. WO 2023, the first countermeasure year, has also commenced with 11 subject consenting and performing their base line data collections (BDC) held in Chile. Another 5 subjects, who were already stationed at Palmer Station, Antarctica, joined as participates in the investigation. These 5 subjects were consented, but no BDC was able to be collected due to their joining in-mission. Therefore, there will be a total of 16 subjects participating in Antarctica's 2023 Winter-Over.

Cody L Gutierrez↗

The Capillary Flow Experiments Aboard the International Space Station: Increments 9-15

This report provides a summary of the experimental, analytical, and numerical results of the Capillary Flow Experiment (CFE) performed aboard the International Space Station (ISS). The experiments were conducted in space beginning with Increment 9 through Increment 16, beginning August 2004 and ending December 2007. Both primary and extra science experiments were conducted during 19 operations performed by 7 astronauts including: M. Fincke, W. McArthur, J. Williams, S. Williams, M. Lopez-Alegria, C. Anderson, and P. Whitson. CFE consists of 6 approximately 1 to 2 kg handheld experiment units designed to investigate a selection of capillary phenomena of fundamental and applied importance, such as large length scale contact line dynamics (CFE-Contact Line), critical wetting in discontinuous structures (CFE-Vane Gap), and capillary flows and passive phase separations in complex containers (CFE-Interior Corner Flow). Highly quantitative video from the simply performed flight experiments provide data helpful in benchmarking numerical methods, confirming theoretical models, and guiding new model development. In an extensive executive summary, a brief history of the experiment is reviewed before introducing the science investigated. A selection of experimental results and comparisons with both analytic and numerical predictions is given. The subsequent chapters provide additional details of the experimental and analytical methods developed and employed. These include current presentations of the state of the data reduction which we anticipate will continue throughout the year and culminate in several more publications. An extensive appendix is used to provide support material such as an experiment history, dissemination items to date (CFE publication, etc.), detailed design drawings, and crew procedures. Despite the simple nature of the experiments and procedures, many of the experimental results may be practically employed to enhance the design of spacecraft engineering systems involving capillary interface dynamics.

Jenson, Ryan M.↗