Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Deep Operator Networks”

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.

898 records · Page 50

DSN Beowulf Cluster-Based VLBI Correlator

The NASA Deep Space Network (DSN) requires a broadband VLBI (very long baseline interferometry) correlator to process data routinely taken as part of the VLBI source Catalogue Maintenance and Enhancement task (CAT M&E) and the Time and Earth Motion Precision Observations task (TEMPO). The data provided by these measurements are a crucial ingredient in the formation of precision deep-space navigation models. In addition, a VLBI correlator is needed to provide support for other VLBI related activities for both internal and external customers. The JPL VLBI Correlator (JVC) was designed, developed, and delivered to the DSN as a successor to the legacy Block II Correlator. The JVC is a full-capability VLBI correlator that uses software processes running on multiple computers to cross-correlate two-antenna broadband noise data. Components of this new system (see Figure 1) consist of Linux PCs integrated into a Beowulf Cluster, an existing Mark5 data storage system, a RAID array, an existing software correlator package (SoftC) originally developed for Delta DOR Navigation processing, and various custom- developed software processes and scripts. Parallel processing on the JVC is achieved by assigning slave nodes of the Beowulf cluster to process separate scans in parallel until all scans have been processed. Due to the single stream sequential playback of the Mark5 data, some ramp-up time is required before all nodes can have access to required scan data. Core functions of each processing step are accomplished using optimized C programs. The coordination and execution of these programs across the cluster is accomplished using Pearl scripts, PostgreSQL commands, and a handful of miscellaneous system utilities. Mark5 data modules are loaded on Mark5 Data systems playback units, one per station. Data processing is started when the operator scans the Mark5 systems and runs a script that reads various configuration files and then creates an experiment-dependent status database used to delegate parallel tasks between nodes and storage areas (see Figure 2). This script forks into three processes: extract, translate, and correlate. Each of these processes iterates on available scan data and updates the status database as the work for each scan is completed. The extract process coordinates and monitors the transfer of data from each of the Mark5s to the Beowulf RAID storage systems. The translate process monitors and executes the data conversion processes on available scan files, and writes the translated files to the slave nodes. The correlate process monitors the execution of SoftC correlation processes on the slave nodes for scans that have completed translation. A comparison of the JVC and the legacy Block II correlator outputs reveals they are well within a formal error, and that the data are comparable with respect to their use in flight navigation. The processing speed of the JVC is improved over the Block II correlator by a factor of 4, largely due to the elimination of the reel-to-reel tape drives used in the Block II correlator.

Rogstad, Stephen P.↗

Science Hybrid Orbiter and Lunar Relay (SCHOLR) Architecture and Design

Considered both a stepping-stone to deep space and a key to unlocking the mysteries of planetary formation, the Moon offers a unique opportunity for scientific study. Robotic precursor missions are being developed to improve technology and enable new approaches to exploration. Robots, lunar landers, and satellites play significant roles in advancing science and technologies, offering close range and in-situ observations. Science and exploration data gathered from these nodes and a lunar science satellite is intended to support future human expeditions and facilitate future utilization of lunar resources. To attain a global view of lunar science, the nodes will be distributed over the lunar surface, including locations on the far side of the Moon. Given that nodes on the lunar far side do not have direct line-of-sight for Earth communications, the planned presence of such nodes creates the need for a lunar communications relay satellite. Since the communications relay capability would only be required for a small portion of the satellite s orbit, it may be possible to include communication relay components on a science spacecraft. Furthermore, an integrated satellite has the potential to reduce lunar surface mission costs. A SCience Hybrid Orbiter and Lunar Relay (SCHOLR) is proposed to accomplish scientific goals while also supporting the communications needs of landers on the far side of the Moon. User needs and design drivers for the system were derived from the anticipated needs of future robotic and lander missions. Based on these drivers and user requirements, accommodations for communications payload aboard a science spacecraft were developed. A team of interns identified and compared possible SCHOLR architectures. The final SCHOLR architecture was analyzed in terms of orbiter lifetime, lunar surface coverage, size, mass, power, and communications data rates. This paper presents the driving requirements, operational concept, and architecture views for SCHOLR within a lunar surface nodal network. Orbital and bidirectional link analysis, between lunar nodes, orbiter, and Earth, as well as a conceptual design for the spacecraft are also presented

Trase, Kathryn K.↗

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

Truncated ARQ Statistical Link Analysis for Dynamic Links

The future deep space links are migrating towards higher frequency bands such as Ka band and optical. These links are susceptible to non Gaussian and non linear effects such as atmospheric turbulence, scintillation, antenna mis-pointing, jitter, etc. These dynamic links thus will experience various degrees of fading loss, and some of these link disruptions cannot be effectively mitigated by forward error correction coding and/or interleaving. One effective way to ensure reliable communication is by using Automatic Repeat Request (ARQ) protocol, where the receiver acknowledges to the transmitter whether or not a data unit is successfully received. If a data unit is not successfully received (such as after a pre-set time-out), the transmitter would then re-transmit the lost data unit to the receiver. In a previous paper, we derived a statistical link analysis method of finding the optimal operating Signal-to-Noise Ratio (SNR) and estimating the latency of an ARQ scheme. In a more recent paper, we demonstrated the above method using the SNR distribution constructed from the Ka-band (32 GHz) flight data. To simplify the discussion, we considered the academic approach that the ARQ scheme allows for an infinite number of retransmissions. In this paper, we consider the more practical case of a truncated ARQ scheme, where there is a limit on the number of retransmissions. We derive the error probability, the optimal SNR setting, and the latency statistics of the correctly received frames of the truncated ARQ schemes. We first discuss the truncated ARQ link analysis principles using the Gaussian assumption for SNR distribution with a large variance. Next, we demonstrate the statistical truncated ARQ link analysis using the SNR distribution constructed from the Ka-band flight data. The results in this paper can be applied in the design of reliable communication systems such as the Consultative Committee for Space Data System (CCSDS) File Transfer Protocol (CFTP) and the Delay Tolerant Network (DTN).

Morabito, David↗

Radio science receiver support of the Mars Exploration Rover Landings

The low power levels of the communication signals during the Entry Descent and Landing (EDL) sequences of the Mars rovers prevented the transmission of telemetry at X-band signal to inform the mission operations center of the health and progress of the spacecraft. As an altemative, a series of tones were sent to indicate basic spacecraft conditions and execution of critical events. An open-loop receiver designed for Radio Science experiments was used to acquire the signal during this time. The receiver recorded over a 100 Khz bandwidth to identify the presence of the carrier and tones. The data were fed in real-time to a processing unit which detected the carrier and the frequency separation of the tones from the carrier, in order to determine which event has occurred. Up to 256 different tones were possible. During the actual events, all tones were identified, and the carrier was tracked down to the surface, and for the second rover, through the bouncing which followed, and finally, while stopped on the surface, found the carrier and tones which indicated the spacecraft was alive. In order to identify the tones, the ground receivers had to be able to respond to the bevy of events occurring in the relatively short timespan of EDL.

Deep Space Network (DSN)↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Design of Experiment for the Measurement of Aerosol Droplet Size Distribution of Temperature-Controlled Thermally Atomized Printed Electronic Inks

In-Space Manufacturing (ISM) centers around NASA’s growing need and ability to produce space technologies on demand in space. As the future of long term presence in space and deep space exploration approach, fundamental questions of our dependence on earth resupply to Low Earth Orbit (LEO) remain unanswered. ISM is leading various effort to evaluate the feasibility of producing essential spares and redundant parts on demand to enable a sustainable space-based supply chain model for part resupply. Among the parts and systems being considered, Avionics form the neural network of modern day aircraft and space vehicles providing a wealth of information ranging from Guidance, Navigation, and Control (GN&C) systems to on board Environmental Control and Life Support (ECLS) systems. Recent advances in the use of Aerosol Jet Technology to print Avionics components ranging from electrical traces on a circuit board to complex transistors and sensors raise the possibility of using such technology to reproduce or recreate electronic parts on demand with the help of custom electronics 3D printers. The challenge herein lies within the ability of such printers to generate and deposit an aerosol of electronic material utilizing processes independent of or enhanced by gravity to ensure controllably identical or improved behavior of the aerosol in an International Space Station (ISS) laboratory and on the ground. The behavior as well as the hazards and properties associated with such aerosols in a microgravity environment must be understood well in order to merit a feasible approach to utilizing them for manufacturing in space. In this report, we outline the experimental setup of a modified conventional vaping device to be used as the ideal gravity independent thermal atomization mechanism to generate aerosol. Our objective is to identify the ideal mass, density, and volume of our aerosolized droplets of ink to conclude that there exist a threshold of aerosolized ink droplet sizes that are indeed independent of the effects of gravity and remain stable after atomization. We use a Malvern Spraytec® Spray Particle Size Analyzer to perform real-time laser diffraction measurement of our ink droplets during atomization. The droplet size between conductive ink, dielectric ink and vegetable glycerin have been measured and contrasted. Furthermore, the mechanism of thermal atomization versus traditional pneumatic and ultrasonic atomization for operation in microgravity have been explored.

Wu, Chih-Hao↗

SWIPE: Spectral Water Inversion Processor and Emulator

Degradation of Earth’s inland water resources due to anthropogenic perturbations and climate anomalies at both local and global scales continues to place human health at substantial risk. There is now a growing necessity to develop pragmatic approaches that allow timely and effective extrapolation of local processes, to spatially resolved global products, and to promote operational and sustainable resource policy management. This presentation will be discussing the progress made developing SWIPE: Spectral Water Inversion Processor and Emulator. SWIPE is a platform for advanced modeling of coastal and inland aquatic habitats. The goal is create a comprehensive and cohesive system to leverage recent advancements in computation and machine learning to develop a synthetic training ground for sensitivity studies and algorithm development. The four principal facets of SWIPE include: 1. Advanced two-layer coated sphere bio-optical modeling and GPU radiative transfer modeling, 2. Big Data involving massive synthetic spectral libraries of optical properties of various global aquatic particles, surface reflectance, and top-of-atmosphere reflectance, all at hyperspectral resolution leveraging high-end computing systems at NASA Ames Research Center, 3. Deep Learning for algorithm development for water quality inversion of concentrations of common biogeophysical variables as well as optics, full uncertainty characterization by water type, and forward emulation, and lastly, 4. Image Processing for application of developed retrieval algorithms for both hyperspectral and multispectral sensors with experimental corrections for global adjacency, noise, sunglint, and benthic reflectance. This presentation will demonstrate the Equivalent Algal Populations (EAP) two-layer coated sphere scattering model which has been used develop spectral libraries of hyperspectral inherent optical properties of roughly 80 species of phytoplankton, covering 15 different classes and nine taxonomic functional types. The EAP model was also used to derive spectral properties of 10 different non-algal particle functional types. Examples of how the SMART-G (Speed-up Monte-carlo Advanced Radiative Transfer using GPU) radiative transfer code is used to model optically complex aquatic signals will be presented and discussed in the context of creating a massive synthetic database which can leverage the full power of next generation machine learning techniques and high end computing for water quality inversion. We will discuss our active investigation in things like appropriate model architectures, dimensionality reduction techniques such as PCA and autoencoders, uncertainty quantification and abstaining, and which variables actually benefit most from hyperspectral information versus multispectral resolution. We are also curious about questions relating to cost/benefit analysis in terms of computation resources, neural network complexity, and data volumes. Answers to these questions will hopefully elaborate on cost efficiency for potential future sensor design considerations.

SWIPE↗

Launch Complex 34, SWMU CCO542022 DNAPL Source Zone Operations, Maintenance, and Monitoring, Site-Wide Long-Term Monitoring, and Hot Spot 6 Air Sparge System Annual Performance Monitoring Report Cape Canaveral Space Force Station, Florida

This Annual Performance Monitoring Report (PMR) for the Dense Non-Aqueous Phase Liquid (DNAPL) Source Zone (DSZ), Site-Wide Long-Term Monitoring (LTM), and Hot Spot (HS) 6 Air Sparge (AS) System presents the results of Year 13 operation of the hydraulic containment (HC) Interim Measure (IM), the results of performance monitoring direct-push technology (DPT) sampling and monitoring well sampling conducted in the DSZ, results of the biennial site-wide LTM event, and the results of operations and performance sampling of the HS 6 AS IM at Launch Complex 34 (LC34), located at Cape Canaveral Space Force Station (CCSFS), Florida. This site has been designated Solid Waste Management Unit (SWMU) CC054 under the Kennedy Space Center (KSC) Resource Conservation and Recovery Act (RCRA) Corrective Action Program. For the site-wide biennial LTM event, a total of 55 monitoring wells were sampled for volatile organic compounds (VOCs) in February 2023 and one well was sampled for polychlorinated biphenyls (PCBs) in December 2022. One well planned for VOC sampling was found to be destroyed and could not be sampled (CW0002). The LTM wells are screened in two lithologic zones: Layer 1 (0 to 25 feet below land surface [bls]) and Layer 2 (25 to 30 ft bls), and are located in the outlying areas of LC34 to monitor groundwater conditions within the Low-Concentration Plume (LCP), defined as concentrations exceeding Groundwater Cleanup Target Levels (GCTLs), and the High-Concentration Plume (HCP), defined as concentrations exceeding Natural Attenuation Default Concentrations (NADCs). Results from the biennial sampling event indicated overall plume stability and delineation for the plume, which extends over 300 acres. The operational period for Year 13 of the HCS was from April 1, 2022 to March 31, 2023. Operational runtime for the system was 90 percent during Year 13, with downtime events attributed to planned maintenance, system repairs, and power outages. As of March 31, 2023, a total of 313,673,241 cumulative gallons of groundwater containing 88,337 pounds of VOCs have been removed by the HCS. Influent concentrations of trichloroethene (TCE) have decreased since startup from approximately 280,000 μg/L (January 2010) to 12,000 μg/L (March 2023). During the reporting period, all effluent concentrations from the HCS (aqueous and vapor) were below regulatory reporting limits, indicating the system continues to operate as intended. Performance monitoring was conducted in December 2022 within the DSZ to evaluate TCE contamination. Groundwater samples were collected via DPT at nine locations, consistent with previous events between 2017 and 2021. Full vertical profile sampling was completed at each DPT from 8 to 98 feet bls, at 5-foot intervals. The DPT performance monitoring results are summarized in this PMR. The results revealed TCE remains at concentrations greater than 11,000 μg/L in the DSZ (1-percent solubility, indicative of DNAPL) at eight of the nine DPT locations and at depths ranging from 8 to 98 feet bls. In addition to DPT sampling, groundwater samples were collected from deep monitoring wells in the DSZ area (Layers 7 and 8) in December 2022 to verify vertical delineation. Layer 7/8 monitoring well results were non-detect in December 2022, with exception of three wells (IW0162, IW043D2, and IW044D2), where TCE, cis-1,2-dichloroethene (cDCE), and/or vinyl chloride (VC) were detected above GCTLs. These wells are screened 105 to 115 feet bls, which is below the existing recovery well capture zone. TCE was first detected in IW0162 in December 2021 and has since been sampled at least monthly to monitor TCE concentrations. The maximum TCE concentration during this operational period was 15,000 μg/L at IW0162 in March 2023. Because of the increased TCE concentrations in this well, a new recovery well (RW21D), screened 86 to 106 feet bls, was installed in January 2023 and incorporated into existing HCS operations. The HS 6 AS IM was initiated in 2018 with 160 AS wells, and expanded in 2019 with an additional 140 AS wells. Quarterly performance monitoring was reduced to semi-annual in 2020. The HS 6 AS system remained operational during the reporting period covered under this report. The results of the HS 6 system operation and semi-annual performance monitoring are summarized in this report. Semi-annual monitoring results collected in April and October 2022 show concentrations of contaminants of concern (cDCE, trans-1,2-dichloroethene, and vinyl chloride) are generally decreasing and not impacting the surface water drainage canal, indicating the HS 6 IM is meeting objectives. A Phase Two Expansion of the HS 6 AS IM was recently completed. As of the date of this report, the expansion became operational in August 2023 and the first quarter of monitoring was conducted in November 2023. Details of the construction, start-up, and performance monitoring will be included in a future Annual PMR. Overall, the tasks associated with Year 13 operation of the HC IM, operation of the HS 6 AS IM, and biennial site-wide sampling were performed in accordance with recommendations included in the previous 2021 LC34 (Year 12) annual report. Evaluation of results from the HC IM and HS 6 IM show that these systems are operating as designed and meeting performance objectives. Results from the site-wide biennial LTM program also show that the overall network of monitoring wells is adequate to continue monitoring plume-wide conditions.

Complex 34↗

High-Reliability Waveguide Vacuum/Pressure Window

The NASA Deep Space Network (DSN) uses commercial waveguide windows on the output waveguide of Ka-band (32 GHz) low-noise amplifiers. Mechanical failure of these windows resulted in an unacceptable loss in tracking time. To address this issue, a new Ka-band WR-28 waveguide window has been designed, fabricated, and tested. The window uses a slab of low-loss, low-dielectric constant foam that is bonded into a 1/2-wave-thick waveguide/flange. The foam is a commercially available, rigid, closed-cell polymethacrylimide. It has excellent electrical properties with a dielectric constant of 1.04, and a loss tangent of 0.01. It is relatively strong with a tensile strength of 1 MPa. The material is virtually impermeable to helium. The finished window exhibits a leak rate of less than 3x10(exp -3)cu cm/s with helium. The material is also chemically resistant and can be cleaned with acetone. The window is constructed by fabricating a window body by brazing a short length of WR-28 copper waveguide into a standard rectangular flange, and machining the resulting part to a thickness of 4.6 mm. The foam is machined to a rectangular shape with a dimension of 7.06x3.53 mm. The foam is bonded into the body with a two-part epoxy. After curing, the excess glue and foam are knife-trimmed by hand. The finished window has a loss of less than 0.08 dB (2%) and a return loss of greater than 25 dB at 32 GHz. This meets the requirements for the DSN application. The window is usable for most applications over the entire 26-to-40-GHz waveguide band. The window return loss can be tuned to a required frequency by var y in g the thickness of the window slightly. Most standard waveguide windows use a thin membrane of material bonded into a recess in a waveguide flange, or sandwiched between two flanges with a polymer seal. Designs using the recessed window are prone to mechanical failure over time due to constraints on the dimensions of the recess that allow the bond to fail. Designs using the sandwich method are often permeable to helium, which prohibits the use of helium leak detection. At the time of this reporting, 40 windows have been produced. Twelve are in operation with a combined operating time of over 30,000 hours without a failure.

Britcliffe, Michael J.↗

State-of-the-Art: Small Spacecraft Technology

When the first edition of NASA’s Small Spacecraft Technology State-of-the-art report was published in 2013, 247 CubeSats and 105 other non-CubeSat small spacecraft under 50 kilograms (kg) had been launched worldwide, representing less than 2% of launched mass into orbit over multiple years. In 2013 alone, around 60% of the total spacecraft launched had a mass under 600 kg, and of those under 600 kg, 83% were under 200 kg and 37% were nanosatellites (1). Of the total 1,849 spacecraft launched in 2021, 94% were small spacecraft with an overall mass under 600 kg, and of those under 600 kg, 40% were under 200 kg, and 11% were nanosatellites (1). Since 2013, the fight heritage for small spacecraft has increased by over 30% and has become the primary source to space access for commercial, government, private, and academic institutions. The total number of spacecraft launched in the past 10 years is 5,681 and 45% of those had a mass. As with all previous editions of this report, the 2022 edition captures and distills a wealth of new information available on small spacecraft systems from NASA and other publicly available sources. This report is limited to publicly available information and cannot reflect major advances in development that are not publicly disclosed. We encourage any opportunity to publish mission outcomes and technology development milestones (e.g., via conference papers, press releases, company website) so they can be reflected in this report. Overall, this report is a survey of small spacecraft technologies sourced from open literature; it does not endeavor to be an original source, and only considers literature in the public domain to identify and classify devices. Commonly used sources for data include manufacturer datasheets, press releases, conference papers, journal papers, public filings with government agencies, news articles, presentations, the compendium of databases accessed via NASA’s Small Spacecraft Systems Virtual Institute (S3VI) Information Search, and engagement with companies. Data not appropriate for public dissemination, such as proprietary, export controlled, or otherwise restricted data, are not considered. As a result, this report includes many dedicated hours of desk research performed by subject matter experts reviewing resources noted above. Content in this 2022 edition is based on data available by October 2022. This report should not be considered as a comprehensive overview of all the technologies but a great reference for the current state-of-the-art SmallSat technologies. The organizational approach for each chapter is relatively consistent with previous editions and includes an introduction of the technology, current development status of the technology’s procurable systems, and summary tables of technologies surveyed. The content in each chapter is uniquely organized to present a mini-stand-alone report on spacecraft subsystems. As in previous years, chapters include information from previous editions but are updated with new and maturating technologies and reference missions. Tables in each section provide a convenient summary of the technologies discussed, with explanations and references in the body text. The authors have attempted to isolate trends in the small spacecraft industry to point out which technologies have been adopted after successful demonstration missions. Lastly, the authors tried to use the terms “SmallSat,” “microsatellite,” “nanosatellite,” and “CubeSat” in a consistent manner, even as these terms are often used interchangeably in the space industry. Every subsystem chapter contains updated information to reflect the growth in the small spacecraft market. Significant changes are included in several chapters. The “Complete Spacecraft Platforms” chapter now includes information on the two main market options, hosted payload services and dedicated buses. The “Power” chapter provides information on the development of solid-state batteries with significantly higher energy than the current state-of-theart lithium-ion batteries. A large effort was made to update the “Communications” chapter to appropriately capture the recent technology maturation of optical communications for SmallSats. The “Ground Data Systems and Mission Operations” chapter was updated to reflect the recent establishment of the Near Space Network and influx of SmallSat Optical Ground Stations. The “Guidance, Navigation and Control” chapter was updated to include Lidar sensor technology. The “Deorbit Systems” chapter includes a discussion of recently proposed changes by the Federal Communications Commission (FCC) to limit a spacecraft’s lifetime to no longer than 5 years after end-of-mission. The “Identification and Tracking” Chapter includes updated information on the progress of SmallSat tracking. Finally, this report now encompasses technology funded by NASA’s Small Spacecraft Technology (SST) program’s SmallSat Technology Partnerships (STP) initiative which is described further in this Introduction. The reader can find the included SST technology in the “On the Horizon” section of the “Thermal Systems”, “Communications”, and “Guidance, Navigation, and Control” chapters. A central element of this report is to list state-of-the-art technologies by NASA standard Technology Readiness Level (TRL) as defined by the 2020 NASA Engineering Handbook, found in NASA NPR 7123.1C NASA Systems Engineering Processes and Requirements. The authors have endeavored to independently verify the TRL value of each technology by reviewing and citing published test results or publicly available data to the best of their ability. Where test results and data disagree with vendors’ own advertised TRL, the authors have attempted to engage the vendors to discuss the discrepancy. Readers are strongly encouraged to follow the references cited in the literature describing the full performance range and capabilities of each technology. Readers of this report should reach out to individual companies to further clarify information. It is important to note that this report takes a broad system-level view. To attain a high TRL, the subsystem must be in a flight-ready configuration with all supporting infrastructure—such as mounting points, power conversion, and control algorithms—in an integrated unit. An accurate TRL assessment requires a high degree of technical knowledge on a subject device, and an in-depth understanding of the mission (including interfaces and environment) on which the device was flown. There is variability in TRL values depending on design factors for a specific technology. For example, differences in TRL assessment based on the operating environment may result from the thermal environment, mechanical loads, mission duration, or radiation exposure. If a technology has flown on a mission without success, or without providing valid confirmation to the operator, such claimed “flight heritage” was discounted. The authors believe TRLs are most accurately determined when assessed within the context of a program’s unique requirements. While the overall capability of small spacecraft has matured since the 2021 edition of this report, technologies are still being developed to make deep space SmallSat missions more routine and more cost effective. Future editions of this report may include content dedicated to the rapidly growing fields of assembly, integration, and testing services, and mission modeling and simulation–all of which are now extensively represented at small spacecraft conferences. Many of these subsystems and services are still in their infancy, but as they evolve and reliable conventions and standards emerge, the next iteration of this report may also evolve to include additional chapters.

Bruce Yost↗

The circum-Chryse region as a possible example of a hydrologic cycle on Mars: Geologic observations and theoretical evaluation

The transection and superposition relationships among channels, chaos, surface materials units, and other features in the circum-Chryse region of Mars were used to evaluate relative age relationships and evolution of flood events. Channels and chaos in contact (with one another) were treated as single discrete flood-carved systems. Some outflow channel systems form networks and are inferred to have been created by multiple flood events. Within some outflow channel networks, several separate individual channel systems can be traced to a specific chaos which acted as flood-source area to that specific flood channel. Individual flood-carved systems were related to widespread materials units or other surface features that served as stratigraphic horizons. Chryse outflow channels are inferred to have formed over most of the perceivable history of Mars. Outflow channels are inferred to become younger with increasing proximity to the Chryse basin. In addition, outflow channels closer to the basin show a greater diversity in age. The relationship of subsequent outflow channel sources to the sources of earlier floods is inferred to disfavor episodic flooding due to the progressive tapping of a juvenile near-surface water supply. Instead, we propose the circum-Chryse region as a candidate site of past hydrological recycling. The discharge rates necessary to carve the circum-Chryse outflow channels would have inevitably formed temporary standing bodies of H2O on the Martian surface where the flood-waters stagnated and pooled (the Chryse basin is topographically enclosed). These observations and inferences have led us to formulate and evaluate two hypotheses: (1) large amounts of the sublimated H2O off the Chryse basin flood lakes precipitated (snowed) onto the flood-source highlands and this H2O was incorporated into the near surface, recharging the H2O sources, making possible subsequent deluges; and (2) ponded flood-water in Chryse basin drained back down an anti basinward dipping subsurface layer accessed along the southern edge of the lake, recharging the flood-source aquifers. H2O not redeposited in the flood-source region was largely lost to the hydrologic cycle. This loss progressively lowered the vitality of the cycle, probably by now killing it. Our numerical evaluations indicate that of the two hypotheses we formulated, the groundwater seep cycle seems by far the more viable. Optimally, approx. 3/4 of the original mass of an ice-covered cylindrical lake (albedo 0.5, 1 km deep, 100-km radius, draining along its rim for one quarter of its circumference into substrata with a permeability of 3000 darcies) can be modeled to have moved underground (on timescales of the order of 10(exp 3) years) before the competing mechanisms of sublimation and freeze down choked off further water removal. Once underground, this water can travel distances equal to the separation between Chryse basin and flood-source sites in geologically short (approx. 10(exp 6) year-scale) times. Conversely, we calculate that optimally only approx. 40% of the H2O carried from Chryse can condense at the highlands, and most of the precipitate would either collect at the base of the highlands/lowlands scarp or sublimate at rates greater than it would accumulate over the flood-source sites. Further observations from forthcoming missions may permit the determination of which mechanisms may have operated to recycle the Chryse flood-waters.

Moore, Jeffrey M.↗

The Circum-Chryse Region as a Possible Example of a Hydrologic Cycle on Mars: Geologic Observations and Theoretical Evaluation

The transection and superposition relationships among channels, chaos, surface materials units, and other features in the circum-Chryse region of Mars were used to evaluate relative age relationships and evolution of flood events. Channels and chaos in contact (with one another) were treated as single discrete flood-carved systems. Some outflow channel systems form networks and are inferred to have been created by multiple flood events. Within some outflow channel networks, several separate individual channel systems can be traced to a specific chaos which acted as flood-source area to that specific flood channel. Individual flood-carved systems were related to widespread materials units or other surface features that served as stratigraphic horizons. Chryse outflow channels are inferred to have formed over most of the perceivable history of Mars. Outflow channels are inferred to become younger with increasing proximity to the Chryse basin. In addition, outflow channels closer to the basin show a greater diversity in age. The relationship of subsequent outflow channel sources to the sources of earlier floods is inferred to disfavor episodic flooding due to the progressive tapping of a juvenile near-surface water supply. Instead, we propose the circum-Chryse region as a candidate site of past hydrological recycling. The discharge rates necessary to carve the circum-Chryse outflow channels would have inevitably formed temporary standing bodies of H2O on the Martian surface where the flood-waters stagnated and pooled (the Chryse basin is topographically enclosed). These observations and inferences have led us to formulate and evaluate two hypotheses: (1) large amounts of the sublimated H2O off the Chryse basin flood lakes precipitated (snowed) onto the flood-source highlands and this H2O was incorporated into the near surface, recharging the H2O sources, making possible subsequent deluges; and (2) ponded flood-water in Chryse basin drained back down an anti basinward dipping subsurface layer accessed along the southern edge of the lake, recharging the flood-source aquifers. H2O not redeposited in the flood-source region was largely lost to the hydrologic cycle. This loss progressively lowered the vitality of the cycle, probably by now killing it. Our numerical evaluations indicate that of the two hypotheses we formulated, the groundwater seep cycle seems by far the more viable. Optimally, approximately 3/4 of the original mass of an ice-covered cylindrical lake (albedo 0.5, 1 km deep, 100-km radius, draining along its rim for one quarter of its circumference into substrata with a permeability of 3000 darcies) can be modeled to have moved underground (on timescales of the order of 10(exp 3) years) before the competing mechanisms of sublimation and freeze down choked off further water removal. Once underground, this water can travel distances equal to the separation between Chryse basin and flood-source sites in geologically short (approximately 10(exp 6) year-scale) times. Conversely, we calculate that optimally only approximately 40% of the H2O carried from Chryse can condense at the highlands, and most of the precipitate would either collect at the base of the highlands/lowlands scrap or sublimate at rates greater than it would accumulate over the flood-source sites. Further observations from forthcoming missions may permit the determination of which mechanisms may have operated to recycle the Chryse flood-waters.

Moore, Jeffrey M.↗

Thomas Leps Internship Abstract

An optical navigation system is being flown as the backup system to the primary Deep Space Network telemetry for navigation and guidance purposes on Orion. This is required to ensure Orion can recover from a loss of communication, which would simultaneously cause a loss of DSN telemetry. Images taken of the Moon and Earth are used to give range and position information to the navigation computer for trajectory calculations and maneuver execution. To get telemetry data from these images, the size and location of the moon need to be calculated with high accuracy and precision. The reentry envelope for the Orion EM-1 mission requires the centroid and radius of the moon images to be determined within 1/3 of a pixel 3 sigma. In order to ensure this accuracy and precision can be attained, I was tasked with building precise dot grid images for camera calibration as well as building a hardware in the loop test stand for flight software and hardware proofing. To calibrate the Op-Nav camera a dot grid is imaged with the camera, the error between the image dot location and the actual dot location can be used to build a distortion map of the camera and lens system so that images can be fixed to display truth locations. To build the dot grid images I used the Electro Optics Lab optical bench Bright Object Simulator System, and gimbal. The gimbal was slewed to a series of elevations and azimuths. An image of the collimated single point light source was then taken at each position. After a series of 99 images were taken at different locations the single light spots were extracted from each image and added to a composite image containing all 99 points. During the development of these grids it was noticed that an intermittent error in the artificial "star" locations occurred. Prior to the summer this error was attributed to the gimbal having glitches in it's pointing direction and was going to be replaced, however after further examining the issue I determined it to be a software issue. I have since narrowed the likely source of the error down to a Software Development Kit released by the camera supplier PixeLink. I have since developed a workaround in order to build star grids for calibration until the software bug can be isolated and fixed. I was also tasked with building a Hardware in the Loop test stand in order to test the full Op-Nav system. A 4k screen displays simulated Lunar and Terrestrial images from a possible Orion trajectory. These images are then projected through a collimator and then captured with an Op-Nav camera controlled by an Intel NUC computer running flight software. The flight software then analyzes the images to determine attitude and position, this data is then reconstructed into a trajectory and matched to the simulated trajectory in order to determine the accuracy of the attitude and position estimates. In order for the system to work it needs to be precisely and accurately aligned. I developed an alignment procedure that allows the screen, collimator and camera to be squared, centered and collinear with each other within a micron spatially and 5 arcseconds in rotation. I also designed a rigid mount for the screen that was machined on site in Building 10 by another intern. While I was working in the EOL we received a $500k Orion startracker for alignment procedure testing. Due to my prior experience in electronics development, as an ancillary duty, I was tasked with building the cables required to operate and power the startracker. If any errors are made building these cables the startracker would be destroyed, I was honored that the director of the lab entrusted such a critical component with me. This internship has cemented my view on public space exploration. I always preferred public sector to privatization because, as a scientist, the most interesting aspects of space for me are not necessarily the most profitable. I was concerned that the public sector was faltering however, and that in order to improve human space exploration I would be forced into private sector. I now know that, at least at JSC, human spaceflight is still progressing, and exciting work is still being done. I am now actively seeking employment at JSC after I complete my Ph.D and have met with my branch chiefs and mentor to discuss transitioning to a grad Co-op position.

Leps, Thomas↗

Mars Global Surveyor Ka-Band Frequency Data Analysis

The Mars Global Surveyor (MGS) spacecraft, launched on November 7, 1996, carries an experimental space-to-ground telecommunications link at Ka-band (32 GHz) along with the primary X-band (8.4 GHz) downlink. The signals are simultaneously transmitted from a 1.5-in diameter parabolic high gain antenna (HGA) on MGS and received by a beam-waveguide (BWG) R&D 34-meter antenna located in NASA's Goldstone Deep Space Network (DSN) complex near Barstow, California. The projected 5-dB link advantage of Ka-band relative to X-band was confirmed in previous reports using measurements of MGS signal strength data acquired during the first two years of the link experiment from December 1996 to December 1998. Analysis of X-band and Ka-band frequency data and difference frequency (f(sub x)-f(sub ka)/3.8) data will be presented here. On board the spacecraft, a low-power sample of the X-band downlink from the transponder is upconverted to 32 GHz, the Ka-band frequency, amplified to I-W using a Solid State Power Amplifier, and radiated from the dual X/Ka HGA. The X-band signal is amplified by one of two 25 W TWTAs. An upconverter first downconverts the 8.42 GHz X-band signal to 8 GHz and then multiplies using a X4 multiplier producing the 32 GHz Ka-band frequency. The frequency source selection is performed by an RF switch which can be commanded to select a VCO (Voltage Controlled Oscillator) or USO (Ultra-Stable Oscillator) reference. The Ka-band frequency can be either coherent with the X-band downlink reference or a hybrid combination of the USO and VCO derived frequencies. The data in this study were chosen such that the Ka-band signal is purely coherent with the X-band signal, that is the downconverter is driven by the same frequency source as the X-band downlink). The ground station used to acquire the data is DSS-13, a 34-meter BWG antenna which incorporates a series of mirrors inside beam waveguide tubes which guide the energy to a subterranean pedestal room, providing a stable environment for the feed and electronics equipment. A dichroic plate is used to reflect the X-band energy and pass the Ka-band energy to another mirror. The RF energy for each band is then focused onto a feed horn and low-noise amplifier package. After amplification and RF/IF downconversion, the IF signals are sent to the Experimental Tone Tracker (ETT), a digital phase-lock-loop receiver, which simultaneously tracks both X-band and Ka-band carrier signals. Once a signal is detected, the ETT outputs estimates of the SNR in a I -Hz bandwidth (Pc/No), baseband phase and frequency of the signals every I -sec. Between December 1996 and December 1998, the Ka-band and X-band signals from MGS were tracked on a regular basis using the ETT. The Ka-band downlink frequencies described here were referenced to the spacecraft's on-board USO which was also the X-band frequency reference (f(sub ka)= 3.8 f(sub x)). The ETT estimates of baseband phase at I -second sampled time tags were converted to sky frequency estimates. Frequency residuals were then generated for each band by removing a model frequency from each observable frequency at each time tag. The model included Doppler and other effects derived from spacecraft trajectory files obtained from the MGS Navigation Team. A simple troposphere correction was applied to the data. In addition to residuals, the USO frequencies emitted by the spacecraft were estimated. For several passes, the USO frequencies were determined from X-band data and from Ka-band data (referred to X-band by dividing by 3.8) and were found to be in good agreement. In addition, X-band USO frequency estimates from MGS Radio Science data acquired from operational DSN stations were available for comparison and were found to agree within the I Hz level. The remaining sub-Hertz differences were attributed to the different models and software algorithms used by MGS Radio Science and KaBLE-11. A summary of the results of a linear fit of the USO frequency versus time (day of year) is presented in Table I for an initial segment of passes.

Morabito, D.↗