Search NASA⌕ Search

SEARCH · Search NASA

Results for “execution time”

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 1,585 records · Page 88

Geologic Investigations Spurred by Analog Testing at the 7504 Cone-SP Mountain Area of the San Francisco Volcanic Field

The SP Mountain area of the San Francisco Volcanic Field, AZ, has been used as an analog mission development site for NASA since 1998. This area consists of basaltic cinder cones, lava flows and maar craters that have been active since mid-Miocene, with the youngest events occurring within the last 10,000 years. The area has been used because its geologic and topographic resemblance to lunar and Martian terrains provides an ideal venue for testing hardware and science operations practices that might be employed on planetary surfaces, as well as training astronauts in field geology. Analog operations have often led to insights that spurred new scientific investigations. Most recently, an investigation of the 7504 cone was initiated due to perceptions that Apollo-style traverse plans executed during the Desert RATS 2010 mission had characterized the area incorrectly, leading to concerns that the Apollo traverse planning process was scientifically flawed. This investigation revealed a complex history of fissure eruptions of lava and cinders, cinder cone development, a cone-fill-and-spill episode, extensive rheomorphic lava flow initiation and emplacement, and cone sector collapse that led to a final lava flow. This history was not discernible on pre-RATS mission photogeology, although independent analysis of RATS 2010 data and samples develped a "75% complete solution" that validated the pre-RATS mission planning and Apollo traverse planning and execution. The study also pointed out that the development of scientific knowledge with time in a given field area is not linear, but may follow a functional form that rises steeply in the early period of an investigation but flattens out in the later period, asymptotically approaching a theoretical "complete knowledge" point that probably cannot be achieved. This implies that future human missions must be prepared to shift geographic areas of investigation regularly if significant science returns are to be forthcoming.

Eppler, Dean B.↗

Initial Satellite Formation Flight Results from the Magnetospheric Multiscale Mission

This paper will describe the results that have been obtained to date concerning MMS formation flying. The MMS spacecraft spin at a rate of 3.1 RPM, with spin axis roughly aligned with Ecliptic North. Several booms are used to deploy instruments: two 5 m magnetometer booms in the spin plane, two rigid booms of length 12.5 m along the positive and negative spin axes, and four flexible wire booms of length 60 m in the spin plane. Minimizing flexible motion of the wire booms requires that reorientation of the spacecraft spin axis be kept to a minimum: this is limited to attitude maneuvers to counteract the effects of gravity-gradient and apparent solar motion. Orbital maneuvers must therefore be carried out in essentially the nominal science attitude. These burns make use of a set of monopropellant hydrazine thrusters: two (of thrust 4.5 N) along the spin axis in each direction, and eight (of thrust 18 N) in the spin plane; the latter are pulsed at the spin rate to produce a net delta-v. An on-board accelerometer-based controller is used to accurately generate a commanded delta-v. Navigation makes use of a weak-signal GPS-based system: this allows signals to be received even when MMS is flying above the GPS orbits, producing a highly accurate determination of the four MMS orbits. This data is downlinked to the MMS Mission Operations Center (MOC) and used by the MOC Flight Dynamics Operations Area (FDOA) for maneuver design. These commands are then uplinked to the spacecraft and executed autonomously using the controller, with the ground monitoring the burns in real time.

satellite↗

Human Capabilities Assessments for Autonomous Missions: A Multi-Team Research Effort to Reduce Risk in the Human-System Integration Architecture for Future Deep-Space Missions

In future exploration missions beyond low earth-orbit, crew will have to execute complex operations and respond to off-nominal events, without real-time support from Mission Control. It is anticipated that increased reliance on automated systems, including human-centric vehicle and information architecture, will need to be designed to support the crew; increased risk to performance, health, and safety may occur if these are not implemented appropriately. The Human Factors and Behavioral Performance Element (HFBP) in the NASA Human Research Program supports research to characterize and mitigate such human health and performance risks, including the Risk of Adverse Outcome Due to Inadequate Human Systems Integration Architecture (HSIA). The HSIA risk addresses the integration of onboard capability and the crew roles and responsibilities necessary to enable the crew to respond effectively and efficiently in the increasingly autonomous mission operations environment. In 2017, HFBP released the “Human Capabilities Assessments for Autonomous Missions” (HCAAM) research topic to address HSIA related questions. HCAAM is a major NASA research effort that has assembled a multidisciplinary team from seven institutions to work closely with design and engineering efforts on research towards developing and refining human performance standards, guidelines and automation tools. The scientific focus is on quantitative assessment of human capabilities relevant to future deep-space missions during which earth/spacecraft communication is so delayed and intermittent that the crew must be able to function autonomously. The integrated strategy of the HCAAM project characterizes human capabilities and limitations related to potential performance decrements during long duration exploration mission spaceflight as relevant to both routine and complex task performance; defines system characteristics that reduce the likelihood or impact of potential decrements in human performance capabilities; performs integrated assessment of intelligent system responses within the context of an operational environment with relevant NASA tools, systems, and data structures in order to determine positive or negative interactions and validate recommended approaches; and proposes specific updates to existing standards and guidelines for inclusion in NASA handbooks for the design of future spacecraft intelligent systems that provide crew performance assessment/feedback, and to also serve as decision-support aids for the onboard crew (i.e., NASA-STD-3001, and NASA/SP-Human Integration Design Handbook (HIDH)). The scientific research vectors being addressed by the seven HCAAM teams include: - crew task performance (accuracy, efficiency) (crew + automation) - crew performance (accuracy, efficiency) - crew Situation Awareness - procedure design and multi-modal enhancement - concurrent tasking (mixed manual + some level of autonomy) - task handover - crew self-planning and time-lining - task design - trust in automation, real-time calibration - human multi-sensory feedback and guidance - human trust in on-board software-based intelligent assistants - virtual assistants The presentation will highlight plans and progress made in each of these research areas as well as the methods by which surrogate astronaut crews in the NASA JSC HERA spaceflight analog facility will function as human test subjects for all of the HCAAM research projects.

HCAAM VNSCOR↗

NASA Small Spacecraft Technology Program

NASA's Small Spacecraft Technology (SST) program within NASA’s Space Technology Mission Directorate, expands the ability to execute unique missions through rapid development and demonstration of capabilities for small spacecraft applicable to exploration, science and the commercial space sector. Through targeted development and frequent in space testing, the program: Enables execution of missions at much lower cost than previously possible; Substantially reduces the time required for development of spacecraft; Enables new mission architectures through the use of small spacecraft; Expands the reach of small spacecraft to new destinations and challenging new environments; and Enables the augmentation of existing assets and future missions with supporting small spacecraft. An overview the program's technology demonstration missions will be provided.

Roger C Hunter↗

NASA Small Spacecraft Technology (SST) Program - Recent and Upcoming Technology Demonstrations and Development Efforts

The Small Spacecraft Technology (SST) program within NASA’s Space Technology Mission Directorate, expands the ability to execute unique missions through rapid development and demonstration of capabilities for small spacecraft applicable to exploration, science and the commercial space sector. Through targeted development and frequent in space testing, the program: • Enables execution of missions at much lower cost than previously possible • Substantially reduces the time required for development of spacecraft • Enables new mission architectures through the use of small spacecraft • Expands the reach of small spacecraft to new destinations and challenging new environments • Enables the augmentation of existing assets and future missions with supporting small spacecraft. The program achieves its objectives through: • Identification and investment in the development of new subsystem technologies to enhance or expand the capabilities of small spacecraft • Sponsorship of flight demonstrations of new technologies, capabilities and applications for small spacecraft • Promotion of the use of small spacecraft as platforms for testing and demonstrating technologies and capabilities that might have more general applications in larger-scale spacecraft and systems Technologies funded by the program that are key to advancing the utility and capability of small spacecraft were demonstrated in 2022 and 2023. Notable on-orbit demonstrations include the following. • The Cislunar Autonomous Positioning System Technology Operations and Navigation Experiment’s (CAPSTONE) navigation technology that was demonstrated for the first time in 2023 could provide autonomous onboard navigation information for future lunar missions, minimizing or eliminating human-in-the-loop mission operations. • The optical communications technology also demonstrated in 2023 by the TeraByte InfraRed Delivery (TBIRD) payload that launched on Pathfinder Technology Demonstrator-3, achieved 200 gigabit per second (Gbps) throughput on a space-to-ground optical link between a satellite in orbit and Earth, the highest data rate ever achieved by optical communications technology. • The precision laser pointing performance of NASA’s CubeSat Infrared CrossLink A (CLICK) spacecraft’s fine steering mirror control system was successfully demonstrated. This element of the laser communications system will be used to demonstrate two-way crosslink communication in low-Earth orbit by CLICK B/C anticipated to launch in late 2024. Investments in subsystem technology development through funding to university, industry, and other government partners in a number of areas will be discussed. Among others, topic areas include propulsion, autonomous swarm technology, edge computing, and thermal control. Additionally, the status of the CubeSat-alternative platform, DiskSat, strategies for accelerating the demonstration of technology payloads via the Realizing Rapid, Reduced-cost high-Risk Research (R5) project, and the status of recently completed and upcoming on-orbit demonstrations will also be presented.

Roger C Hunter↗

Simple Linux Utility for Resource Management

SLURM is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small computer clusters. As a cluster resource manager, SLURM has three key functions. First, it allocates exclusive and/or non exclusive access to resources (compute nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (normally a parallel job) on the set of allciated nodes. Finally, it arbitrates conflicting requests for resouces by managing a queue of pending work.

Jette, M.↗

Technique for grouping instructions into independent strands

A device compiler and linker is configured to group instructions into different strands for execution by different threads based on the dependence of those instructions on other, long-latency instructions. A thread may execute a strand that includes long-latency instructions, and then hardware resources previously allocated for the execution of that thread may be de-allocated from the thread and re-allocated to another thread. The other thread may then execute another strand while the long-latency instructions are in flight. With this approach, the other thread is not required to wait for the long-latency instructions to complete before acquiring hardware resources and initiating execution of the other strand, thereby eliminating at least a portion of the time that the other thread would otherwise spend waiting.

Mehrara, Mojtaba↗

Validation Testing for Molten Chloride Reactor Experiment Equipment Removal and Disposal Techniques

The Molten Chloride Reactor Experiment (MCRE) will be the first reactor featuring a fast-spectrum molten chloride circulating nuclear fuel system in the world. Planning for equipment removal and disposal (ERD) of MCRE has identified several technology gaps due to the unique environment of this nuclear experiment. Some of the gaps arise from the application of existing disassembly and/or sizing methods to novel material forms or in novel configurations. Others arise from unknown material behavior. This paper summarizes proposed test plans for ERD validation experiments to address these complicated or unknown equipment removal procedures. At the Waste Management Symposia in 2024, the Idaho National Laboratory (INL) MCRE ERD team presented the challenges associated with hosting multiple nuclear experiments in series with only brief transition periods between systems. Such difficulties include higher dose rates, the presence of radioisotopes infrequently encountered in reactor decommissioning and radioactive waste management, lack of intrinsic remote-operations infrastructure in the test bed, space constraints in the test bed, and contamination minimization requirements. To address these challenges, remote or semi-remote technologies are planned to be implemented in a non-hot cell environment with limited space availability. The team also discussed how a systems engineering approach is being used for conceptual development and design of equipment removal systems to address these challenges. For example, to reduce constraints for the removal of more difficult components, non-activated, noncontaminated elements are planned to be taken out first where possible. Still, there are complexities associated with the remaining components. In this work, the operational framework for MCRE ERD was reviewed for technical gaps and open questions, and test plans were drafted to address these areas. The tests plans were written for the following categories: vision systems, pipe cutting, drill/grout/filler, flush salt, and miscellaneous, with the miscellaneous group consisting of tests like techniques for removing bearings and reflector bricks. The test plans explore material, infrastructure, and staffing requirements needed for test execution. The test plans additionally focus on the evaluation of success. Determining the outcome of a test is imperative - as these explorative actions have the potential to rearrange or re-scope planned ERD activities. Success criteria identified thus far include required tool output, required area(s), debris production and mitigation, and repeatability. Test plans are an essential aspect of the systems engineering approach to MCRE ERD. They are used as the beginning steps in defining use cases for the ERD system. Performance of the validation tests is expected to begin in the summer of 2025 and will take approximately 9 to 12 months to complete. Execution of these plans will be expedited by specifying test needs ahead of time, facilitating efficient interactions with any subcontractors tasked with running the requested tests. Evaluating the outcomes of these tests will inform MCRE ERD procedures and timing and will also identify additional technical constraints for the MCRE ERD System. This upfront process optimization effort will help the project save time and resources at the end of the experiment.

21 - SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLAN↗

Time Utility Functions for Modeling and Evaluating Resource Allocations in a Heterogeneous Computing System

This study considers a heterogeneous computing system and corresponding workload being investigated by the Extreme Scale Systems Center (ESSC) at Oak Ridge National Laboratory (ORNL). The ESSC is part of a collaborative effort between the Department of Energy (DOE) and the Department of Defense (DoD) to deliver research, tools, software, and technologies that can be integrated, deployed, and used in both DOE and DoD environments. The heterogeneous system and workload described here are representative of a prototypical computing environment being studied as part of this collaboration. Each task can exhibit a time-varying importance or utility to the overall enterprise. In this system, an arriving task has an associated priority and precedence. The priority is used to describe the importance of a task, and precedence is used to describe how soon the task must be executed. These two metrics are combined to create a utility function curve that indicates how valuable it is for the system to complete a task at any given moment. This research focuses on using time-utility functions to generate a metric that can be used to compare the performance of different resource schedulers in a heterogeneous computing system. The contributions of this paper are: (a) a mathematical model of a heterogeneous computing system where tasks arrive dynamically and need to be assigned based on their priority, precedence, utility characteristic class, and task execution type, (b) the use of priority and precedence to generate time-utility functions that describe the value a task has at any given time, (c) the derivation of a metric based on the total utility gained from completing tasks to measure the performance of the computing environment, and (d) a comparison of the performance of resource allocation heuristics in this environment.

99 GENERAL AND MISCELLANEOUS↗

Understanding data motion in the modern HPC data center

The utilization and performance of storage, compute, and network resources within HPC data centers have been studied extensively, but much less work has gone toward characterizing how these resources are used in conjunction to solve larger scientific challenges. To address this gap, we present our work in characterizing workloads and workflows at a data-center-wide level by examining all data transfers that occurred between storage, compute, and the external network at the National Energy Research Scientific Computing Center over a three-month period in 2019. Using a simple abstract representation of data transfers, we analyze over 100 million transfer logs from Darshan, HPSS user interfaces, and Globus to quantify the load on data paths between compute, storage, and the wide-area network based on transfer direction, user, transfer tool, source, destination, and time. We show that parallel I/O from user jobs, while undeniably important, is only one of several major I/O workloads that occurs throughout the execution of scientific workflows. We also show that this approach can be used to connect anomalous data traffic to specific users and file access patterns, and we construct time-resolved user transfer traces to demonstrate that one can systematically identify coupled data motion for individual workflows.

Lockwood, GK↗

Using a Large Language Model as a Building Block to Generate Usable Validation and Verification Suite for OpenMP

In the HPC area, both hardware and software move quickly. Often new hardware is developed and deployed, the corresponding software stack, including compilers and other tools, are under active development while leading edge software developers are working to port and tune their applications, all at the same time. While the software ecosystem is in flux, one of the key challenges for users is obtaining insight into the state of implementation of key features in the programming languages and models their applications are using – whether they have been implemented, and whether the implementation conforms to the specification, especially for newly implemented features (less tested by widespread use). OpenMP is one of the most prominent shared memory programming models used for on-node programming in HPC. With the shift towards accelerators (such as GPUs and FPGAs) and heterogeneous programming OpenMP features are getting more complex. It is natural to ask whether generative AI approaches, and large language models (LLMs) in particular, can help in producing validation and verification test suites to allow users better and faster insights into the availability and correctness of OpenMP features of interest. In this work, we explore the use of ChatGPT-4 to generate a suite of tests for OpenMP features. We have chosen a set of directives and clauses, a total of 78 combinations, which first appeared in OpenMP 3.0 (released in May 2008) but are also relevant for accelerators. We prompted ChatGPT to generate tests in the C and Fortran languages, for both host (CPU) and device (accelerator). On the Summit super-computer using the GNU implementation, we found that, of the 78 generated tests 67 C tests and 43 Fortran tests compiled successfully and fewer than those executed to completion. On further analysis we show that not all generated tests are valid. We document the process, results, and provide detailed analysis regarding the quality of tests generated. With the aim of providing input to a production quality validation and verification suite, we manually implement the corrections required to make the tests valid according to the current OpenMP specification. We quantify this effort as small, medium, or large, and record the lines of code changed to correct the invalid tests. With the corrected tests we validate recent implementations from HPE, AMD, and GNU on the Frontier supercomputer. Our experiment and subsequent analysis show that although LLMs are capable of producing HPC specific codes, they are limited by their understanding of the deeper semantics and restrictions of programming models such as OpenMP. Unsurprisingly more commonly used features have better support, while some OpenMP 3.0 directives such as sections and tasking are not universally supported on accelerators. We demonstrate that successful compilation and execution to completion are inadequate metrics for evaluating generated code and that, at this time, commodity LLMs require expert intervention for code verification. This points to gaps in the training data that is currently available for HPC. We demonstrate that with "small" effort 37% of generated invalid C tests and 63% of generated invalid Fortran tests could be corrected. This improves productivity of test generation as we circumvent writing from scratch and the common programming errors associated with it.

Pophale, Swaroop [ORNL] (ORCID:0000000185446367)↗

Content and Representation of Information Needed to Support Time-Constrained Problem Solving

NASA’s current mission-operations paradigm originated with Project Mercury and endured with minimum evolution through the Apollo Program, Space Shuttle Program, and ISS missions. At its foundation is a near-complete real-time dependence on a ground team to manage the combined state of the mission, vehicle, and crew. Utilizing many engineers and operators with broad and deep expertise; large, distributed datasets including extensive telemetry; and expansive analytical and computing power, this ground team has served as the safety net for crewed spaceflight missions over the past 60 years. This approach must change to address challenges associated with missions beyond low Earth orbit (BLEO), including infrequent resupply, reduced ability to evacuate, and delayed communications that prohibit real-time operational support. We anticipate that a necessary part of this change will be increased independence for the crew, as roles and responsibilities traditionally performed by ground teams move on board the vehicle. While many risks are associated with Earth-independent operations, one particular concern is ensuring that the crew will have adequate onboard support to perform urgent problem solving when communication with the ground is delayed or intermittent. A key resource that enables the ground team to respond to anomalies quickly and effectively is the extraordinary expertise and experience it possesses. It is comprised of 80+ experts on at any given time, with a combined 600+ years of system-specific experience across 22 unique console disciplines. A small crew will face the unprecedented challenge of independently responding to anomalies that have historically been handled by a team 20 times their size. Another important resource upon which the ground heavily relies to support procedure execution and anomaly response is data. The amount of telemetry data that each flight controller monitors is extensive. In addition, as the ground team works to further assess impacts, trouble shoot, identify workarounds, and oversee procedure execution, it accesses and synthesizes engineering and procedure information, as well as system build, test, and configuration documentation. It is not feasible nor useful to put all these data onboard as crews become more Earth independent. Each member of a small Mars mission small crew will have multiple roles beyond monitoring telemetry and data gathering, and multiple roles within anomaly resolution processes, thereby limiting their capacity for copious amounts of information. Moreover, while access is necessary, it alone is insufficient. Information will need to be compiled, refined, and represented appropriately to support the crew’s reduced attention and expertise. This work seeks to understand the content and representation of information needed to support time-constrained problem solving and decision making by the crew without real-time ground support. To build this understanding, we first surveyed the literature, focusing on how expert problem solvers construct and manipulate their mental models. Next, we interviewed expert problem solvers in spaceflight and analogous domains and surveyed industry solutions for data presentation. Finally, we analyzed current spaceflight operations by investigating flight controller anomaly resolution processes during ISS training simulations and real operational events. These methods led to creating a problem-solving framework that details common themes and features of attending to, assessing, analyzing, and acting on problems in complex, time-constrained domains. Using this framework and the results of our analysis, we identified conceptual data representations needed for crew-led problem-solving. Preliminary onboard user interface concepts to meet identified needs will be presented.

anomaly response↗

Economic consequences of improved temperature forecasts: An experiment with the Florida citrus growers (control group results). Executive summary

A demonstration experiment is being planned to show that frost and freeze prediction improvements are possible utilizing timely Synchronous Meteorological Satellite temperature measurements and that this information can affect Florida citrus grower operations and decisions so as to significantly reduce the cost for frost and freeze protection and crop losses. The design and implementation of the first phase of an economic experiment which will monitor citrus growers decisions, actions, costs and losses, and meteorological forecasts and actual weather events was carried out. The economic experiment was designed to measure the change in annual protection costs and crop losses which are the direct result of improved temperature forecasts. To estimate the benefits that may result from improved temperature forecasting capability, control and test groups were established with effective separation being accomplished temporally. The control group, utilizing current forecasting capability, was observed during the 1976-77 frost season and the results are reported. A brief overview is given of the economic experiment, the results obtained to date, and the work which still remains to be done.

Source record↗

Influence of UAS Pilot Communication and Execution Delay on Controller's Acceptability Ratings of UAS-ATC Interactions

Successful integration of UAS in the NAS will require that UAS interactions with the air traffic management system be similar to interactions between manned aircraft and air traffic management. For example, UAS response times to air traffic controller (ATCo) clearances should be equivalent to those that are currently found to be acceptable with manned aircraft. Prior studies have examined communication delays with manned aircraft. Unfortunately, there is no analogous body of research for UAS. The goal of the present study was to determine how UAS pilot communication and execution delays affect ATCos' acceptability ratings of UAS pilot responses when the UAS is operating in the NAS. Eight radar-certified controllers managed traffic in a modified ZLA sector with one UAS flying in it. In separate scenarios, the UAS pilot verbal communication and execution delays were either short (1.5 s) or long (5 s) and either constant or variable. The ATCo acceptability of UAS pilot communication and execution delays were measured subjectively via post trial ratings. UAS verbal pilot communication delay, were rated as acceptable 92% of the time when the delay was short. This acceptability level decreased to 64% when the delay was long. UAS pilot execution delay had less of an influence on ATCo acceptability ratings in the present stimulation. Implications of these findings for UAS in the NAS integration are discussed.

communication↗

iHarmonizer: improving the disk efficiency of I/O-intensive multithreaded codes

Challenged by serious power and thermal constraints, and limited by available instruction-level parallelism, processor designs have evolved to multi-core architectures. These architectures, many augmented with native simultaneous multithreading, are driving software developers to use multithreaded programs to exploit thread-level parallelism. While multithreading is well-known to introduce concerns of data dependency and CPU load balance, less known is that the uncertainty of relative progress of thread execution can cause patterns of I/O requests, issued by different threads, to be effectively random and so significantly degrade hard-disk efficiency. This effect can severely offset the performance gains from parallel execution, especially for I/O-intensive programs. Retaining the benefits of multithreading while not reducing I/O efficiency is an urgent and challenging problem. We propose a user-level scheme, iHarmonizer, to streamline the servicing of I/O requests from multiple threads in OpenMP programs. Specifically, we use the compiler to insert code into OpenMP programs so that data usage can be transmitted at run time to a supporting run-time library; this library in turn prefetches data in a disk-friendly way and coordinates threads execution according to the availability of their requested data. Transparently to the programmer, iHarmonizer makes a multithreaded program I/O efficient while maintaining the benefits of parallelism. Our experiments show that iHarmonizer can significantly speed up the execution of a representative set of I/O-intensive scientific benchmarks.

97 MATHEMATICS AND COMPUTING↗

Reusable Reentry Satellite (RRS): Telemetry, Tracking, and Command (TT/C) Coverage Tradeoff Study

The Reusable Reentry Satellite (RRS) Telemetry, Tracking & Command (TT&C) Coverage Tradeoff Study described herein was performed during Part 1 of the RRS Phase B contract. This report is one of several that describes the results of various trade studies performed to arrive at a recommended design for the RRS satellite system. The overall RRS Phase B Study objective is to design a relatively inexpensive satellite to access space for extended periods of time, with eventual recovery of experiments on Earth. The RRS will be capable of: (1) being launched by a variety of expendable launch vehicles; (2) operating in low earth orbit as a free flying unmanned laboratory; and (3) executing an independent atmospheric reentry and soft landing. The RRS will be designed to be refurbished and reused up to three times a year for a period of 10 years. The expected principal use for such a system is research on the effects of variable gravity (0 to 1.5 g) and radiation on small animals, plants, lower life forms, tissue samples, and materials processes. This Summary Report provides a description of the RRS Telemetry, Tracking & Command Analysis performed to study the ground station coverage available to meet RRS requirements. Concepts were considered that used off-the-shelf technology, had generous margins of capability, and high reliability, were easily maintained, cost effective, and were compatible with existing support networks. From this study, a recommended RRS TT&C configuration will be developed.

Source record↗

System architecture for asynchronous multi-processor robotic control system

The architecture for the Modular Telerobot Task Execution System (MOTES) as implemented in the Supervisory Telerobotics (STELER) Laboratory is described. MOTES is the software component of the remote site of a local-remote telerobotic system which is being developed for NASA for space applications, in particular Space Station Freedom applications. The system is being developed to provide control and supervised autonomous control to support both space based operation and ground-remote control with time delay. The local-remote architecture places task planning responsibilities at the local site and task execution responsibilities at the remote site. This separation allows the remote site to be designed to optimize task execution capability within a limited computational environment such as is expected in flight systems. The local site task planning system could be placed on the ground where few computational limitations are expected. MOTES is written in the Ada programming language for a multiprocessor environment.

Steele, Robert D.↗

The OpenSE Cookbook: A Practical, Recipe Based Collection of Patterns, Procedures, and Best Practices for Executable Systems Engineering for the Thirty Meter Telescope

The OpenSE Cookbook is an open-sourced collection of patterns, procedures, and best practices targeted for systems engineers who seek guidance on applying model-based and executable systems engineering (MBSE) using SysML. Its content has emerged from the system level modeling effort on the European Framework Program 6 (FP6) and the Thirty Meter Telescope (TMT). The TMT MBSE approach applied the Executable Systems Engineering Method (ESEM) and the open-source Engineering Environment (OpenMBEE) to specify, analyze, and verify requirements of TMT’s Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS). In these applications, implicit dependencies are made explicit in a formal model through the use of ESEM, OpenMBEE, and SysML modeling constructs. The value proposition for applying this MBSE approach was to establish precise requirements and fine-grained traceability to system designs, and to verify key requirements beginning early in development. The integration of ESEM and the OpenMBEE tooling infrastructure (providing linked-data and web-operability) is a significant added value for the MBSE approach. The APS is responsible for the overall pre-adaptive optics wavefront quality, using starlight to measure wavefront errors and align the TMT optics. In the formally integrated and executable SysML model, simulations are performed to analyze the impact of changed requirements and verify specified constraints for various operational scenarios. The APS team used several modeling patterns to capture information such as the requirements, the operational scenarios, involved subsystems and their interaction points, the estimated or required time durations, and the mass and power consumption. Adaptive optics systems are designed to sense real-time atmospheric turbulence and correct the telescope’s optical beam to remove its effect. The system model for the adaptive optics operational modes was developed to capture sequence behaviors and operational scenarios to run Monte-Carlo simulations for verifying acquisition time, observing efficiency, and operational behavior requirements. The model is particularly useful for investigating the effect of parallelization, identifying interface issues, and re-ordering sequence acquisition tasks. A former version of the Cookbook (which is now updated to MBSE challenges, goals, and lessons learned) included modeling guidelines and conventions for all system aspects, hierarchy levels, and views, which were developed during for the Active Phasing Experiment (APE), an opto-mechatronical system technology demonstrator for the Extremely Large Telescope (ELT). The Cookbook utilizes the above mentioned system models as real-world case-studies to demonstrate and document the applications of the recipes, providing also instructional examples and addressing the available tooling support. The Cookbook is accompanied by a number of SysML models and aodel libraries which facilitate model authoring and maintenance. The Cookbook covers the different aspects of Systems Engineering such as management of Requirements, Design (behavior and structure), Interfaces, Interdisciplinary Integration, Analysis, Trade Studies, and Technical Resources. This paper presents the background, motivation, architecture, and highlights some key content of the Cookbook. For example, interface management, error budget management, requirements verification, Monte Carlo driven analysis, and timing analysis of operational scenarios. The paper discusses how the capabilities of OpenMBEE contributed significantly to the adoption of executable systems engineering.

Brower, Eric↗