Search NASA⌕ Search

SEARCH · Search NASA

Results for “Adaptive Scheduling”

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 343 records · Page 19

FLYING SERVING: On-the-Fly Parallelism Switching for Large Language Model Serving

Production LLM serving must simultaneously deliver high throughput, low latency, and sufficient context capacity under non-stationary traffic and mixed request requirements. Data parallelism (DP) maximizes throughput by running independent replicas, while tensor parallelism (TP) reduces per-request latency and pools memory for long-context inference. However, existing serving stacks typically commit to a static parallelism configuration at deployment; adapting to bursts, priorities, or long-context requests is often disruptive and slow. We present Flying Serving, a vLLM-based system that enables online DP-TP switching without restarting engine workers. Flying Serving makes reconfiguration practical by virtualizing the state that would otherwise force data movement: (i) a zero-copy Model Weights Manager that exposes TP shard views on demand, (ii) a KV Cache Adaptor that preserves request KV state across DP/TP layouts, (iii) an eagerly initialized Communicator Pool to amortize collective setup, and (iv) a deadlock-free scheduler that coordinates safe transitions under execution skew. Across three popular LLMs and realistic serving scenarios, Flying Serving improves performance by up to 4.79 × under high load and 3.47 × under low load while supporting latency- and memory-driven requests.

Gao, Shouwei [ORNL]↗

Autonomous Satellite Command and Control through the World Wide Web: Phase 3

NASA's New Millenium Program (NMP) has identified a variety of revolutionary technologies that will support orders of magnitude improvements in the capabilities of spacecraft missions. This program's Autonomy team has focused on science and engineering automation technologies. In doing so, it has established a clear development roadmap specifying the experiments and demonstrations required to mature these technologies. The primary developmental thrusts of this roadmap are in the areas of remote agents, PI/operator interface, planning/scheduling fault management, and smart execution architectures. Phases 1 and 2 of the ASSET Project (previously known as the WebSat project) have focused on establishing World Wide Web-based commanding and telemetry services as an advanced means of interfacing a spacecraft system with the PI and operators. Current automated capabilities include Web-based command submission, limited contact scheduling, command list generation and transfer to the ground station, spacecraft support for demonstrations experiments, data transfer from the ground station back to the ASSET system, data archiving, and Web-based telemetry distribution. Phase 2 was finished in December 1996. During January-December 1997 work was commenced on Phase 3 of the ASSET Project. Phase 3 is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer; (2) Support prioritized handling of multiple PIs as well as associated payload experimenters; (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft; (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware; (5) Implement a beacon monitoring test; (6) Implement an experimental blackboard controller for space system management; (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals is examined in the next section. Significant sections of this report were also published as a conference paper.

Cantwell, Brian↗

Turnaround operations analysis for OTV. Volume 2: Detailed technical report

The objectives and accomplishments were to adapt and apply the newly created database of Shuttle/Centaur ground operations. Previously defined turnaround operations analyses were to be updated for ground-based OTVs (GBOTVs) and space-based OTVs (SBOTVs), design requirements identified for both OTV and Space Station accommodations hardware, turnaround operations costs estimated, and a technology development plan generated to develop the required capabilities. Technical and programmatic data were provided for NASA pertinent to OTV round and space operations requirements, turnaround operations, task descriptions, timelines and manpower requirements, OTV modular design and booster and Space Station interface requirements. SBOTV accommodations development schedule, cost and turnaround operations requirements, and a technology development plan for ground and space operations and space-based accommodations facilities and support equipment. Significant conclusion are discussed.

Source record↗

Human factors issues in performing life science experiments in a 0-G environment

An overview of the environmental conditions within the Spacelab and the planned Space Station Freedom is presented. How this environment causes specific Human Factors problems and the nature of design solutions are described. The impact of these problems and solutions on the performance of life science activities onboard Spacelab (SL) and Space Station Freedom (SSF) is discussed. The first area highlighted is contamination. The permanence of SSF in contrast to the two-week mission of SL has significant impacts on crew and specimen protection requirements and, thus, resource utilization. These requirements, in turn impose restrictions on working volumes, scheduling, training, and scope of experimental procedures. A second area is microgravity. This means that all specimens, materials, and apparatus must be restrained and carefully controlled. Because so much of the scientific activity must occur within restricted enclosures (gloveboxes), the provisions for restraint and control are made more complex. The third topic is crewmember biomechanics and the problems of movement and task performance in microgravity. In addition to the need to stabilize the body for the performance of tasks, performance of very sensitive tasks such as dissection is difficult. The issue of space sickness and adaption is considered in this context.

Gonzalez, Wayne↗

Neurolab: Final Report for the Ames Research Center Payload

Neurolab, the final Spacelab mission, launched on STS-90 on April 17, 1998, was dedicated to studying the nervous system. NASA cooperated with domestic and international partners to conduct the mission. ARC's (Ames Research Center's) Payload included 15 experiments designed to study the adaptation and development of the nervous system in microgravity. The payload had the largest number of Principal and Co-Investigators, largest complement of habitats and experiment unique equipment flown to date, and most diverse distribution of live specimens ever undertaken by ARC, including rodents, toadfish, swordtail fish, water snails, hornweed and crickets To facilitate tissue sharing and optimization of science objectives, investigators were grouped into four science discipline teams: Neuronal Plasticity, Mammalian Development, Aquatic, and Neurobiology. Several payload development challenges were experienced and required an extraordinary effort, by all involved, to meet the launch schedule. With respect to hardware and the total amount of recovered science, Neurolab was regarded as an overall success. However, a high mortality rate in one rodent group and several hardware anomalies occurred inflight that warranted postflight investigations. Hardware, science, and operations lessons were learned that should be taken into consideration by payload teams developing payloads for future Shuttle missions and the International Space Station.

Maese, A. Christopher↗

Initial Performance Evaluation of Flight Path Management Onboard Automation

Significant developments in automation are necessary to achieve safe and efficient operations in advanced aerial mobility related concepts. Urban Air Mobility (UAM) is rapidly growing, emerging field that poses a challenging use case with a tighter scale of operations compared to the traditional commercial transport paradigm. A large part of the challenge is the uncharted territory; as of this paper, no set of operational standards or guidelines for UAM operations have been established and automated en route operations for UAM level 4 (UML-4) have not been studied. Flight Path Management (FPM) automation provides a set of capabilities that are critical toward enabling airborne vehicles to achieve mission success while maintaining operational safety. An initial performance evaluation of FPM automation was conducted using a UAM-adapted version of the Autonomous Operations Planner (AOP), an onboard trajectory management capability developed over years of research targeting commercial transport operations, as its reference implementation. This paper describes the evaluation, including the approach and methodology for simulating FPM automation in UML-4, key results, future work, and conclusions.

flight path management↗

A Process for Technology Prioritization in a Competitive Environment

This slide presentation reviews NASA's process for prioritizing technology requirements where there is a competitive environment. The In-Space Propulsion Technology (ISPT) project is used to exemplify the process. The ISPT project focuses on the mid level Technology Readiness Level (TRL) for development. These are TRL's 4 through 6, (i.e. Technology Development and Technology Demonstration. The objective of the planning activity is to identify the current most likely date each technology is needed and create ISPT technology development schedules based on these dates. There is a minimum of 4 years between flight and pacing mission. The ISPT Project needed to identify the "pacing mission" for each technology in order to provide funding for each area. Graphic representations show the development of the process. A matrix shows which missions are currently receiving pull from the both the Solar System Exploration and the Sun-Solar System Connection Roadmaps. The timeframes of the pacing missions technologies are shown for various types of propulsion. A pacing mission that was in the near future serves to increase the priority for funding. Adaptations were made when budget reductions precluded the total implementation of the plan.

Stephens, Karen↗

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗

Engineering Antifragile Systems: A Change In Design Philosophy

While technology has made astounding advances in the last century, problems are confronting the engineering community that must be solved. Cost and schedule of producing large systems are increasing at an unsustainable rate and these systems often do not perform as intended. New systems are required that may not be achieved by current methods. To solve these problems, NASA is working to infuse concepts from Complexity Science into the engineering process. Some of these problems may be solved by a change in design philosophy. Instead of designing systems to meet known requirements that will always lead to fragile systems at some degree, systems should be designed wherever possible to be antifragile: designing cognitive cyberphysical systems that can learn from their experience, adapt to unforeseen events they face in their environment, and grow stronger in the face of adversity. Several examples are presented of on ongoing research efforts to employ this philosophy.

Jones, Kennie H.↗

MUSTANG Applications

Reducing nonrecurring cost and shortening the build schedule for space qualified avionics has been a recurring theme in Space Industry. The NASA Goddard Space Flight Center has leverage its heritage flight qualified design and developed a portfolio of modular avionics comprised of 22 different board designs in a form factor named MUSTANG (Modular Unified Space Technology Avionics for Next Generation) that can be utilized in a variety flight applications. Since the design has no backplane, the modules can be mixed and match to meet the needed requirements. The MUSTANG form factor is sized to fill the void between 3U and 6U form factor and with flexibility to adapting the design without relaying out the boards.

Space↗

High-Rate Delay Tolerant Networking (HDTN) User Guide Version 1.0

Delay Tolerant Networking (DTN) has been identified as a key technology to enable and facilitate the development and growth of future space networks. Classically, space communications networks are collections of disparate links that are manually managed either point-to-point or use space relays. The accelerating accessibility of space enables a new scaling of space nodes, yet both the manual management of configurations and scheduling and the lack of structure connecting links precisely prohibit scaling. This challenge gives rise to newer and larger classes of communications needs that are met by DTN, which must overcome the disconnection, disruption, latency, and mobility featured in space communications systems. DTN joins the underlying links as an overlay, and can be made to communicate over any protocol stack. The core actions of DTN are store, carry, and forward, where data are stored instead of dropped if there is no immediately available outduct. It does this by taking the DTN unit of data, bundles, and providing necessary layers to adapt these bundles to the underlying transport protocols of choice; these are called convergence layers. DTN's Bundle Protocol (BP) can then be used on top of terrestrial protocol stacks, such as TCP/IP, as well as protocols for space, such as LTP/AOS, all in the same network. For emphasis it is noted that bundles can be of essentially any size, and hence this convergence to lower layers of choice is necessary. Existing DTN implementations have operated in constrained environments with limited resources, resulting in low data speeds. However, as various technologies have advanced, data transfer rates and efficiency have advanced, which has pushed the need for a DTN implementation for ground systems and for spacecraft that is performance-oriented in order to not impose an unnecessary bottleneck. High-rate Delay Tolerant Networking (HDTN) takes advantage of modern hardware platforms to substantially reduce latency and improve throughput compared to today’s DTN operations. The HDTN implementation maintains interoperability with existing deployments of DTN that conform to IETF RFCs 4838, 5050, and 9171. At the same time, HDTN defines a new data format better suited to higher-rate operation. It defines and adopts a massively parallel pipelined and message-oriented architecture, allowing the system to scale gracefully as its resources increase. HDTN’s architecture also supports hooks to replace various processing pipeline elements with specialized hardware accelerators. This offers improved Size, Weight, and Power (SWaP) characteristics while reducing development complexity and cost.

Delay Tolerant Networking↗

High-Rate Delay Tolerant Networking (HDTN) User Guide Version 1.3.0

Delay Tolerant Networking (DTN) has been identified as a key technology to enable and facilitate the development and growth of future space networks. Classically, space communications networks are collections of disparate links that are manually managed either point-to-point or use space relays. The accelerating accessibility of space enables a new scaling of space nodes, yet both the manual management of configurations and scheduling and the lack of structure connecting links precisely prohibit scaling. This challenge gives rise to newer and larger classes of communications needs that are met by DTN, which must overcome the disconnection, disruption, latency, and mobility featured in space communications systems. DTN joins the underlying links as an overlay, and can be made to communicate over any protocol stack. The core actions of DTN are store, carry, and forward, where data are stored instead of dropped if there is no immediately available outduct. It does this by taking the DTN unit of data, bundles, and providing necessary layers to adapt these bundles to the underlying transport protocols of choice; these are called convergence layers. DTN's Bundle Protocol (BP) can then be used on top of terrestrial protocol stacks, such as TCP/IP, as well as protocols for space, such as LTP/AOS, all in the same network. For emphasis it is noted that bundles can be of essentially any size, and hence this convergence to lower layers of choice is necessary. Existing DTN implementations have operated in constrained environments with limited resources, resulting in low data speeds. However, as various technologies have advanced, data transfer rates and efficiency have advanced, which has pushed the need for a DTN implementation for ground systems and for spacecraft that is performance-oriented in order to not impose an unnecessary bottleneck. High-rate Delay Tolerant Networking (HDTN) takes advantage of modern hardware platforms to substantially reduce latency and improve throughput compared to today’s DTN operations. The HDTN implementation maintains interoperability with existing deployments of DTN that conform to IETF RFCs 4838, 5050, and 9171. At the same time, HDTN defines a new data format better suited to higher-rate operation. It defines and adopts a massively parallel pipelined and message-oriented architecture, allowing the system to scale gracefully as its resources increase. HDTN’s architecture also supports hooks to replace various processing pipeline elements with specialized hardware accelerators. This offers improved Size, Weight, and Power (SWaP) characteristics while reducing development complexity and cost.

Delay Tolerant Networking↗

Interference Mitigation Using Cyclic Autocorrelation and Multi-Objective Optimization

Radio frequency interference on space-to-ground communications links can degrade performance and disrupt the transfer of critical data. These interference events become increasingly likely as more users enter the spectrum, due in part to shared spectrum allocations and scheduling conflicts. If this interference could be detected and mitigated by an automated system, then link performance and reliability in these scenarios could be improved. This report describes the implementation and evaluation of an automated interference mitigation system that provides this functionality. The system uses Cyclic Autocorrelation (CAC) signal processing techniques to monitor the spectrum and detect interfering signals, and it applies a multi-objective optimization approach to mitigate interference by changing link parameters to continuously optimize the link. The implementation was evaluated to characterize its signal detection capabilities for various link qualities and to compare its link management performance to Adaptive Coding and Modulation (ACM) and Constant Coding and Modulation (CCM) when in the presence of randomized interference. In the latter evaluation, the interference mitigation system achieved the highest average throughput in each tested scenario. With these results, the proposed solution provides the groundwork for further automated link management capabilities and continued investigation into interference mitigation approaches.

Interference mitigation↗

Initial Performance Evaluation of Flight Path Management Onboard Automation

Significant developments in automation are necessary to achieve safe and efficient operations in advanced aerial mobility related concepts. Urban Air Mobility (UAM) is rapidly growing, emerging field that poses a challenging use case with a tighter scale of operations compared to the traditional commercial transport paradigm. A large part of the challenge is the uncharted territory; as of this paper, no set of operational standards or guidelines for UAM operations have been established and automated en route operations for UAM level 4 (UML-4) have not been studied. Flight Path Management (FPM) automation provides a set of capabilities that are critical toward enabling airborne vehicles to achieve mission success while maintaining operational safety. An initial performance evaluation of FPM automation was conducted using a UAM-adapted version of the Autonomous Operations Planner (AOP), an onboard trajectory management capability developed over years of research targeting commercial transport operations, as its reference implementation. This paper describes the evaluation, including the approach and methodology for simulating FPM automation in UML-4, key results, future work, and conclusions.

flight path management↗

NASA: Biomedical applications team

The status of projects involving the adaptation of NASA technologies for medical purposes is reviewed. Devices for the measurement of joint deformation of arthritic hands, the development of an artificial pancreas, provision of an auditory signal to avert epileptic seizures, are described along with the control of medication levels, a compressed air tank to supply power for field dentistry, and an electroencephalogram monitor. The use of the Lixiscope as a portable fluoroscope, thermal laminates for hand and foot warmers for patients with Raynaud's syndrome, and the use of absorptive coatings for instruments for controlling medication levels are described. The applicability of occupation health and safety practices to industry, computerized patient scheduling, impregnation of the common facial tissue with an agent for killing respiratory viruses, commercial applications of anthropometric data, and multispectral image analysis of the skin as a diagnostic tool are reviewed.

Source record↗

An assessment of technology alternatives for telecommunications and information management for the space exploration initiative

On the 20th anniversary of the Apollo 11 lunar landing, President Bush set forth ambitious goals for expanding human presence in the solar system. The Space Exploration Initiative (SEI) addresses these goals beginning with Space Station Freedom, followed by a permanent return to the Moon, and a manned mission to Mars. A well designed, adaptive Telecommunications, Navigation, and Information Management (TNIM) infrastructure is vital to the success of these missions. Utilizing initial projections of user requirements, a team under the direction of NASA's Office of Space Operations developed overall architectures and point designs to implement the TNIM functions for the Lunar and Mars mission scenarios. Based on these designs, an assessment of technology alternatives for the telecommunications and information management functions was performed. This technology assessment identifies technology developments necessary to meet the telecommunications and information management system requirements for SEI. Technology requirements, technology needs and alternatives, the present level of technology readiness in each area, and a schedule for development are presented.

Ponchak, Denise S.↗

Panel to review EOSDIS plans

Formed in Jan. 1992, the Panel to Review EOSDIS Plans was charged with advising NASA on its plans for developing the Earth Observing System (EOS) Data and Information System (EOSDIS). Specifically, the panel was asked to do the following: assess the validity of the engineering and technical underpinnings of the EOSDIS; assess its potential value to scientific users; suggest how technical risk can be minimized; and assess whether current plans are sufficiently resilient to be adaptable to changing technology and requirements such as budget environments, data volumes, new users, and new databases. The panel completed an interim report (Addendum A) and transmitted it to NASA and other interested parties in the government on 9 Apr. 1992. Because of a delay in NASA's plans to select the contractor for EOSDIS, the panel was not able to complete its review of the program according to the original government request. With the issuance of a letter report (Addendum B) on 28 Sep. 1992, the panel became inactive until such time as NASA could release the details of the contractor's proposed architecture, schedule, and costs for developing EOSDIS. In early 1993, NASA awarded the contract for the EOSDIS Core System (ECS). On 20 Apr. 1993, NASA asked the panel to reconvene to do the following: ( 1) complete its review of NASA's approach to the EOSDIS architecture and implementation; (2) appraise NASA's responses to the panel's previous recommendations; and (3) review the planning for EOSDIS in the context of NASA's role in the Global Change Data and Information System (GCDIS) implementation plan. To respond to the NASA charge, the panel met three times in 1993 including sessions with NASA officials and the EOSDIS contractor. In addition, several of the panel members visited individual Distributed Active Archive Centers (DAAC's) to obtain additional views of EOSDIS. The panel has now obtained substantial information on the EOSDIS budget, contractor work program, and current baseline architecture that was not previously available, due to procurement restrictions. This report presents the panel's findings and recommendations based on this additional information.

Source record↗

Development of an Actuator for Ambient to Cryo Application

During the qualification campaign of the NIRSpec Instrument Mechanism, the actuator could not achieve the expected life time which was extended during the development phase. The initial design could not be adapted to the requested number of revolutions during that phase. Consequently the actuator needed to be modified such that the function of the mechanism would not be endangered and thus the overall function of the NIRSpec instrument. The modification included the change of the overall actuator design - internal dimensions, tolerances, materials, lubrication and assembly process - while keeping the interface to the mechanism, mass, and function. The lessons learned from the inspection of the failed actuator have been implemented in order to ensure the development and qualification success. The initially available time for this activity was in the range of 6 months to meet the overall program schedule.

Menzel, Karen↗