Search NASA⌕ Search

SEARCH · Search NASA

Results for “task load”

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.

796 records · Page 45

Muscle Volume Increases Following 16 Weeks of Resistive Exercise Training with the Advanced Resistive Exercise Device (ARED) and Free Weights

Space flight-induced muscle atrophy, particularly in the postural and locomotorymuscles, may impair task performance during long-duration space missions and planetary exploration. High intensity free weight (FW) resistive exercise training has been shown to prevent atrophy during bed rest, a space flight analog. NASA developed the Advanced Resistive Exercise Device (ARED) to simulate the characteristics of FW exercise (i.e. constant mass, inertial force) and to be used as a countermeasure during International Space Station (ISS) missions. PURPOSE: To compare the efficacy of ARED and FW training to induce hypertrophy in specific muscle groups in ambulatory subjects prior to deploying ARED on the ISS. METHODS: Twenty untrained subjects were assigned to either the ARED (8 males, 3 females) or FW (6 males, 3 females) group and participated in a periodizedtraining protocol consisting of squat (SQ), heel raise (HR), and deadlift(DL) exercises 3 d wk-1 for 16 wks. SQ, HR, and DL muscle strength (1RM) was measured before, after 8 wks, and after 16 wks of training to prescribe exercise and measure strength changes. Muscle volume of the vastigroup (V), hamstring group (H), hip adductor group (ADD), medial gastrocnemius(MG), lateral gastrocnemius(LG), and deep posterior muscles including soleus(DP) was measured using MRI pre-and post-training. Consecutive cross-sectional images (8 mm slices with a 2 mm gap) were analyzed and summed. Anatomical references insured that the same muscle sections were analyzed pre-and post-training. Two-way repeated measures ANOVAs (p<0.05) were used to test for differences in muscle strength and volume between training devices. RESULTS: SQ, HR, and DL 1RM increased in both FW (SQ: 49+/-6%, HR: 12+/-2%, DL: 23+/-4%) and ARED (SQ: 31+/-4%, HR: 18+/-2%, DL: 23+/-3%) groups. Both groups increased muscle volume in the V (FW: 13+/-2%, ARED: 10+/-2%), H (FW: 3+/-1%, ARED: 3+/-1 %), ADD (FW: 15=/-2%, ARED: 10+/-1%), LG (FW: 7+/-2%, ARED: 4+/-1%), MG (FW: 7+/-2%, ARED: 5+/-2%), and DP (FW: 2+/-1%; ARED: 2+/-1%) after training. There were no between group differences in muscle strength or volume. CONCLUSIONS: The increase in muscle volume and strength following ARED training is not different than FW training. With the training effects similar to FW and a 600 lb load capacity, ARED likely will protect against muscle atrophy in microgravity.

Nash, R. E.↗

A Low Cost Spacecraft Architecture for Robotic Lunar Exploration Projects

A program of frequent, capable, but affordable lunar robotic missions prior to return of humans to the moon can contribute to the Vision for Space Exploration (VSE) NASA is tasked to execute. The Lunar Reconnaissance Orbiter (LRO) and its secondary payload are scheduled to orbit the moon, and impact it, respectively, in 2008. It is expected that the sequence of missions occurring for approximately the decade after 2008 will place an increasing emphasis on soft landed payloads. These missions are requited to explore intrinsic characteristics of the moon, such as hydrogen distribution in the regolith, and levitated dust, to demonstrate the ability to access and process in-situ resources, and to demonstrate functions critical to supporting human presence, such as automated precision navigation and landing. Additional factors governing the design of spacecraft to accomplish this diverse set of objectives are: operating within a relatively modest funding profile, the need tb visit multiple sites (both polar and equatorial) repeatedly, and to use the current generation of launch vehicles. In the US, this implies use of the Evolved Expendable Launch Vehicles, or EELVs, although this design philosophy may be extended to launch vehicles of other nations, as well. Many of these factors are seemingly inconsistent with each other. For example, the cost of a spacecraft usually increases with mass; therefore the desire to fly frequent, modestly priced spacecraft seems to imply small spacecraft (< 1 Mt, injected mass). On the other hand, the smallest of the EELVs will inject approx. 3 Mt. on a Trans Lunar Injection (TLI) trajectory md would therefore be wasteful or launching a single, small spacecraft. Increasing the technical capability of a spacecraft (such as autonomous navigation and soft landing) also usually increases cost. A strategy for spacecraft design that meets these conflicting requirements is presented. Taken together, spacecraft structure and propulsion subsystems constitute the majority of spacecraft mass; saving development and integration cost on these elements is critical to controlling cost. Therefore, a low cost, modular design for spacecraft structure and propulsion subsystems is presented which may be easily scaled up or down for either insertion into lunar orbit or braking for landing on the lunar surface. In order to effectively use the approx.3 Mt mass-to-TLI of the EELV, two low cost spacecraft will be manifested on the same launch. One spacecraft will be located on top of the other for launch and the two will have to be released in sequence in order to achieve all mission objectives. The two spacecraft could both be landers, both orbiters, or one lander and one orbiter. In order to achieve mass efficiency, the body of the spacecraft will serve the dual purposes of carrying launch loads and providing attachment points for all the spacecraft subsystems. In order to avoid unaffordable technology development costs, small liquid propulsion components and autonomous, scene-matching navigation cameras may be adapted from military missile programs in order to execute precision soft landings.

Lemke, Lawrence G.↗

EVA Swab Kit: Tools and Techniques for Collecting Aseptic Samples from Crewed Space Missions

Introduction: When we send humans to search for life on other planets, we'll need to know what we brought with us versus what may already be there. To ensure our crewed spacecraft meet planetary protection requirements—and to protect our science from human contamination—we'll need to assess and verify whether micro-organisms may be leaking/venting from our spacesuits. This requires collecting samples under Extravehicular Activity (EVA) conditions. Detailed, systematic research on forward contamination from robotic spacecraft has been steadily progressing since the Viking missions, but systematic studies of contamination from space suits has not been conducted in many years. The modern EMU (Extravehicular Mobility Unit) suit used by NASA is designed to leak at rates as high as 100 cc/min. Before humans land on Mars there is a critical need to understand the types and quantities of microbes that could be introduced via space suits. The Human Forward Contamination Assessment team at NASA’s Johnson Space Center (JSC) has developed a prototype EVA swab tool [1,2,3,4] designed for use in space to sample cleaned and uncleaned space suits to determine the present day microbial load and eventually the rate of leakage. The ability to assess microbial leakage early in advanced space suit and life support system design cycles will help avoid costly hardware redesign later. Test Objectives: The primary objective of EMU testing was to characterize the type of micro-organisms typically found on or near selected suit pressure joints under suit differential pressure conditions. Most human-borne microbes can fit through a 0.5 to 1.0 µm gap. Knowing which joints are more likely to leak will inform hardware design decisions. Knowing which types of micro-organisms may leak from EVA suits provides a basis for subsequent studies to characterize the viability of those organisms under destination conditions, as well as how far they might spread through natural or human-influenced processes. That data, in turn, will inform exploration mission operations and hardware design. The secondary objective of testing was to evaluate the interface between a fully suited test subject and the EVA swab tool at vacuum. Bulky EVA suits can restrict movement and limit visibility through the helmet visor. Fully suited testing is important for identifying tool design issues prior to flight. At exploration destinations, such as Mars, suited crew may be required to periodically sample their suits as part of an environmental monitoring protocol. Suit Microbial Sampling Results: This report details results of microbial swabs collected from current flight suit configurations worn by crew members assigned to upcoming ISS expedition missions as well as swabs collected from prototype suits intended for use on the Orion spacecraft. These tests were intended to characterize the types of contaminants found on flight suits under current, typical handling conditions. No attempt was made to change suit handling procedures, provide additional sterilization, or to limit typical potential contaminant sources. Using culture based techniques, we cultivated 235 CFU (colony forming units) comprised of 26 bacterial species and one fungal species on the outside of the suits. The fungal species and 14 of the bacterial species were unique to the suit surfaces and were not detected in any of the background samples collected within the chambers. We sequenced 755,434 ribosomal fragments on all of the suit surfaces from swab samples. 557,016 of these sequences represent DNA that survived at least 4 hours at vacuum. These sequences formed 2,464 OTU's (Operational Taxonomic Units, 97% similarity) showing low diversity in the samples. The most abundant sequences that survived vacuum belong to the genera Staphyloccocus, Ralstona, Bacillus and Rhodobacter all of which are common to the human microbiome. [5] See Danko et al., (2021) for more complete details of these first analyses. Further analysis of EVA suit materials with respect to the efficacy of various cleaning protocols and engineered containment solutions is planned to inform suit design for NASA’s Artemis Moon to Mars program crew testing. Swab Tool Function Results: The kit was demonstrated for fit and function in suited subject vacuum tests to determine how well the tool worked as an aseptic microbial sampling device as well as to identify any design elements that could be upgraded for EVA task specific improvement. It was found that sample acquisition efficacy could be enhanced by redesign of the sample canister to end-effector interface. Several modifications of the sample caddy assemblies to optimize EVA safety and functionality were also identified. Consequently, fabrication of the redesigned sample canister to end-effector assembly interfaces and and the sample caddy assemblies are required. Fabrication of sixteen flight sample canister assemblies (8 per each of two EVA Swab Kits) and two sample caddy assemblies are in process to be followed by hardware testing and certification to produce two flight-certified EVA Swab Kits for transport to ISS no earlier than summer of 2022. Sampling Strategy: The International Space Station is an ideal testbed for systematic studies of contamination from crewed vehicles since it has been continuously occupied for 20 years and exposed to non-terrestrial conditions. We will sample the exterior of the ISS during EVA using a purpose-built swab tool capable of maintaining sterility while undergoing temperature changes from -151 to +121°C under hard vacuum. Prior to each EVA, the project team will work with ISS mission managers to identify precise sampling locations, which will vary by EVA based on the translation paths and worksites scheduled for that particular EVA. Ideally, translation path handrails and areas near ECLSS (Environmental Control and Life Support System) external vent openings on a spacecraft would be assessed. There are currently more than a dozen ECLSS external vents on the ISS. Some are connected to systems that vent waste products, while others are intended to equalize cabin pressure. As EVA opportunity allows, microbial samples from any of these external vents would provide a valuable data point, though some will be more useful than others. Four criteria have been identified to help prioritize sampling sites near vents: • EVA Accessibility: To minimize cost, it is desired to piggy-back onto a planned EVA. Therefore, the sampling location must be readily accessible by an EVA crew • Type of Vented Products: Vent products that have been in direct contact with crew, such as cabin air, are more likely to contain microorganisms than vent products associated with isolated systems, such as experiment module combustion products. • Mass of Vented Products: Higher-flow vents are more likely to contain detectible levels of microbial contaminants than lower-flow vents. • Local Environment: Sample locations with relatively benign local conditions, such as warm surfaces shielded from direct ultraviolet (UV) radiation exposure, may be more likely to support microbial growth than locations with harsher local environmental conditions. Because EVA accessibility is the most important criteria, the proposal team worked with an astronaut and flight controllers using the Dynamic Onboard Ubiquitous Graphics (DOUG) tool. The DOUG virtual environment allows an operator to “fly” around the current ISS vehicle configuration to assess EVA translation paths, attach points, and keep-out zones. While analysis on station or rapid return to Earth would be preferable, samples collected from the exterior of the ISS have already been exposed to temperature variations between -157 and +121 °C as well as hard vacuum. Therefore, they should be fairly stable and robust. We hypothesize that samples collected from the ISS exterior could be stored for up to 6 months at -80°C without degradation. Sample canisters will be returned to Earth while frozen at -80°C for analysis, and sterilized canisters can be re-flown back to ISS to support additional sampling opportunities Relevance to NASA Exploration Objectives: These data will allow us to identify new or improved methods, technologies, and procedures for spacecraft sterilization and leakage mitigation to minimize the amount of contamination introduced to the environment by human explorers. This work is funded by NASA research grant: NNH18ZDA001N-PPR References: [1] Bell, M.S. et al. (2015) LPS XLVI, Abst. #1832 [2] Rucker et al. (2018) 42nd COSPAR (PPP.3) [3] Bell, M.S. et al. (2019) Mars Extant Life Conference, Abst. #5096.[4] Bell, M.S. et al., (2020) 43rd COSPAR (BO.2).[5] Danko D, et.al.,(2021)Front.Microbiol.12:608478.

Mary Suzanne Bell↗

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗