Search NASA⌕ Search

SEARCH · Search NASA

Results for “Load Management”

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 163 records · Page 9

Application of expert systems in the Common Module electrical power system

Each Common Module (CM) of the Space Station must be capable of handling a 50 kW electricity supply, 25 kW for transmission and 25 kW for consumption. The power must be handled and managed by on-board systems, a necessity that dovetails with the objectives of Public Law 98-371, which mandates that the Space Station push the state of the art of automation and AI. Expert systems will be needed to handle the large data flow for the power system and to ensure that the system degrades gracefully. Features of the first expert systems expected for the power system, i.e., a dynamic load planner/scheduler and energy storage subsystem management, fault diagnosis/analysis, health status/trend analysis, and orbital replacement advisor expert systems, are described. Finally, growth Space Station expert systems applications are discussed.

Weeks, D. J.↗

Thermal Management and Power Packaging for Spacecraft of the Next Millennium

Power Distribution; Cabling, fault protection and switches to turn power on/off to spacecraft loads; Isolate loads from bus noise and regulate power to load against disturbances from the load and the bus; Protect the power distribution system from load failures.

X2000 Thermal management Power Packaging Next Mill↗

A Machine Learning Approach to Improve Air Traffic Management Initiatives

Collaborating closely with commercial air carriers and related organizations, the Federal Aviation Administration(FAA) regulates air traffic and ensures the safety and efficiency of air operations. Air traffic controllers make strategic decisions, such as delaying, rerouting, or canceling flights, partly based on guidance provided by the FAA’s Air TrafficControl System Command Center (ATCSCC). The guidance includes, among other things, control measures known asTraffic Management Initiatives (TMIs) designed to enhance safety and improve operational efficiency. TMIs play a crucial role in managing the demand and capacity within the U.S. National Airspace System (NAS). Two major TMIs that are routinely used (primarily to mitigate the adverse effects of bad weather) are Ground Delay Programs (GDPs) andGround Stops (GSs). In a GDP, flights destined for airports facing thunderstorm activity experience delays at their origin airports. This proactive approach minimizes the risk of routing aircraft through hazardous weather conditions and also replaces (fuel burning) airborne delays with ground delays. In a GS, a temporary restriction is imposed on the departure or arrival of aircraft at a specific airport or within a designated airspace. Although other TMIs (e.g., miles-in-trail) are also implemented as part of (air) traffic flow management in the NAS, the focus of this work is on GDPs and GSs. Since TMIs, by design, lead to flight delays or cancellations, it is crucial to put in place the right set of parameters(e.g., scope and duration of the GDP). For example, when the end time of a GDP extends beyond what is necessary, it imposes unnecessary delays on departing flights. This situation could occur as a result of inaccurate prediction of the(required) duration of the GDP based on the weather forecast. On the other hand, if a GDP ends prematurely before the underlying capacity constraints are resolved at the destination airport, it may result in airborne holding. The delicate balance lies in matching the termination of the GDP precisely with the resolution of capacity constraints, avoiding both the imposition of unnecessary ground delays and the need for airborne holding due to premature program termination.Failing to specify the right parameters for TMIs also leads to flight delays, creating a significant obstacle in managing the increasing traffic volumes causing increased work load for the controllers. To address this issue, we propose the integration of Machine Learning (ML) models in the traffic flow management(TFM) pipeline. In current operations, decisions are made by human experts based on extensive training, historical patterns, available traffic and weather data. Since we have an abundance of data from past events that tell us the likely impact of various TMIs, by ingesting historical data, properly trained ML models can offer valuable insights and aid human decision-making. With the FAA increasingly exploring advanced analytics, ML emerges as a focal point for enhancing TFM within the National Airspace System (NAS). As a first step, this study aims to provide traffic controllers with decision-making support for the issuance and adjustment of TMIs. Data analytics and machine learning have been previously employed to address some of the challenges associated with TMIs. Numerous studies have concentrated on various facets of TMI issuance, exploring factors influencing TMI parameters, including arrival rate, airport capacity, and delay prediction. For example, using weather forecasts, several statistical methods were used to produce probabilistic capacity profiles which in conjunction with deterministic models provided insights into the GDP planning process [1–4]. The downside of using deterministic models is that they rely on fixed inputs and predetermined rules, which lack the ability to account for the inherent uncertainty and variability present in real-world scenarios. In a separate series of studies, researchers aimed to predict the occurrences of GDPs and GSs. The majority of these studies utilized various supervised learning methods, including Decision Trees, Naive Bayes, Support VectorMachines, and Random Forests to analyze the influence of weather conditions and arrival demand on TMI incidents[5–8]. However, these studies primarily focused on predicting the incidence of TMIs without explicitly addressing the scope of TMIs, including their duration and their geographical coverage. Furthermore, the emphasis of these studies was largely on GDPs, given their higher frequency and longer duration when compared to GSs. A limited number of studies focused on predicting the parameters of TMIs, specifically addressing their duration and extent. In one such study focusing on optimizing the TMI parameters at San Francisco International Airport (SFO),the authors utilized a probabilistic forecast of fog [9]. They simulated various capacity scenarios based on the (fog)burn-off forecasts, selecting GDP parameters that minimized airborne and overall ground delays. However, this approach exclusively emphasizes stratus (fog) burn-off as the primary determinant of GDP and GS, neglecting other influential factors like severe weather events, runway closures, lower capacity than traffic demand, and other important variables. Given the complexity of predicting the TMI and determining its scope, we seek a more holistic approach. We aim to consider all significant factors that could impact TMIs and their parameters. What sets this research apart is the fusion of all data sources relevant to the issuance and adjustment of TMIs and it represents the first comprehensive attempt to optimize TMIs in this manner. Since this comprehensive solution involves various aspects, we break down the problem into smaller components and input all parameters into a unified model called the “TMI Adjuster”. Figure 1 shows the overall framework and the list of datasets used in each model. The objective of the TMI Adjuster module is to deliver reliable, consistent and expedited recommendations for the progression, adjustment, and termination of TMIs. The ML solution entails developing a pipeline capable of predicting the necessity of a TMI (e.g., GS or GDP) along with its various parameters. For example, in the case of a GS, this includes the scope of the GS either in terms of distance from the destination airport or based on pre-defined airspace sectors. Here, scope refers to those regions and departing airports that are subject to the GS. In this paper, we concentrate on the issuance of GSs in the three major airports in the New York area — LaGuardia(LGA), John F. Kennedy International (JFK), and Newark Liberty International (EWR). We fuse traffic, weather and other relevant aviation data from years 2017 to 2019 to train and validate the ML models. In particular, we use the following datasets: •Terminal Aerodrome Forecast (TAF): meteorological forecasts specific to each airport, issued four times a day, covering predefined time periods. •TMI data: includes all GSs and GDPs along with their respective parameters. •Aviation System Performance Metrics (ASPM): includes traffic related data such as aircraft delays, arrival, and departure rates. •Notices to Airmen (NOTAMs): utilized to extract runway closure data and manage interdependencies between terminals in close proximity. •Flight cancellation data •Airspace Flow Programs (AFP): includes information on flight airborne holdings caused by TMIs. The data preprocessing entails transforming ASPM, TMI, AFP, NOTAMs, and weather data into an hourly format and consolidating all datasets by merging them based on date and time as the primary key. The TMI Adjuster framework comprises two parallel models: one dedicated to GS and a second model focused on GDP. As previously mentioned, our specific focus is on the GS model as a multi-classification problem. In this framework, each data point of the GS model input summarizes ten hours of data. Specifically, the data loader for the GS model generates the input and output of the model as follows: at a given time step, the input includes the actual traffic, weather, and TMI data from the two-hour window before the time step, alongside the weather forecast and scheduled traffic for the next 8 hours starting from the time step. Based on this information, the output of the GS model for each time interval consists of three dimensions. The first dimension represents a binary decision on whether there should be a GS in place for the next hour or not. The second dimension is related to the scope of the GS in the United States, and the third dimension is related to the scope of the GS in Canada (i.e., to determine if the GS impacts airports in Canada).One of the challenges with TMI modeling is the sparsity of TMI events, particularly regarding its scope. To address this challenge in the scope of the GS model output, we implement grouping. The GS scope for the US region is defined based on a list of centers that should be included when the GS is in place. With 20 centers in the US, we utilized historical data to group them into 4 categories. In particular, we summarized our historical data in a graph format where nodes represent centers, and link weights are defined based on the co-occurrence of centers in the scope parameter ofTMIs. By identified strongly connected components in this graph, we were able to partition the centers into four groups. We consider two model structures for the GS Model. Firstly, a hierarchical classification model [10], where the human decision-making for a GS is of hierarchical nature. The decision-maker first decides whether there is a need fora GS, and if the answer is yes, determines the scope. A hierarchical classification model organizes the problem into a class hierarchy, typically a tree or a Directed Acyclic Graph (DAG) structure, and considers the dependency of the decision in the previous step to the next component [10]. Here, we employ the local classifier per level approach, which involves training one multi-class classifier for each level of the class hierarchy. The second structure is the independent structure. In this setting, as the name suggests, we do not consider the dependency of the decisions in the different dimensions of the output of the model. Instead, for each dimension, we train a multi-class classifier independently. Table 1 summarizes GS model statistics for training, validation and testing. The table documents the effect of limiting data to the time steps when there was actually a TMI in place or when a TMI had just terminated. This resulted in a more balanced distribution of the GS class(GS positive class)versus “No GS”(GS negative class), which might help the training process. While JFK and LGA follow very similar distributions, with 40% and 42% GS positive class respectively, EWR has proportionally fewer GS incidents at 28%. Our subsequent phase involves evaluating the performance of both hierarchical structure and independent structure using different state-of-the-art multi-class classifier models such as Random Forest, Decision Trees, K-nearest Neighbors, and Logistic Regression and forecast the duration and scope of the GSs.

Farzan Masrour Shalmani↗

Green Propellant Landing Demonstration at U.S. Range

The Green Propellant Loading Demonstration (GPLD) was conducted December 2015 at Wallops Flight Facility (WFF), leveraging work performed over recent years to bring lower toxicity hydrazine replacement green propellants to flight missions. The objective of this collaboration between NASA Goddard Space Flight Center (GSFC), WFF, the Swedish National Space Board (SNSB), and Ecological Advanced Propulsion Systems (ECAPS) was to successfully accept LMP-103S propellant at a U.S. Range, store the propellant, and perform a simulated flight vehicle propellant loading. NASA GSFC Propulsion (Code 597) managed all aspects of the operation, handling logistics, preparing the procedures, and implementing the demonstration. In addition to the partnership described above, Moog Inc. developed an LMP-103S propellant-compatible titanium rolling diaphragm flight development tank and loaned it to GSFC to act as the GPLD flight vessel. The flight development tank offered the GPLD an additional level of flight-like propellant handling process and procedures. Moog Inc. also provided a compatible latching isolation valve for remote propellant expulsion. The GPLD operation, in concert with Moog Inc. executed a flight development tank expulsion efficiency performance test using LMP-103S propellant. As part of the demonstration work, GSFC and WFF documented Range safety analyses and practices including all elements of shipping, storage, handling, operations, decontamination, and disposal. LMP-103S has not been previously handled at a U.S. Launch Range. Requisite for this activity was an LMP-103S Risk Analysis Report and Ground Safety Plan. GSFC and WFF safety offices jointly developed safety documentation for application into the GPLD operation. The GPLD along with the GSFC Propulsion historical hydrazine loading experiences offer direct comparison between handling green propellant versus safety intensive, highly toxic hydrazine propellant. These described motives initiated the GPLD operation in order to investigate the handling and process safety variances in project resources between LMP-103S and typical in-space propellants. The GPLD risk reduction operation proved successful for many reasons including handling the green propellant at a U.S. Range, loading and pressurizing a flight-like tank, expelling the propellant, measuring the tank expulsion efficiency, and most significantly, GSFC propulsion personnel's new insight into the LMP-103S propellant handling details.

Propellant↗

Green Propellant Loading Demonstration at U.S. Range

The Green Propellant Loading Demonstration (GPLD) was conducted December 2015 at Wallops Flight Facility (WFF), leveraging work performed over recent years to bring lower toxicity hydrazine replacement green propellants to flight missions. The objective of this collaboration between NASA Goddard Space Flight Center (GSFC), WFF, the Swedish National Space Board (SNSB), and Ecological Advanced Propulsion Systems (ECAPS) was to successfully accept LMP-103S propellant at a U.S. Range, store the propellant, and perform a simulated flight vehicle propellant loading. NASA GSFC Propulsion (Code 597) managed all aspects of the operation, handling logistics, preparing the procedures, and implementing the demonstration. In addition to the partnership described above, Moog Inc. developed an LMP-103S propellant-compatible titanium rolling diaphragm flight development tank and loaned it to GSFC to act as the GPLD flight vessel. The flight development tank offered the GPLD an additional level of flight-like propellant handling process and procedures. Moog Inc. also provided a compatible latching isolation valve for remote propellant expulsion. The GPLD operation, in concert with Moog Inc. executed a flight development tank expulsion efficiency performance test using LMP-103S propellant. As part of the demonstration work, GSFC and WFF documented Range safety analyses and practices including all elements of shipping, storage, handling, operations, decontamination, and disposal. LMP-103S has not been previously handled at a U.S. Launch Range. Requisite for this activity was an LMP-103S Risk Analysis Report and Ground Safety Plan. GSFC and WFF safety offices jointly developed safety documentation for application into the GPLD operation. The GPLD along with the GSFC Propulsion historical hydrazine loading experiences offer direct comparison between handling green propellant versus safety intensive, highly toxic hydrazine propellant. These described motives initiated the GPLD operation in order to investigate the handling and process safety variances in project resources between LMP-103S and typical in-space propellants. The GPLD risk reduction operation proved successful for many reasons including handling the green propellant at a U.S. Range, loading and pressurizing a flight-like tank, expelling the propellant, measuring the tank expulsion efficiency, and most significantly, GSFC propulsion personnel's new insight into the LMP-103S propellant handling details.

Green Propellant↗

Space network interoperability panel (SNIP) study

The history and status of the SNIP study conducted by NASA, ESA, and NASDA are reviewed. Particular attention is given to data relay systems development plans; agency load situations; cross support; the top managers agreement about implementation of S-band interoperability and accelerating the K-alpha band high data rate exploration; testing of actual systems; NASA interim architecture for an S-band era system to make NASA spacecraft and TDRSS/TDRS-II compatible with ESA and NASDA systems; tropical rainfall measuring mission support; S-band cross support; and K-alpha band status.

Fahnestock, Dale↗

Parallel simulation today

This paper surveys topics that presently define the state of the art in parallel simulation. Included in the tutorial are discussions on new protocols, mathematical performance analysis, time parallelism, hardware support for parallel simulation, load balancing algorithms, and dynamic memory management for optimistic synchronization.

Nicol, David↗

Characterizing parallel file-access patterns on a large-scale multiprocessor

Rapid increases in the computational speeds of multiprocessors have not been matched by corresponding performance enhancements in the I/O subsystem. To satisfy the large and growing I/O requirements of some parallel scientific applications, we need parallel file systems that can provide high-bandwidth and high-volume data transfer between the I/O subsystem and thousands of processors. Design of such high-performance parallel file systems depends on a thorough grasp of the expected workload. So far there have been no comprehensive usage studies of multiprocessor file systems. Our CHARISMA project intends to fill this void. The first results from our study involve an iPSC/860 at NASA Ames. This paper presents results from a different platform, the CM-5 at the National Center for Supercomputing Applications. The CHARISMA studies are unique because we collect information about every individual read and write request and about the entire mix of applications running on the machines. The results of our trace analysis lead to recommendations for parallel file system design. First the file system should support efficient concurrent access to many files, and I/O requests from many jobs under varying load conditions. Second, it must efficiently manage large files kept open for long periods. Third, it should expect to see small requests predominantly sequential access patterns, application-wide synchronous access, no concurrent file-sharing between jobs appreciable byte and block sharing between processes within jobs, and strong interprocess locality. Finally, the trace data suggest that node-level write caches and collective I/O request interfaces may be useful in certain environments.

Purakayastha, Apratim↗

Post-Flight Sampling and Loading Characterization of Trace Contaminant Control Subassembly Charcoal

Trace chemical contaminants produced by equipment offgassing and human metabolic processes are removed from the atmosphere of the International Space Station s U.S. Segment by a trace contaminant control subassembly (TCCS). The TCCS employs a combination of physical adsorption, thermal catalytic oxidation, and chemical adsorption processes to accomplish its task. A large bed of granular activated charcoal is a primary component of the TCCS. The charcoal contained in this bed, known as the charcoal bed assembly (CBA), is expendable and must be replaced periodically. Pre-flight engineering analyses based upon TCCS performance testing results established a service life estimate of 1 year. After nearly 1 year of cumulative in-flight operations, the first CBA was returned for refurbishment. Charcoal samples were collected and analyzed for loading to determine the best estimate for the CBAs service life. A history of in-flight TCCS operations is presented as well as a discussion of the charcoal sampling procedures and chemical analysis results. A projected service life derived from the observed charcoal loading is provided. Recommendations for better managing TCCS resources are presented.

Perry, J. L.↗

Orbital Winch for High-Strength, Space-Survivable Tethers

An Orbital Winch mechanism enables high-load, multi-line tethers to be deployed and retracted without rotating the spool on which the tether is wound. To minimize damage to the tether and the wound package during retraction or deployment under load, it can incorporate a Tension Management Module that reduces the infeed tension by a factor of 15 through the use of a powered capstan with guide rollers. This design eliminates the need for rotating high-voltage electrical connections in tether systems that use propellantless electro-dynamic propulsion. It can also eliminate the need for rotating optical connections in applications where the tether contains optical fibers. This winch design was developed to deploy a 15-km-long, 15-kg high-strength Hoytether structure incorporating conductive wires as part of the MXER-1 demonstration mission concept. Two slewing rings that orbit around the tether spool, combined with translation of one of the slewing rings back and forth along the spool axis to traverse the wind point, enables the winch to wind the tether. Variations of the traverse motion of the slewing ring can accomplish level winds and conical pirn winds. By removing the non-traversing slewing ring, and adding an actuated guide arm, the winch can manage rapid, low-drag deployment of a tether off the end of a pirn-wound spool, followed by controlled retraction and rewinding, in a manner very similar to a spin-casting reel. The winch requires at least two motor driver controller units to coordinate the action of two stepper motors to accomplish tether deployment or retraction.

Hoyt, Robert↗

Uncrewed Lunar Surface Operations and Support Activities

Sustained human presence on the surface of the Moon and future missions to Mars require increased independence from surface crews and Earth-based mission control to operate efficiently, safely, and reliably. The time for surface crews to perform tasks will be limited. Extravehicular activities by surface personnel are burdensome and time-consuming, even when a continuous human presence on the surface occurs. Identifying and balancing human/automation roles and tasks and infusing automation and autonomy practices early in a system’s lifecycle will be essential to achieve mission objectives. Among these objectives are attaining a sustained human presence, improving performance and mission effectiveness, reducing operations and maintenance (O&M) costs, and ensuring operations that are robust to communication delays. To achieve these objectives, an operational shift toward increased automation and autonomy with less reliance on humans is needed. Uncrewed lunar surface operations and support activities occur when surface crews are not present or are independent of surface crew timeline activities requiring no surface crew oversight or intervention. These uncrewed surface opportunities can also be planned to minimize crew workload that avoids routine maintenance and support tasks, thus maximizing crew exploration time. Uncrewed preparations such as staging and prepositioning equipment and materials before the crew arrives could improve crew task efficiency. Additional opportunities exist to conduct uncrewed science, exploration, and utilization. Uncrewed surface architecture functions can include science and exploration; habitation; launch and landing support; surface communication and navigation; surface power generation and distribution; human surface mobility; lifting, handling, manipulating; excavation, construction, and site preparation; logistics management; maintenance and repair; surface resource utilization; integrated site operations and shared support services (e.g., site scheduling/prioritization, dust mitigation/contamination control, and surface safety). Early robotic lunar surface campaigns will provide information on the availability of resources, such as oxygen and water, and demonstrate surface-based technologies. After the Artemis III human lunar return mission, a series of landers will deliver surface systems, cargo, supplies, science packages, spare parts, and commodities. A balance of crewed and uncrewed surface operations will enable a sustained lunar surface presence at the South Pole of the Moon at a site that will be known as the Artemis Base Camp (ABC). It is envisioned that base camp operations on and around the Moon will then help prepare for the mission durations and activities needed to support the first human mission to Mars. Before long-duration crew missions to the base camp can occur, the necessary surface infrastructure will be pre-deployed and verified operational. Surface assets will be teleoperated and remotely managed from Earth. Additionally, robotic and short-duration crewed missions to the ABC will ensure the site’s merit to achieve long-term science objectives, availability of usable resources, and that terrain, seasonal variations, and illumination conditions are acceptable. ABC will consist of different areas where specific functions and services are rendered, including: • Launch and Landing Area • Habitation Area • Power Production Area • Resource Areas Launch and Landing Area—The launch and landing area will support associated functions for the arrival and departure of vehicles, such as crewed landing and ascent and uncrewed cargo deliveries and offloading. It will evolve from an unimproved site at the beginning of the exploration campaign to a more sustainable landing and launch area that can support repeated arrivals and departures. Initial uncrewed Lunar Terrain Vehicle (LTV) surface operations may include emplacement of navigation beacons and communication equipment, real-time video and photography of landing/liftoff events, and element repositioning, such as portable utility power (PUP) (applicable for other landed assets at other areas). Site preparations, such as surface leveling, soil compaction, and berm/path construction, may be needed for a more sustainable launch and landing area capable of accommodating vehicles that are increasingly more reusable and reduce the effects of plume surface interactions and ejecta impacts on nearby surface assets. During the ABC missions, cargo and logistics will be delivered to the lunar surface via robotic cargo landers before the crew arrives. These shipments, which can arrive in pressurized logistics carriers, will deliver the logistics necessary to support a crewed mission and include items such as food, water, equipment spares, etc. Providing the capability to retrieve, offload, and transport the logistics closer to the ABC site before the arrival of the crew will increase the overall efficiency of crew operations once they arrive. In the sustained phase of exploration, other supporting services may be needed, such as lander propellant servicing, surface power services, commodity refreshes, and additional inspection, maintenance, and repair capabilities, to sustain a cadence of extended personnel stays and cargo arrivals and departures. Habitation Area—Uncrewed support to surface habitation could involve supporting activation and pre-entry operations of the habitat while the crew is in orbit at the Gateway outpost preparing for a surface landing. Surface Habitat (SH) uncrewed operations may include bringing the cabin environment to a habitable temperature and air mix and activating other critical crew support systems. Potential crop production uncrewed tasks in the SH could also include autonomous watering and tending. Additionally, when the crew departs, the SH enters dormancy for the long period of uncrewed operation. A logistical staging area could also be collocated near the SH. If so, staging operations for crew supplies, waste re-location, and recycling operations may be opportunities for uncrewed operations. Power Production Area—The Fission Surface Power (FSP) element and its supporting distribution equipment provide power to surface elements as needed across the ABC to supplement day-to-day operations and survive lunar nights. Uncrewed support of this power system includes any initial LTV-assisted deployments of cables and other distributed equipment, associated electrical connections, and system testing and activation operations. Robotically performing some inspections, maintenance, or repair tasks on the power distribution equipment could reduce the surface crew workload. Resource Area— Uncrewed resource prospecting, mapping, and characterizing possible resource sites is likely to be time-consuming and represents an opportunity for uncrewed operations between crewed missions. Uncrewed mobile equipment operations will be needed in the extreme environments of permanently shadowed locations where resource extractions occur. As In-Situ Resource Utilization (ISRU) pilot plant operations begin, uncrewed surface support activities with available mobile and portable assets (LTV, PUP, etc.) will better support these operations. Any produced commodities can be stored at a centralized storage location for future use. Also associated with these operations is the use of mobile robotic excavators for resource acquisition and robotic/autonomous regolith processing. The waste tailings generated during excavation and regolith processing would also need to be transported and deposited at a dedicated location. Surface assets will continue operating between crew visits to maintain surface capabilities, conduct lunar surface science, technology demonstrations, and public outreach opportunities. Additionally, certain sustaining tasks that would consume valuable crew time could be performed before crew arrival, or after their departure. This capability may offer more affordable options to construct, activate, test, and maintain a broad set of surface assets. Telerobotically operated human surface mobility systems, such as the LTV and Pressurized Rover (PR), can be utilized for various tasks. Surface environmental conditions pose a distinct challenge for all these activities. Surface illumination and localized shadows are one such factor. Night-survival operations could consist of thermal management, battery pre-charging, and load shedding. Some surface systems may hibernate through the night and then awake and continue nominal operations. Uncrewed mobile assets may use a more adaptive approach to optimize their power and operations; one method is to follow the sunlight. Night-survival operations may be initiated remotely by teleoperation, automated, or accomplished by supervised autonomous operation. The ability to pre-deploy and control remote assets in orbit or on Mars before the arrival of the mission crew is a key capability that can be simulated on the moon. The base camp provides a venue where these advanced operational concepts, technologies, and autonomous methods and techniques, including the incorporation of time delays to simulate Earth-Mars latency can be replicated to help buy down future Mars mission risks. This paper will examine the evolution of uncrewed lunar surface operations and support activities. It will also discuss the lunar surface environmental conditions (thermal, lighting, terrain, topography, communications) along with the challenges they pose on uncrewed surface operations, and the performance of these activities with limited to minimal human interaction and/or teleoperation. Since lunar missions include Mars mission analogs, such investigation provides the framework for future uncrewed Mars mission support.

Mark E Lewis↗

Development of Hierarchical Control for a Lunar Habitat DC Microgrid Model Using Power Hardware-in-the-Loop

As interest in space exploration grows, developing a lunar habitat has become a key component of extending missions into deep space. To guarantee reliable power management of a habitat’s DC microgrid, control schemes are needed that can manage the different assets (batteries, photovoltaics, loads) effectively. Proposed hierarchical control schemes are further developed into hardware solutions using Opal-RT’s real-time simulation software and Power Hardware-in-the-Loop platform. Experimental results of a simulated DC microgrid and physical DC/DC components can allow better realization and performance of applications such as battery discharge control.

PHIL↗

A History of Space Toxicology Mishaps: Lessons Learned and Risk Management

After several decades of human spaceflight, the community of space-faring nations has accumulated a diverse and sometimes harrowing history of toxicological events that have plagued human space endeavors almost from the very beginning. Lessons have been learned in ground-based test beds and others were discovered the hard way - when human lives were at stake in space. From such lessons one can build a risk-management framework for toxicological events to minimize the probability of a harmful exposure, while recognizing that we cannot foresee all events. Space toxicologists have learned that relatively harmless compounds can be converted by air revitalization systems into compounds that cause serious harm to the crew. Our toxic risk management strategy now includes an assessment of the fate of any compound that might be released into the atmosphere. Propellants are highly toxic compounds, yet we have not always been able to thoroughly isolate the crew from exposure to these toxicants. Leakage of fluids from systems has resulted in hazardous conditions at times, and the behavior of such compounds inside a spacecraft has taught us how to manage potentially harmful escapes should they occur. Potential combustion events are an ever-present threat to the wellbeing of the crew. Such events have been sufficiently common that we have learned that one cannot judge the health threat of a given fire by the magnitude of the event. Management of such risks demands monitoring of combustion products. In the category of unpredictable toxic events, if one assumes that fires are predictable, we can place experience with toxic microbial metabolites, upsets during repair operations, and discharges from filters that have accumulated a substantial load of pollutants in their absorption beds. Management of such events requires a broad-spectrum, real-time analytical capability to discern the identity and concentrations of pollutants if they enter the atmosphere. Adverse events are an integral part of any human activity, and the spacefaring community must learn as much as possible from mistakes and near misses.

James, John T.↗

Technique and applications of device driver dynamic loading

This paper discusses the techniques and feasibility of dynamically loading device drivers for the real-time operating system of the Space Station Freedom Data Management System. The rationale and advantages of device driver dynamic loading are discussed and the procedures are analyzed. A prototype program is implemented to demonstrate the feasibility and to simplify the procedure of device driver dynamic loading for the Space Station Freedom Program.

Liu, Yuan-Kwei↗

Integrated Stirling Convertor and Hall Thruster Test Conducted

An important aspect of implementing Stirling Radioisotope Generators on future NASA missions is the integration of the generator and controller with potential spacecraft loads. Some recent studies have indicated that the combination of Stirling Radioisotope Generators and electric propulsion devices offer significant trip time and payload fraction benefits for deep space missions. A test was devised to begin to understand the interactions between Stirling generators and electric thrusters. An electrically heated RG- 350 (350-W output) Stirling convertor, designed and built by Stirling Technology Company of Kennewick, Washington, under a NASA Small Business Innovation Research agreement, was coupled to a 300-W SPT-50 Hall-effect thruster built for NASA by the Moscow Aviation Institute (RIAME). The RG-350 and the SPT-50 shown, were installed in adjacent vacuum chamber ports at NASA Glenn Research Center's Electric Propulsion Laboratory, Vacuum Facility 8. The Stirling electrical controller interfaced directly with the Hall thruster power-processing unit, both of which were located outside of the vacuum chamber. The power-processing unit accepted the 48 Vdc output from the Stirling controller and distributed the power to all the loads of the SPT-50, including the magnets, keeper, heater, and discharge. On February 28, 2001, the Glenn test team successfully operated the Hall-effect thruster with the Stirling convertor. This is the world's first known test of a dynamic power source with electric propulsion. The RG-350 successfully managed the transition from the purely resistive load bank within the Stirling controller to the highly capacitive power-processing unit load. At the time of the demonstration, the Stirling convertor was operating at a hot temperature of 530 C and a cold temperature of -6 C. The linear alternator was producing approximately 250 W at 109 Vac, while the power-processing unit was drawing 175 W at 48 Vdc. The majority of power was delivered to the Hall thruster discharge circuit operating at 115 Vdc and 0.9 A. Testing planned for late 2001 will examine the possibility of directly driving the Hall thruster discharge circuit using rectified and filtered output from the Stirling alternator.

Mason, Lee S.↗

Data processing pipeline with transaction-oriented data sharing

This paper makes three contributions to the area of modern science data processing systems. First, the paper describes the science data processing pipeline, developed at the Multi-mission Image Processing Lab of JPL, for transforming raw space data into high quality image data and automating the distribution of data using a high-performance file transaction service. File Exchange Interface is the file transaction service developed MIPL. Second, it presents the FEI component architecture in the are of file transaction management, security,a nd file integrity verfication. Finally, the paper presents the federated model for the FEI service to demonstrate how to create a pool of file trasaction services to support load balancing and service fallover, and simplify service management.

science data processing↗

Use of Semi-Autonomous Tools for ISS Commanding and Monitoring

As the International Space Station (ISS) has moved into a utilization phase, operations have shifted to become more ground-based with fewer mission control personnel monitoring and commanding multiple ISS systems. This shift to fewer people monitoring more systems has prompted use of semi-autonomous console tools in the ISS Mission Control Center (MCC) to help flight controllers command and monitor the ISS. These console tools perform routine operational procedures while keeping the human operator "in the loop" to monitor and intervene when off-nominal events arise. Two such tools, the Pre-positioned Load (PPL) Loader and Automatic Operators Recorder Manager (AutoORM), are used by the ISS Communications RF Onboard Networks Utilization Specialist (CRONUS) flight control position. CRONUS is responsible for simultaneously commanding and monitoring the ISS Command & Data Handling (C&DH) and Communications and Tracking (C&T) systems. PPL Loader is used to uplink small pieces of frequently changed software data tables, called PPLs, to ISS computers to support different ISS operations. In order to uplink a PPL, a data load command must be built that contains multiple user-input fields. Next, a multiple step commanding and verification procedure must be performed to enable an onboard computer for software uplink, uplink the PPL, verify the PPL has incorporated correctly, and disable the computer for software uplink. PPL Loader provides different levels of automation in both building and uplinking these commands. In its manual mode, PPL Loader automatically builds the PPL data load commands but allows the flight controller to verify and save the commands for future uplink. In its auto mode, PPL Loader automatically builds the PPL data load commands for flight controller verification, but automatically performs the PPL uplink procedure by sending commands and performing verification checks while notifying CRONUS of procedure step completion. If an off-nominal condition occurs during procedure execution, PPL Loader notifies CRONUS through popup messages, allowing CRONUS to examine the situation and choose an option of how PPL loader should proceed with the procedure. The use of PPL Loader to perform frequent, routine PPL uplinks offloads CRONUS to better monitor two ISS systems. It also reduces procedure performance time and decreases risk of command errors. AutoORM identifies ISS communication outage periods and builds commands to lock, playback, and unlock ISS Operations Recorder files. Operation Recorder files are circular buffer files of continually recorded ISS telemetry data. Sections of these files can be locked from further writing, be played back to capture telemetry data that occurred during an ISS loss of signal (LOS) period, and then be unlocked for future recording use. Downlinked Operation Recorder files are used by mission support teams for data analysis, especially if failures occur during LOS. The commands to lock, playback, and unlock Operations Recorder files are encompassed in three different operational procedures and contain multiple user-input fields. AutoORM provides different levels of automation for building and uplinking the commands to lock, playback, and unlock Operations Recorder files. In its automatic mode, AutoORM automatically detects ISS LOS periods, then generates and uplinks the commands to lock, playback, and unlock Operations Recorder files when MCC regains signal with ISS. AutoORM also features semi-autonomous and manual modes which integrate CRONUS more into the command verification and uplink process. AutoORMs ability to automatically detect ISS LOS periods and build the necessary commands to preserve, playback, and release recorded telemetry data greatly offloads CRONUS to perform more high-level cognitive tasks, such as mission planning and anomaly troubleshooting. Additionally, since Operations Recorder commands contain numerical time input fields which are tedious for a human to manually build, AutoORM's ability to automatically build commands reduces operational command errors. PPL Loader and AutoORM demonstrate principles of semi-autonomous operational tools that will benefit future space mission operations. Both tools employ different levels of automation to perform simple and routine procedures, thereby offloading human operators to perform higher-level cognitive tasks. Because both tools provide procedure execution status and highlight off-nominal indications, the flight controller is able to intervene during procedure execution if needed. Semi-autonomous tools and systems that can perform routine procedures, yet keep human operators informed of execution, will be essential in future long-duration missions where the onboard crew will be solely responsible for spacecraft monitoring and control.

Brzezinski, Amy S.↗

Interactive Management and Updating of Spatial Data Bases

The decision making process, whether for power plant siting, load forecasting or energy resource planning, invariably involves a blend of analytical methods and judgement. Management decisions can be improved by the implementation of techniques which permit an increased comprehension of results from analytical models. Even where analytical procedures are not required, decisions can be aided by improving the methods used to examine spatially and temporally variant data. How the use of computer aided planning (CAP) programs and the selection of a predominant data structure, can improve the decision making process is discussed.

French, P.↗