Search NASA⌕ Search

SEARCH · Search NASA

Results for “data collection methods”

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 55 records · Page 3

Utilization of the International Space Station for Crew Autonomous Scheduling Test (CAST)

The United States space policy is evolving toward missions beyond low Earth orbit. In an effort to meet that policy, NASA has recognized Autonomous Mission Operations (AMO) as a valuable capability. Identified within AMO capabilities is the potential for autonomous planning and replanning during human spaceflight operations. That is allowing crew members to collectively or individually participate in the development of their own schedules. Currently, dedicated mission operations planners collaborate with international partners to create daily plans for astronauts aboard the International Space Station (ISS), taking into account mission requirements, ground rules, and various vehicle and payload constraints. In future deep space operations the crew will require more independence from ground support due to communication transmission delays. Furthermore, crew members who are provided with the capability to schedule their own activities are able to leverage direct experience operating in the space environment, and possibly maximize their efficiency. CAST (Crew Autonomous Scheduling Test) is an ISS investigation designed to analyze three important hypotheses about crew autonomous scheduling. First, given appropriate inputs, the crew is able to create and execute a plan in a reasonable period of time without impacts to mission success. Second, the proximity of the planner, in this case the crew, to the planned operations increases their operational efficiency. Third, crew members are more satisfied when given a role in plan development. This paper presents the results from a single astronaut test subject who participated in five CAST sessions. The details on the operational philosophy of CAST are discussed, including the approach to crew training, selection criteria for test days, and data collection methods. CAST is a technology demonstration payload sponsored by the ISS Research Science and Technology Office, and performed by experts in Mission Operations Planning from the Flight Operations Directorate at NASA Johnson Space Center, and researchers across multiple NASA centers. It is hoped the results of this investigation will guide NASA's implementation of autonomous mission operations for long duration human space missions to Mars and beyond.

Healy, Matthew↗

Field Evaluations of Sampling, Interviewing, and Flight Tracking of NASA's Low Boom Flight Demonstrator Aircraft

The first year’s effort identified sampling and interviewing as the principal risks to assessment of prompt reactions to overflights producing low-amplitude sonic booms. It also 1) established the utility of geo-information system-based route planning for LBFD flight missions, 2) developed and demonstrated a prototype of a geographically-distributed, Internet-enabled instrumentation system capable of wide-area tracking of LBFD aircraft in near-real time. The latter system permits synchronizing the conduct of interviews in multiple overflown communities with arrival times of shock waves at interviewing sites; and of measuring, archiving, and processing their acoustic signatures. Means were also recommended for constructing representative, telephone-based samples of eligible respondents living in households within carpet boom corridors adjacent to LBFD flight tracks, and for conducting interviews with cross-sectional (independent) samples of such respondents about their prompt reactions to exposure to low-amplitude sonic booms. A detailed study design was prepared and accepted by NASA for a set of single-contact attempt telephone interviews with a nationally representative sample of households. The study design focused on testing automated and live agent interview completion rates obtainable without callbacks. A minimal (two monitoring station) version of the aircraft tracking system was built and installed near a civil airport in a successful demonstration of the system’s ability to detect and track aircraft movements. The field exercise also demonstrated the ability of the system to capture the acoustic emissions of departing aircraft, and to serve aircraft position and sound level information to remote, geographically-distributed analysts in near-real time. Upon approval of OMB and IRB of the detailed study plan, a stratified, nationally representative sample of landline and wireless telephone-subscribing households was constructed. A total of 12,734 telephone interview contact attempts of the sort required by a straightforward cross-sectional study design were then made. These contact attempts demonstrated the impracticality of conducting a time-critical, cross-sectional study of prompt community response to low-amplitude sonic booms by means of “independent” (single contact attempt per respondent for each LBFD flight mission) telephone samples of respondents. The observed interview completion rates for these single telephone contact attempts were so low (~ 1% to 3% for automated and live agent interviews, respectively) that: 1) the representativeness of collected opinions would be susceptible to intuitive challenge as inadequate, even absent conclusive evidence of non-representativeness. Refuting challenges to representativeness would have to demonstrate that the composition of the actual sample did not differ from that of the target population, a task that is tantamount to proving a negative; 2) the information required to refute allegations of non-representativeness would require a questionnaire considerably lengthier than that required simply to determine the prevalence of boom-induced startle and annoyance. Such a questionnaire would have to inquire about potentially sensitive and intrusive matters, including respondents’ age, gender, education, employment, home ownership, income, ethnicity, family size, and other demographic factors; and 3) unreasonable numbers of attempts would be required to re-contact households with unsuccessful initial contact attempts, given the limited time available for doing so. For example, if about 500 completed interviews were desired in a supersonically overflown community, approximately 50,000 automated interview attempts would have to be made within ten to fifteen minutes of each LBFD overflight. Such large numbers of contact attempts could well exceed the numbers of households available for interview in areas of similar boom exposure levels in some communities near LBFD flight tracks. Such large numbers of interviews could be cost-effectively undertaken only by means of automated (i.e., outgoing interactive voice response) interviewing, a data collection method ill-suited for complex and sensitive questionnaire items. The infeasibility of independent sampling for evaluating prompt responses to LBFD overflights in a cross-sectional study is due in large part to simple non-response: that is, potential respondents – particularly those contacted on wireless telephones – refusing to answer calls with unfamiliar caller IDs. It is also due in part, however, to 1) the lack of time to attempt to contact the same respondent more than once within a few minutes after the arrival of a shock wave at the respondent’s location; and 2) the need to place calls during weekday/daytime hours, when response rates are notably lower than during evenings and weekends. Despite the poor interview completion rates achieved under the above constraints, cross sectional assessments of delayed reactions to LBFD overflights could still be feasible, if multiple attempts could be made to contact respondents during evening and weekend time periods, over extended time periods. Detailed plans for a longitudinal (panel) sample were developed as an alternative to a cross sectional sample design.

Fidell, Sanford↗

TPSAS-NF1676L-32540-DND

The supersonic/hypersonic ground testing serves a multitude of purposes and objectives. From structural and material integrity, to force and moment models; from pressure mapping, thermal imaging, shock structure to scramjet/ramjet engine operability and ignition studies. Hypersonics has become more of a high profile area of late. Compared to flight testing, ground testing typically it is less expensive and usually is not a one single-test test program. It is more forgiving in the fact that a test program can utilize a single test article and get data from a number of tests. Ground test data is the input to the formation of research databases, as well as, validation of CFD models/tools. To understand the output, one must first understand the inputs. To achieve supersonic/hypersonic speeds the use of compressors or compressed air storage along with converging-diverging nozzles are needed. Flight temperatures also need to be achieved for the ground test to truly simulate flight conditions. At NASA Langley's 8' High Temperature Tunnel (HTT), compressed natural gas (methane) is burned to heat the air. To validate that the desired test condition is met, test instrumentation is used and data is collected from the combustor all the way through the nozzle exit plane. In this talk, NASA Langley's 8' HTT will be the basis for what kind of test capabilities hypersonic ground testing offers. It certainly does not offer every capability within ground testing, nor will the discussion cover all types. Specific test techniques used and data collection methods will be discussed and how these confirm certain flight conditions have been achieved. There will be subsequent thoughts on experimental methods that aid test articles such as thrust stands, model actuation, etc.

Aaron W Fuchs↗

Vermont & New Hampshire Ecological Forecasting: Monitoring Trends in Tree Defoliation Due to Lymantria dispar Outbreaks to Predict Future Hardwood Tree Mortality and Health Impacts

The invasive, herbivorous insect Lymantria dispar is a major defoliator of hardwood trees in the northeastern United States. Established populations of L. dispar typically rest at low levels but undergo recurring outbreaks that cause tree mortality if they occur in quick succession or are combined with other stressors on tree health. Widespread defoliation events disrupt local wildlife, economies, and livelihoods. Accurate monitoring of defoliation events is necessary to implement effective land management practices that support tree health. There are challenges to accurately monitoring L. dispar outbreaks that include the ephemeral character of defoliation disturbances and the difficulties of conducting large-scale surveys of L. dispar populations using existing aerial and ground-based data collection methods. To better monitor the impact of L. dispar on forests in Vermont and New Hampshire, the NASA DEVELOP team partnered with organizations responsible for supporting land and invasive species management including the Forest Ecosystem Monitoring Cooperative, the Vermont Agency of Agriculture, Food and Markets, the University of New Hampshire Cooperative Extension, and the New Hampshire Division of Forests and Lands, Forest Health Program. The team used NASA Earth observations collected by the Terra, Soil Moisture Active Passive (SMAP), Shuttle Radar Topography Mission (SRTM), Landsat 7, and Landsat 8 satellites along with ancillary datasets to map historical tree defoliation from 2012 to 2021. In support of partners’ future land management efforts, the team created a Google Earth Engine tool that displays annual defoliation extent.

Seamore Zhu↗

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Medical Data Architecture Platform and Recommended Requirements for A Medical Data System for Exploration Missions

Minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions.In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Medical Data Architecture Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗

Medical Data Architecture (MDA) Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗

Medical Data Architecture (MDA) Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.In fiscal year 2018, the MDA project developed Test Bed 2, the second iteration in a series of prototypes with functionality focused on data security through role-based access control and encryption, integration with One Portal exercise software and ingestion of an ultrasound Digital Imaging and Communications in Medicine (DICOM) file and image display. Test Bed 2 advances the medical data system architecture framework by providing these functionalities in a scalable system that maintained a layered, modular design. The architecture framework uses a data services approach with role-based access to data in a customized medical record system suitable for space exploration. These functionalities were demonstrated as part of the Next Space Technologies for Exploration Partnerships (NextSTEP) ground test demonstrated at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Interfacing to a Core Flight Software (CFS) system, the MDA system, using Consultative Committee for Space Data Systems (CCSDS) protocol, transferred an exercise file from the simulated flight MDA system to a mirrored MDA system on the ground through the CFS system. The selection of data sources and demonstrations enabled the team to address stakeholder concerns throughout the development process. In the next iteration, the MDA team will work with stakeholders to identify additional relevant functionalities to further advance system data models, standards and principles that will inform the medical system requirements development.

medical data architecture↗

Medical Data Architecture Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current International Space Station (ISS) medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable an increasingly autonomous crew than the current ISS paradigm. The MDA will develop capabilities that support automated data collection, and the necessary functionality and challenges in executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. To attain this goal, the first year of the MDA project focused on reducing technical risk, developing documentation and instituting iterative development processes that established the basis for the first version of MDA software (or Test Bed 1). Test Bed 1 is based on a nominal operations scenario authored by the ExMC Element Scientist. This narrative was decomposed into a Concept of Operations that formed the basis for Test Bed 1 requirements. These requirements were successfully vetted through the MDA Test Bed 1 System Requirements Review, which permitted the MDA project to begin software code development and component integration. This paper highlights the MDA objectives, development processes, and accomplishments, and identifies the fiscal year 2017 milestones and deliverables in the upcoming year.

Data management↗

Medical Data Architecture Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current International Space Station (ISS) medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable an increasingly autonomous crew than the current ISS paradigm. The MDA will develop capabilities that support automated data collection, and the necessary functionality and challenges in executing a self-contained medical system that approaches crew health care delivery without assistance from ground support.To attain this goal, the first year of the MDA project focused on reducing technical risk, developing documentation and instituting iterative development processes that established the basis for the first version of MDA software (or Test Bed 1). Test Bed 1 is based on a nominal operations scenario authored by the ExMC Element Scientist. This narrative was decomposed into a Concept of Operations that formed the basis for Test Bed 1 requirements. These requirements were successfully vetted through the MDA Test Bed 1 System Requirements Review, which permitted the MDA project to begin software code development and component integration. This paper highlights the MDA objectives, development processes, and accomplishments, and identifies the fiscal year 2017 milestones and deliverables in the upcoming year.

Exploration medical system↗

Communication and Organization in Software Development: An Empirical Study

The empirical study described in this paper addresses the issue of communication among members of a software development organization. The independent variables are various attributes of organizational structure. The dependent variable is the effort spent on sharing information which is required by the software development process in use. The research questions upon which the study is based ask whether or not these attributes of organizational structure have an effect on the amount of communication effort expended. In addition, there are a number of blocking variables which have been identified. These are used to account for factors other than organizational structure which may have an effect on communication effort. The study uses both quantitative and qualitative methods for data collection and analysis. These methods include participant observation, structured interviews, and graphical data presentation. The results of this study indicate that several attributes of organizational structure do affect communication effort, but not in a simple, straightforward way. In particular, the distances between communicators in the reporting structure of the organization, as well as in the physical layout of offices, affects how quickly they can share needed information, especially during meetings. These results provide a better understanding of how organizational structure helps or hinders communication in software development.

Seaman, Carolyn B.↗

Method and systems for collecting data from multiple fields of view

Systems and methods for processing light from multiple fields (48, 54, 55) of view without excessive machinery for scanning optical elements. In an exemplary embodiment of the invention, multiple holographic optical elements (41, 42, 43, 44, 45), integrated on a common film (4), diffract and project light from respective fields of view.

Schwemmer, Geary K.↗

Using Simulations to Investigate Decision Making in Airline Operations

This paper examines a range of methods to collect data for the investigation of decision-making in airline Operations Control Centres (OCCs). A study was conducted of 52 controllers in five OCCs of both domestic and international airlines in the Asia-Pacific region. A range of methods was used including: surveys, interviews, observations, simulations, and think-aloud protocol. The paper compares and evaluates the suitability of these techniques for gathering data and provides recommendations on the application of simulations. Keywords Data Collection, Decision-Making, Research Methods, Simulation, Think-Aloud Protocol.

Bruce, Peter J.↗

Kinematic Sensors Evaluation for Spaceflight Exercise Data Collections

INTRODUCTION: On the International Space Station (ISS), exercise feedback from astronauts is very important to diagnose and mitigate any form-related injuries and ensure efficacious exercise prescriptions and systems. Going forward, exploration exercise efforts seek to gain further quantitative data of human and system performance. Currently, methods of collecting in-flight exercise data on the ISS are limited to marker-based motion capture (MoCap) where astronauts must wear reflective markers over their clothes and specialized cameras are used. The main objective of this work was to investigate the following alternative tracking options: markerless video-based MoCap and inertial measurement units (IMUs). These were compared against traditional marker-based MoCap to evaluate kinematic accuracy and inform feasible methods for future exercise data collections on the ISS, especially in support of future Vibration Isolation and Stabilization (VIS) system development. METHODS: Three test subjects performed a variety of flight-like resistance and aerobic exercises using the Miniature Exercise Device (MED-2), Concept-2 rowing ergometer, barbell mockup, bench (e.g., for bench press, hip thruster, and cycling), and a custom structure for dips. These were intended also to represent exercises which could be performed on the multi-modality European Enhanced Exploration Exercise Device (E4D) [1]. The marker-based MoCap data, collected through a 16-camera OptiTrack MoCap system, was regarded as the gold standard to compare the data against. Passive markers were affixed to each subject according to a modified full body Plug-in Gait marker set [2] with 46 total markers. The markerless MoCap data was collected using two GoPro Hero7 cameras and one GoPro Hero11 camera. For the IMU data, a full body set of 17 Xsens DOTs were placed on the subject: 10 upper body and 7 lower body IMUs. Biomechanical modeling and evaluation was conducted through OpenSim [3] (MoCap), OpenSense [4] (IMU), OpenCap [5] (markerless), ENABLE [6] (markerless), and other modeling software. Secondary objectives included comparing the volume of equipment, reducing mass and crew set-up time. RESULTS AND DISCUSSION: While there were issues with initial processing for the IMUs and markerless MoCap, the results aided in the understanding of each sensor, developing end-to-end processes, and identifying future needs. Some observed concerns with the markerless MoCap approaches included being cognizant of a cluttered background, number of people in field of view, camera number and placement. Some challenges with the IMUs included possible sliding, early deactivation possibly due to exercise pose, and large quantity sensor synchronization. Overall, the markerless MoCap option may be the preferred method of data collection and processing as it provides a solution for certain IMU shortcomings and may be least in equipment volume, upmass, and crew setup time. CONCLUSIONS: While this work was mainly focused on ISS data collection, these sensor data along with continued evaluation and development efforts will help to establish best methods for exercise data collection on Gateway, for other Artemis missions, and beyond. Details on the latest end-to-end processing of the data and results will be presented, along with lessons learned and recommended sensor selection and methods.

S. Faragalla↗

Kinematic Sensors Evaluation for Spaceflight Exercise Data Collections

INTRODUCTION: On the International Space Station (ISS), exercise feedback from astronauts is very important to diagnose and mitigate any form-related injuries and ensure efficacious exercise prescriptions and systems. Going forward, exploration exercise efforts seek to gain further quantitative data of human and system performance. Currently, methods of collecting in-flight exercise data on the ISS are limited to marker-based motion capture (MoCap) where astronauts must wear reflective markers over their clothes and specialized cameras are used. The main objective of this work was to investigate the following alternative tracking options: markerless video-based MoCap and inertial measurement units (IMUs). These were compared against traditional marker-based MoCap to evaluate kinematic accuracy and inform feasible methods for future exercise data collections on the ISS, especially in support of future Vibration Isolation and Stabilization (VIS) system development. METHODS: Three test subjects performed a variety of flight-like resistance and aerobic exercises using the Miniature Exercise Device (MED-2), Concept-2 rowing ergometer, barbell mockup, bench (e.g., for bench press, hip thruster, and cycling), and a custom structure for dips. These were intended also to represent exercises which could be performed on the multi-modality European Enhanced Exploration Exercise Device (E4D) [1]. The marker-based MoCap data, collected through a 16-camera OptiTrack MoCap system, was regarded as the gold standard to compare the data against. Passive markers were affixed to each subject according to a modified full body Plug-in Gait marker set [2] with 46 total markers. The markerless MoCap data was collected using two GoPro Hero7 cameras and one GoPro Hero11 camera. For the IMU data, a full body set of 17 Xsens DOTs were placed on the subject: 10 upper body and 7 lower body IMUs. Biomechanical modeling and evaluation was conducted through OpenSim [3] (MoCap), OpenSense [4] (IMU), OpenCap [5] (markerless), ENABLE [6] (markerless), and other modeling software. Secondary objectives included comparing the volume of equipment, reducing mass and crew set-up time. RESULTS AND DISCUSSION: While there were issues with initial processing for the IMUs and markerless MoCap, the results aided in the understanding of each sensor, developing end-to-end processes, and identifying future needs. Some observed concerns with the markerless MoCap approaches included being cognizant of a cluttered background, number of people in field of view, camera number and placement. Some challenges with the IMUs included possible sliding, early deactivation possibly due to exercise pose, and large quantity sensor synchronization. Overall, the markerless MoCap option may be the preferred method of data collection and processing as it provides a solution for certain IMU shortcomings and may be least in equipment volume, upmass, and crew setup time. CONCLUSIONS: While this work was mainly focused on ISS data collection, these sensor data along with continued evaluation and development efforts will help to establish best methods for exercise data collection on Gateway, for other Artemis missions, and beyond. Details on the latest end-to-end processing of the data and results will be presented, along with lessons learned and recommended sensor selection and methods.

S Faragalla↗

An automated data collection system for a Charpy impact tester

A method for automated data collection has been developed for a Charpy impact tester. A potentiometer is connected to the pivot point of the hammer and measures the angular displacement of the hammer. This data is collected with a computer and, through appropriate software, accurately records the energy absorbed by the specimen. The device can be easily calibrated with minimal effort.

Weigman, Bernard J.↗