Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Offloading”

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 91 records · Page 5

A Multi-Objective Approach for Optimizing Edge-Based Resource Allocation Using TOPSIS

Existing approaches for allocating resources on edge environments are inefficient and lack the support of heterogeneous edge devices, which in turn fail to optimize the dependency on cloud infrastructures or datacenters. To this extent, we propose in this paper OpERA, a multi-layered edge-based resource allocation optimization framework that supports heterogeneous and seamless execution of offloadable tasks across edge, fog, and cloud computing layers and architectures. By capturing offloadable task requirements, OpERA is capable of identifying suitable resources within nearby edge or fog layers, thus optimizing the execution process. Throughout the paper, we present results which show the effectiveness of our proposed optimization strategy in terms of reducing costs, minimizing energy consumption, and promoting other residual gains in terms of processing computations, network bandwidth, and task execution time. We also demonstrate that by optimizing resource allocation in computation offloading, it is then possible to increase the likelihood of successful task offloading, particularly for computationally intensive tasks that are becoming integral as part of many IoT applications such robotic surgery, autonomous driving, smart city monitoring device grids, and deep learning tasks. The evaluation of our OpERA optimization algorithm reveals that the TOPSIS MCDM technique effectively identifies optimal compute resources for processing offloadable tasks, with a 96% success rate. Moreover, the results from our experiments with a diverse range of use cases show that our OpERA optimization strategy can effectively reduce energy consumption by up to 88%, and operational costs by 76%, by identifying relevant compute resources.

97 MATHEMATICS AND COMPUTING↗

Robotics

Lunar robotic functions include: 1. Transport of crew and payloads on the surface of the moon; 2. Offloading payloads from a lunar lander; 3. Handling the deployment of surface systems; with 4. Human commanding of these functions from inside a lunar vehicle, habitat, or extravehicular (space walk), with Earth-based supervision. The systems that will perform these functions may not look like robots from science fiction. In fact, robotic functions may be automated trucks, cranes and winches. Use of this equipment prior to the crew s arrival or in the potentially long periods without crews on the surface, will require that these systems be computer controlled machines. The public release of NASA's Exploration plans at the 2nd Space Exploration Conference (Houston, December 2006) included a lunar outpost with as many as four unique mobility chassis designs. The sequence of lander offloading tasks involved as many as ten payloads, each with a unique set of geometry, mass and interface requirements. This plan was refined during a second phase study concluded in August 2007. Among the many improvements to the exploration plan were a reduction in the number of unique mobility chassis designs and a reduction in unique payload specifications. As the lunar surface system payloads have matured, so have the mobility and offloading functional requirements. While the architecture work continues, the community can expect to see functional requirements in the areas of surface mobility, surface handling, and human-systems interaction as follows: Surface Mobility 1. Transport crew on the lunar surface, accelerating construction tasks, expanding the crew s sphere of influence for scientific exploration, and providing a rapid return to an ascent module in an emergency. The crew transport can be with an un-pressurized rover, a small pressurized rover, or a larger mobile habitat. 2. Transport Extra-Vehicular Activity (EVA) equipment and construction payloads. 3. Transport habitats and power modules over long distances, pre-positioning them for the arrival of crew on a subsequent lander. Surface Handling 1. Offload surface system payloads from the lander, breaking launch restraints and power/data connections. Payloads may be offloaded to a wheeled vehicle for transport. 2. Deploy payloads from a wheeled vehicle at a field site, placing the payloads in their final use site on the ground or mating them with existing surface systems. 3. Support regolith collection, site preparation, berm construction, or other civil engineering tasks using tools and implements attached to rovers. Human-Systems Interaction 1. Provide a safe command and control interface for suited EVA to ride on and drive the vehicles, making sure that the systems are also safe for working near dismounted crew. 2. Provide an effective control system for IV crew to tele-operate vehicles, cranes and other equipment from inside the surface habitats with evolving independence from Earth. .. Provide a supervisory system that allows machines to be commanded from the ground, working across the Earth-Lunar time delays on the order of 5-10 seconds (round trip) to support operations when crew are not resident on the surface. Technology Development Needs 1. Surface vehicles that can dock, align and mate with outpost equipment such as landers, habitats and fluid/power interfaces. 2. Long life motors, drive trains, seals, motor electronics, sensors, processors, cable harnesses, and dash board displays. 3. Active suspension control, localization, high speed obstacle avoidance, and safety systems for operating near dismounted crew. 4. High specific energy and specific power batteries that are safe, rechargeable, and long lived.

Ambrose, Robert O.↗

Lessons Learned from Performance Testing of Humans in Spacesuits in Simulated Reduced Gravity

Introduction: The overarching objective of the Integrated Suit Test (IST) series is to evaluate suited human performance using reduced-gravity analogs and learn what aspects of an EVA suit system affect human performance. For this objective to be successfully achieved, the testing methodology should be valid and reproducible, and the partial-gravity simulations must be as accurate and realistic as possible. Objectives: To highlight some of the key lessons learned about partial-gravity analogs and testing methodology, and to suggest considerations for optimizing the effectiveness and quality of results of future tests. Methods: Performance testing of suited and unsuited subjects was undertaken in different reduced-gravity analogs including the Space Vehicle Mockup Facility s Partial Gravity Simulator (POGO), parabolic flight on the C-9 aircraft, underwater environments including NASA s Extreme Environment Mission Operations (NEEMO) and the Neutral Buoyancy Lab (NBL), and in field analogs including Desert Research and Technology Studies (RATS), the Haughton Mars Project (HMP), and the JSC Rock Pile. Subjects performed level walking, incline/decline walking, running, shoveling, picking up and transferring rocks, kneeling/standing, and task boards. Lessons Learned Analogs: No single analog will properly simulate all aspects of the true partial-gravity environment. The POGO is an ideal environment from the standpoint that there are no time limits or significant volumetric constraints, but it does have several limitations. It allows only 2 translational degrees of freedom (DOF) and applies true partial-gravity offload only through the subject s center of gravity (CG). Also, when a subject is doing non-stationary tasks, significant overhead inertia from the lift column seems to have a negative impact on performance. Parabolic flight allows full translational and rotational DOF and applies offload to all parts of the body, but the simulation lasts less than 30 seconds. When this is coupled with the volumetric constraints of the plane, both task selection and data collection options are significantly limited. The underwater environments also allow all 6 DOF and allow off-loading to be applied throughout the body, but the data collection capabilities are limited to little more than subjective ratings. In addition, water drag negatively affects performance of tasks requiring dynamic motion. Field analogs provide the ability to simulate lunar terrain and more realistic mission-like objectives, but all of them operate at 1-g, so suited human performance testing generally must utilize a reduced-mass or "mockup" suit, depending on study objectives. In general, the ground-based overhead-suspension partial-gravity analogs like POGO allow the most diverse data collection methods possible while still simulating partial gravity. However, as currently designed, the POGO has significant limitations. Design of the Active Response Gravity Offload System (ARGOS) has begun and is focusing on adding full x,y,z translational DOF, improved offload accuracy, increased lift capacity, and active control of the x and y axes to minimize offload system inertia. Additionally, a new gimbal is being designed to reduce mass and inertia and to be able to work with different suits, as the current gimbal only supports suited testing with the Mark III Technology Demonstrator Suit (MKIII).

Norcross, Jason R.↗

Human Performance in Simulated Reduced Gravity Environments

NASA is currently designing a new space suit capable of working in deep space and on Mars. Designing a suit is very difficult and often requires trade‐offs between performance, cost, mass, and system complexity. Our current understanding of human performance in reduced gravity in a planetary environment (the moon or Mars) is limited to lunar observations, studies from the Apollo program, and recent suit tests conducted at JSC using reduced gravity simulators. This study will look at our most recent reduced gravity simulations performed on the new Active Response Gravity Offload System (ARGOS) compared to the C‐9 reduced gravity plane. Methods: Subjects ambulated in reduced gravity analogs to obtain a baseline for human performance. Subjects were tested in lunar gravity (1.6 m/sq s) and Earth gravity (9.8 m/sq s) in shirt‐sleeves. Subjects ambulated over ground at prescribed speeds on the ARGOS, but ambulated at a self‐selected speed on the C‐9 due to time limitations. Subjects on the ARGOS were given over 3 minutes to acclimate to the different conditions before data was collected. Nine healthy subjects were tested in the ARGOS (6 males, 3 females, 79.5 +/- 15.7 kg), while six subjects were tested on the C‐9 (6 males, 78.8 +/- 11.2 kg). Data was collected with an optical motion capture system (Vicon, Oxford, UK) and was analyzed using customized analysis scripts in BodyBuilder (Vicon, Oxford, UK) and MATLAB (MathWorks, Natick, MA, USA). Results: In all offloaded conditions, variation between subjects increased compared to 1‐g. Kinematics in the ARGOS at lunar gravity resembled earth gravity ambulation more closely than the C‐9 ambulation. Toe‐off occurred 10% earlier in both reduced gravity environments compared to earth gravity, shortening the stance phase. Likewise, ankle, knee, and hip angles remained consistently flexed and had reduced peaks compared to earth gravity. Ground reaction forces in lunar gravity (normalized to Earth body weight) were 0.4 +/- 0.2 on the ARGOS, but only 0.2 +/- 0.1 on the C‐9. Discussion: Gait analysis showed differences in joint kinematics and temporal‐spatial parameters between the reduced gravity simulators and with respect to earth gravity. Although most of the subjects chose a somewhat unique ambulation style as a result of learning to ambulate in a new environment, all but two were consistent with keeping an Earth‐like gait. Learning how reduced gravity affects ambulation will help NASA to determine optimal suit designs, influence mission planning, help train crew, and may shed light on the underlying methods the body uses to optimize gait for energetic efficiency. Conclusion: Kinematic and kinetic analysis demonstrated noteworthy differences between an offloaded environment and 1‐g, as would be expected. The analysis showed a trend to change the ambulation style in an offloaded environment to a rolling‐loping walk (resembling crosscountry skiing) with increased swing time. This ambulation modification, particularly in the ARGOS, indicated that the relative kinetic energy of the subject was increased, on average, per the static body weight compared to the 1‐g condition. How much of this was influenced by the active offloading of the ARGOS system is unknown.

Cowley, Matthew↗

Enabling Fortran Standard Parallelism in GAMESS for Accelerated Quantum Chemistry Calculations

The performance of Fortran 2008 DO CONCURRENT (DC) relative to OpenACC and OpenMP target offloading (OTO) with different compilers is studied for the GAMESS quantum chemistry application. Specifically, DC and OTO are used to offload the Fock build, which is a computational bottleneck in most quantum chemistry codes, to GPUs. The DC Fock build performance is studied on NVIDIA A100 and V100 accelerators and compared with the OTO versions compiled by the NVIDIA HPC, IBM XL, and Cray Fortran compilers. The results show that DC can speed up the Fock build by 3.0× compared with that of the OTO model. Finally, with similar offloading efforts, DC is a compelling programming model for offloading Fortran applications to GPUs.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

A Path Toward Understanding the Performance Capabilities of SmartNIC Devices [Slides]

SmartNICs, accelerator devices integrated with a network, have conventionally been utilized to offload low-level networking functionality. However, newer SmartNIC variants, which incorporate a system-on-chip (SoC) with traditional designs, are challenging this precedent. Leveraging significantly augmented resources, these new devices offer increased versatility and the potential to more effectively complement a given architecture’s CPU. Naturally, there is performance overhead associated with offloading tasks from a host CPU to a SmartNIC. As SmartNICs become more versatile and are used for a wider range of computational tasks, it is critical to understand how well the SmartNICs perform those respective tasks in order to determine whether the cost of offloading is worthwhile. In this work, we lay out a path to understand the important question of when and when not to offload to SmartNIC devices by way of a series of microbenchmarks.

97 MATHEMATICS AND COMPUTING↗

The Instrumented Walking and Turning Test to Evaluate Suited Gait Dynamics and Performance in Extravehicular Activity Training Environments

Background and aims: Walking will be required for many exploration tasks on the Moon during the Artemis program. Walking in a straight line on the confined floorspace of a testing area, and repetitive treadmill walking that requires no change in direction may not adequately reflect the balance and coordination required during ambulation. Also, performance of turning maneuvers may be affected differently in different extravehicular activity (EVA) training facilities that simulate partial gravity. For example, the Neutral Buoyancy Lab (NBL) simulates lunar gravity by adding weight to underwater subjects to alter buoyancy and achieve the equivalent ground reaction force of 1/6 of Earth’s gravity (1/6G), whereas the Active Response Gravity Offload System (ARGOS) uses a computer controlled overhead suspension system programmed to continuously offload a percentage of a subject’s weight to simulate 1/6G. The degree to which dynamic movements such as turning are comparable across these EVA training facilities has not yet been evaluated. The instrumented gait test helps NASA scientists and engineers evaluate gait dynamics and performance in suited conditions, and this test demonstrates the unique characteristics and limitations of EVA training facilities. We developed an instrumented walking and turning test using inertial measurement units (IMUs) and conducted the test at NASA’s EVA training facilities. Results were used to compare suited walking and turning characteristics in the ARGOS and the NBL. Methods: Subjects donned the Mark III space suit during offloading with the ARGOS spreader bar gimbal and donned the Z2.5 space suit while underwater in the NBL with weights and floatation added to achieve realistic suit center of gravity. The test team securely attached three Opal (APDM, OR, USA) wireless IMUs on the space suit for each test run: one on the middle of the hard upper torso, and one on the left and on the right ankle bearings. During the NBL tests, the IMUs were encased in a waterproof housing (GoPro) with foam added to create a tighter fit. At both testing facilities, 6.3 m x 1.0 m (LxW) walking lines were marked, and a cone for turning or walking around was located at the end of the walking path with another line on the other side of the cone to indicate the stopping point after walking around the cone. Under simulated 1/6G, subjects began by standing at the marked line with their arms folded across the chest, they then walked at a preferred speed along the straight walking path until they reached the end, turned 180 degrees around the cone, and finally stopped at the marked stopping point. All IMU data recorded during testing were automatically saved to the internal memory. Then, raw IMU signals were processed using custom MATLAB (Mathworks, MA, USA) code to compare gait parameters during both the walking and the turning components of the task. These parameters included time (s), speed (m/s for walking and rad/s for turning), step number (n) and walk:turn time ratio (% time spent straight walking versus turning). Results: Less time, faster gait, fewer steps, and higher walk:turn ratio during both walking and turning components were exhibited during tests performed at the ARGOS versus those performed at the NBL. During the NBL tests, the slower walking speed continued at the same rate throughout a U-shape turn. During the ARGOS tests, the subjects performed shorter and tighter turns at 4 times the speed of the NBL turns because they walked 30% faster and the vertical offloading system gave them more support. Conclusion: Our data show that the differences in walking and turning parameters during the NBL tests may be due to the high viscosity in the water environment where the motion of the lower limbs was slow and did not reach full flexion and extension. These tests improve the current knowledge of testing environments in preparation for EVAs on the lunar surface.

Kyoung Jae Kim↗

NASA Space Environment Analog for Training, Engineering, Science, and Technology (SEATEST) 6 Detailed Final Report

After more than 50 years since the last crewed lunar landing, plans for more missions to the moon are in development. For these missions, efficient and sustainable logistics will be critical. Additionally, innovative methods of cargo transfer to and from a lunar outpost should be considered for successfully establishing a permanent presence on the moon. SEATEST (Space Environment Analog for Training, Engineering, Science, and Technology) is an immersive mission-analogous operational atmosphere where buoyancy effects and supplemental weights can simulate partial gravity conditions similar to those astronauts will experience on the moon. SEATEST 6 took place at the University of Southern California (USC) Wrigley Marine Science Center on Santa Catalina Island from July 18-30, 2023. The analog was used to collect preliminary logistics data on two different offloading conceptual methods (a davit and a zipline) during a simulated lunar mission. Pre-test analysis indicated for a crew of two on a 14-day mission, approximately three Medium Pressurized Logistics Containers (MPLC) sized logistics containers (or a total of 37.5 single Cargo Transfer Bag Equivalents (CTBE)) would be needed to support a mission. A Computer-Aided Design (CAD) analysis was employed on the SEATEST airlock mockup to determine how many logistic containers would fit with two suited crewmembers, don/doff stands, and hatch operations. It was determined that for SEATEST, a total of 15 1.0 Small Pressurized Logistics Containers (SPLCs) and 8 2.0 SPLCs would adequately fit into the approximate 9.5 cubic meter airlock volume. This does not fully represent a complete 14-day logistic supply; however, it does provide a preliminary estimate to initiate design conversations between logistics teams and crew at this early stage of development. Data were collected in eight logistics transfer scenarios over two days with four scenarios per day. Five test subject crew participated in scenarios as pairs. Scenarios included two sizes of logistics containers – 1.0 SPLC (equivalent to a single Cargo Transfer Bag (CTB) and 2.0 SPLC (equivalent to two CTBs). Planed evaluations included the use of a logistics port compared to transfer through an Airlock hatch, offloading methods based on either a davit or a zipline system, choreography of cargo in the airlock to permit ingress and suit doffing, and dust removal protocols for an understanding of the overall impact to transfer ops. Data collected included objective data (task times for conducting overall tasks and subtasks, full audio/video of test activities, and inadvertent “dings” on hardware) and subjective data (crew consensus of: task acceptability and capability assessment ratings related to best practices, considerations, and constraints for EVA-driven logistics transfer ConOps, sim quality of the test environment, and more general debrief comments). The two logistic offloading transfer concepts (davit, zipline) presented both advantages and limitations. The davit’s flexibility in allowing the crew to pick up the containers without physical interaction was well regarded by the crew. Some limitations of select davit hardware components were noted, but the overall concept was acceptable. The zipline system proved to be the most efficient way of moving logistics from the lander to the airlock and eliminated the need for dust operations. However, extended and repetitive lifting of containers to the line could be fatiguing. In conclusion, logistics transfer could hypothetically be achieved without an offloading method; however, the time requirement for such operations would be prohibitive. Results of crew subjective feedback proposed a combined or hybrid davit/zipline method to increase efficiency.

Logistics↗

Comparison of Physical Workload Across Eva-Simulation Analog Environments: Hybrid Space Suit Simulator and Pressurized Suit Testing

NASA conducts research, testing, and training across a variety of analog environments to support characterization of human performance during Extravehicular Activities (EVAs). Time utilizing pressurized suits in an offloaded environment is both limited and expensive, making it challenging to carry out extensive research with these suits. The Human Physiology, Performance, Protection, and Operations (H-3PO) Laboratory at NASA Johnson Space Center designed a Hybrid Space Suit Simulator (HS3) as a low-cost, workload approximator and easy access research tool to provide relevant physical and cognitive workloads during simulated EVAs. A pilot study was conducted in a 1g analog environment where six healthy subjects (3 male, 3 female) underwent simulated 5-hour EVAs in the HS3. This study used a COSMED K5 portable metabolic analyzer and a Polar H10 heart rate monitor to evaluate physical workload during the EVAs. For direct comparison, EVA tasks and timelines were modeled after a similar study conducted in pressurized suits (Mark-III spacesuit, n=3 male; small xPGS spacesuit, n=3 female) at NASA’s Active Response Gravity Offload System (ARGOS) offloaded to Lunar gravity (1/6 g). The 1g HS3 data demonstrated increased metabolic rate when compared to pressurized, Lunar-offloaded suited simulated EVAs for certain tasks including the kneeling scoop (HS3: 1194±199 BTU/hr, ARGOS: 860±170 BTU/hr, p < 0.05) and 20 lb object relocation (HS3: 1651±136 BTU/hr, ARGOS: 1048±252.8 BTU/hr, p < 0.05), but it did not demonstrate any significant differences in heart rate (p > 0.05). Other simulated EVA tasks, such as a 500 m traverse (HS3: 1431±177 BTU/hr, ARGOS: 1212±294 BTU/hr, p > 0.05), showed similar workload profiles with no significant workload differences between HS3 and ARGOS. The HS3 is a useful research tool for increasing workloads in EVA research without pressurized suits, though it may overestimate workload during certain EVA tasks when used in 1g environments.

Zachary Wusk↗

Performance Characteristics of the BlueField-2 SmartNIC

High-performance computing (HPC) researchers have long envisioned scenarios where application workflows could be improved through the use of programmable processing elements embedded in the network fabric. Recently, vendors have introduced programmable Smart Network Interface Cards (SmartNICs) that enable computations to be offloaded to the edge of the network. There is great interest in both the HPC and high-performance data analytics (HPDA) communities in understanding the roles these devices may play in the data paths of upcoming systems. This paper focuses on characterizing both the networking and computing aspects of NVIDIA’s new BlueField-2 SmartNIC when used in a 100Gb/s Ethernet environment. For the networking evaluation we conducted multiple transfer experiments between processors located at the host, the SmartNIC, and a remote host. These tests illuminate how much effort is required to saturate the network and help estimate the processing headroom available on the SmartNIC during transfers. For the computing evaluation we used the stress-ng benchmark to compare the BlueField-2 to other servers and place realistic bounds on the types of offload operations that are appropriate for the hardware. Our findings from this work indicate that while the BlueField-2 provides a flexible means of processing data at the network’s edge, great care must be taken to not overwhelm the hardware. While the host can easily saturate the network link, the SmartNIC’s embedded processors may not have enough computing resources to sustain more than half the expected bandwidth when using kernel-space packet processing. From a computational perspective, encryption operations, memory operations under contention, and on-card IPC operations on the SmartNIC perform significantly better than the general-purpose servers used for comparisons in our experiments. Therefore, applications that mainly focus on these operations may be good candidates for offloading to the SmartNIC.

97 MATHEMATICS AND COMPUTING↗

Simulating Diverse HEP Workflows on Heterogeneous Architectures

We evaluate key patterns and estimate throughput bounds of simulated transformation of conventional high energy physics (HEP) data processing workflows to heterogeneous equivalents. The simulation parameter space includes the number of offloaded tasks, CPU/accelerator ratios of intra-task computations, offload latencies, and run time efficiency of offloaded computations. The simulation is performed for a diverse set of state-of-the-art event reconstruction scenarios from ATLAS, LHCb and CMS - the frontier HEP experiments of the Large Hadron Collider project.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

Clacc: OpenACC for C/C++ in Clang

The Clacc project has developed OpenACC compiler, runtime, and profiling interface support for C/C++ by extending Clang and LLVM. A key Clacc design feature is that it translates OpenACC to OpenMP to leverage the OpenMP offloading support that is actively being developed for Clang and LLVM. A benefit of this design is support for two compilation modes: traditional compilation mode produces a binary, and source-to-source mode produces OpenMP source. Clacc has been deployed on Oak Ridge National Laboratory’s (ORNL’s) Frontier, on which Clacc is the only OpenACC implementation for C/C++. Clacc supports x86_64, POWER9, AMD GPUs, and NVIDIA GPUs. Clacc’s OpenACC profiling interface support has been integrated with TAU, which is also deployed on Frontier. While Clacc has always supported C as a base language, Clacc also has increasing C++ support, including support for Kokkos’s OpenACC back end. Clacc itself is hosted publicly on GitHub. In this paper, we describe Clacc’s design and mapping from OpenACC directives to OpenMP. We also present a performance evaluation on ORNL’s Frontier (AMD MI250x GPU offload) and Argonne National Laboratory’s (ANL’s) Polaris (NVIDIA A100 GPU offload) for various SPEC ACCEL and Kokkos OpenACC back end benchmarks.

97 MATHEMATICS AND COMPUTING↗

Exploring OpenSNAPI Use Cases and Evolving Requirements [Slides]

Emerging system architectures are rapidly transforming in order to meet shifting requirements. Motivated by expanding data volumes, energy efficiency concerns, and the omnipresent need to improve performance, architectures are increasingly adopting a data-centric approach. At the core of this concept is the goal of minimizing data motion and instead processing data in-situ to the greatest degree possible. Therefore, data-centric designs, in contrast to conventional CPU-centric models, typically distribute compute capabilities throughout the architecture. As part of this paradigm shift, a novel class of devices known as data processing units (DPUs), alongside CPUs and GPUs, are quickly forming a third pillar of data-centric systems. These devices, which include smart network adapters and switches, seek to offload computation on data at the network edge as well as in-flight within the network fabric. The Open Smart Network API (OpenSNAPI) project seeks to develop a unified API for DPU devices. In our previous talks, we introduced the OpenSNAPI project and detailed our investigations regarding the viability of offloading compute intensive kernels to BlueField DPUs. In contrast, in this talk we detail our efforts to offload application-level file I/O to the DPU. We also discuss plans and early efforts to explore in-network compute capabilities. Finally, we describe our observations with respect to the evolving design of OpenSNAPI.

97 MATHEMATICS AND COMPUTING↗

Design and feasibility study for a portable oil recovery turbopump

A portable oil recovery turbopump concept, using the Firefly module as primer mover, for the offloading of distressed tank vessels is examined. The demands to be met both in terms of the type of petroleum to be offloaded, as well as the operational requirements placed on the pump, are studied with respect to the capability of different pump configurations. Two configurations, one a centrifugal type and the other a screw type pump, are developed and evaluated. While the centrifugal configuration is found to be effective in a large proportion of tank vessel offloading situations, the screw type will be required where high viscosity cargoes are involved. The feasibility of the turbopump concept, with the Firefly module as prime mover, is established.

Source record↗

Acquisition and production of skilled behavior in dynamic decision-making tasks: Modeling strategic behavior in human-automation interaction: Why and aid can (and should) go unused

Advances in computer and control technology offer the opportunity for task-offload aiding in human-machine systems. A task-offload aid (e.g., an autopilot, an intelligent assistant) can be selectively engaged by the human operator to dynamically delegate tasks to an automated system. Successful design and performance prediction in such systems requires knowledge of the factors influencing the strategy the operator develops and uses for managing interaction with the task-offload aid. A model is presented that shows how such strategies can be predicted as a function of three task context properties (frequency and duration of secondary tasks and costs of delaying secondary tasks) and three aid design properties (aid engagement and disengagement times, aid performance relative to human performance). Sensitivity analysis indicates how each of these contextual and design factors affect the optimal aid aid usage strategy and attainable system performance. The model is applied to understanding human-automation interaction in laboratory experiments on human supervisory control behavior. The laboratory task allowed subjects freedom to determine strategies for using an autopilot in a dynamic, multi-task environment. Modeling results suggested that many subjects may indeed have been acting appropriately by not using the autopilot in the way its designers intended. Although autopilot function was technically sound, this aid was not designed with due regard to the overall task context in which it was placed. These results demonstrate the need for additional research on how people may strategically manage their own resources, as well as those provided by automation, in an effort to keep workload and performance at acceptable levels.

Kirlik, Alex↗

Modeling strategic behavior in human-automation interaction - Why an 'aid' can (and should) go unused

Task-offload aids (e.g., an autopilot, an 'intelligent' assistant) can be selectively engaged by the human operator to dynamically delegate tasks to automation. Introducing such aids eliminates some task demands but creates new ones associated with programming, engaging, and disengaging the aiding device via an interface. The burdens associated with managing automation can sometimes outweigh the potential benefits of automation to improved system performance. Aid design parameters and features of the overall multitask context combine to determine whether or not a task-offload aid will effectively support the operator. A modeling and sensitivity analysis approach is presented that identifies effective strategies for human-automation interaction as a function of three task-context parameters and three aid design parameters. The analysis and modeling approaches provide resources for predicting how a well-adapted operator will use a given task-offload aid, and for specifying aid design features that ensure that automation will provide effective operator support in a multitask environment.

Kirlik, Alex↗

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.↗

Generating a Reduced Gravity Environment on Earth

The Active Response Gravity Offload System (ARGOS) is designed to simulate reduced gravity environments, such as Lunar, Martian, or microgravity using a vertical lifting hoist and horizontal motion system. Three directions of motion are provided over a 41 ft x 24 ft x 25 ft tall area. ARGOS supplies a continuous offload of a portion of a person's weight during dynamic motions such as walking, running, and jumping. The ARGOS system tracks the person's motion in the horizontal directions to maintain a vertical offload force directly above the person or payload by measuring the deflection of the cable and adjusting accordingly.

Dungan, L. K.↗