Search NASA⌕ Search

SEARCH · Search NASA

Results for “Communicate knowledge”

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 775 records · Page 43

Real-Time Science Decisioning During High Tempo-High Intensity Mission Operations and the Role of Analogs

Introduction: NASA’s VIPER mission presents a unique operational paradigm within the history of robotic spaceflight. The proximity of the Moon to the Earth and the terrain elements (surface characteristics, light/shadow dynamics, communication links) of the lunar South Polar landing site create unprecedented operational conditions between these two planetary bodies. Apollo era lunar science and exploration included humans in situ to operate instruments and assimilate observational inputs in real-time. Previous lunar orbital missions have worked to operational timescales, e.g., decisional timelines and communication exchanges, that were weeks in length. Mars rover missions have worked to operational timescales, e.g., decisional timelines and communication exchanges between Mars and Earth, that were hours, days, and weeks in length. In the case of the VIPER mission, our operational decisioning for rover driving and instrument commanding will be compressed to minute-scale timeframes. These operational conditions directly impact the manner and speed with which the VIPER Science Team (VST) is required to synthesize and analyze data and produce timely science-driven decisions throughout surface mission operations. The VST shall provide mission enhancing scientific input to guide rover traverse planning and drill site confirmation and selection throughout surface operations. Further, the VST input will be of vital importance to the mission’s ability to maximize science return and to meet broader NASA objectives for future lunar in-situ resource utilization (ISRU)and exploration activities. The VST co-located in the Mission Science Center (MSC) will be responsive to the tactical operational cadence of the Mission Operations Center (MOC) and will provide further strategic and Long-Term Planning (LTP) guidance to the mission. The VIPER Science Operations & Integration(SO&I)team has developed an architecture that is focused on the infusion of science-decisioning into the operational framework and execution cadence of VIPER. NASA analog research has played a significant role in the construction of the VIPER science operations systems. As an example, the SO&I team has led analog missions that have focused on bringing together expertise in the sciences (natural, applied and social) and in operations in service of learning how to build and hold together interdisciplinary work environments and what tools are needed to support high tempo, high intensity integrated decisioning. These experiences have provided an essential foundation of knowledge to the VIPER team. Those analogs that specifically influenced the VIPER science operations construct were identified through a process of comparative analysis to prioritize those that offered relevance in whole or in part, and those that did not. The analog research output that provided extensibility to the VIPER science operations architecture included remote teams of humans and robots in cooperation (synchronous and asynchronous) with simulated earthbound systems, engineering and science teams, and the integrated assembly of tools that supported scientific analysis and data synthesis and provided infrastructure for the remote testing framework. Analogs which included real-time data monitoring, synthesis, visualization and access in a democratized and operationalized manner were of particular interest to the development of the VIPER MSC toolset both in terms of the technology and the processes used to develop the supporting infrastructure. We anticipate that each subsequent mission to the lunar south pole, whether with robots or humans, will be able to optimize science and exploration return by evolving strategies to infuse real-time collaborative science-decisioning. Furthermore, these efforts will result in a foundation for science operations development in support of human-robotic exploration of deep space and Mars. NASA analogs can continue to provide the opportunity to prepare, test and iterate on the operational concepts and tools that will support these ever-expanding space exploration efforts. Our presentation will include an overview of the VIPER Science Operations & Integration development process and specifics on what aspects of analog research have had a significant impact on our work systems.

D S S Lim↗

Understanding Climate Policy Data Needs. NASA Carbon Monitoring System Briefing: Characterizing Flux Uncertainty, Washington D.C., 11 January 2012

Climate policy in the United States is currently guided by public-private partnerships and actions at the local and state levels. This mitigation strategy is made up of programs that focus on energy efficiency, renewable energy, agricultural practices and implementation of technologies to reduce greenhouse gases. How will policy makers know if these strategies are working, particularly at the scales at which they are being implemented? The NASA Carbon Monitoring System (CMS) will provide information on carbon dioxide fluxes derived from observations of earth's land, ocean and atmosphere used in state of the art models describing their interactions. This new modeling system could be used to assess the impact of specific policy interventions on CO2 reductions, enabling an iterative, results-oriented policy process. In January of 2012, the CMS team held a meeting with carbon policy and decision makers in Washington DC to describe the developing modeling system to policy makers. The NASA CMS will develop pilot studies to provide information across a range of spatial scales, consider carbon storage in biomass, and improve measures of the atmospheric distribution of carbon dioxide. The pilot involves multiple institutions (four NASA centers as well as several universities) and over 20 scientists in its work. This pilot study will generate CO2 flux maps for two years using observational constraints in NASA's state-of -the-art models. Bottom-up surface flux estimates will be computed using data-constrained land and ocean models; comparison of the different techniques will provide some knowledge of uncertainty in these estimates. Ensembles of atmospheric carbon distributions will be computed using an atmospheric general circulation model (GEOS-5), with perturbations to the surface fluxes and to transport. Top-down flux estimates will be computed from observed atmospheric CO2 distributions (ACOS/GOSAT retrievals) alongside the forward-model fields, in conjunction with an inverse approach based on the CO2 model of GEOS ]Chem. The forward model ensembles will be used to build understanding of relationships among surface flux perturbations, transport uncertainty and atmospheric carbon concentration. This will help construct uncertainty estimates and information on the true spatial resolution of the top-down flux calculations. The relationship between the top-down and bottom-up flux distributions will be documented. Because the goal of NASA CMS is to be policy relevant, the scientists involved in the flux modeling pilot need to understand and be focused on the needs of the climate policy and decision making community. If policy makers are to use CMS products, they must be aware of the modeling effort and begin to design policies that can be evaluated with information. Improving estimates of carbon sequestered in forests, for example, will require information on the spatial variability of forest biomass that is far more explicit than is presently possible using only ground observations. Carbon mitigation policies being implemented by cities around the United States could be designed with the CMS data in mind, enabling sequential evaluation and subsequent improvements in incentives, structures and programs. The success of climate mitigation programs being implemented in the United States today will hang on the depth of the relationship between scientists and their policy and decision making counterparts. Ensuring that there is two-way communication between data providers and users is important for the success both of the policies and the scientific products meant to support them..

Brown, Molly E.↗

Analyzing Risks and Vulnerabilities of Various Computer Systems and Undergoing Exploitation using Embedded Devices

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere has heightened from airports to communication among the military branches legionnaires. With advanced persistent threats (APTs) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated, patched and secured state in a launch control system environment. Attacks on critical systems are becoming more and more relevant and frequent. Nation states are hacking into critical networks that might control electrical power grids or water dams as well as carrying out advanced persistent threat (APTs) attacks on government entities. NASA, as an organization, must protect its self from attacks from all different types of attackers with different motives. Although the International Space Station was created, there is still competition between the different space programs. With that in mind, NASA might get attacked and breached for various reasons such as espionage or sabotage. My project will provide a way for NASA to complete an in house penetration test which includes: asset discovery, vulnerability scans, exploit vulnerabilities and also provide forensic information to harden systems. Completing penetration testing is a part of the compliance requirements of the Federal Information Security Act (FISMA) and NASA NPR 2810.1 and related NASA Handbooks. This project is to demonstrate how in house penetration testing can be conducted that will satisfy all of the compliance requirements of the National Institute of Standards and Technology (NIST), as outlined in FISMA. By the end of this project, I hope to have carried out the tasks stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, as well as policies and procedures.

Penetration Testing↗

An Intelligent Archive Testbed Incorporating Data Mining

Many significant advances have occurred during the last two decades in remote sensing instrumentation, computation, storage, and communication technology. A series of Earth observing satellites have been launched by U.S. and international agencies and have been operating and collecting global data on a regular basis. These advances have created a data rich environment for scientific research and applications. NASA s Earth Observing System (EOS) Data and Information System (EOSDIS) has been operational since August 1994 with support for pre-EOS data. Currently, EOSDIS supports all the EOS missions including Terra (1999), Aqua (2002), ICESat (2002) and Aura (2004). EOSDIS has been effectively capturing, processing and archiving several terabytes of standard data products each day. It has also been distributing these data products at a rate of several terabytes per day to a diverse and globally distributed user community (Ramapriyan et al. 2009). There are other NASA-sponsored data system activities including measurement-based systems such as the Ocean Data Processing System and the Precipitation Processing system, and several projects under the Research, Education and Applications Solutions Network (REASoN), Making Earth Science Data Records for Use in Research Environments (MEaSUREs), and the Advancing Collaborative Connections for Earth-Sun System Science (ACCESS) programs. Together, these activities provide a rich set of resources constituting a value chain for users to obtain data at various levels ranging from raw radiances to interdisciplinary model outputs. The result has been a significant leap in our understanding of the Earth systems that all humans depend on for their enjoyment, livelihood, and survival. The trend in the community today is towards many distributed sets of providers of data and services. Despite this, visions for the future include users being able to locate, fuse and utilize data with location transparency and high degree of interoperability, and being able to convert data to information and usable knowledge in an efficient, convenient manner, aided significantly by automation (Ramapriyan et al. 2004; NASA 2005). We can look upon the distributed provider environment with capabilities to convert data to information and to knowledge as an Intelligent Archive in the Context of a Knowledge Building system (IA-KBS). Some of the key capabilities of an IA-KBS are: Virtual Product Generation, Significant Event Detection, Automated Data Quality Assessment, Large-Scale Data Mining, Dynamic Feedback Loop, and Data Discovery and Efficient Requesting (Ramapriyan et al. 2004).

Ramapriyan, H.↗

College Bound with the Office of Educational Programs

The Educational Programs Office at NASA Glenn Research Center hosts a variety of programs that takes on the hard task of getting students of all ages interested in pursuing careers in science, mathematics, and engineering. To help assist students along the way there are many programs to participate in such as: the explorers, shadowing opportunities, and paid internships. The Educational Programs Office not only creates learning opportunities for students, they also host workshops to help educators enhance their knowledge these fields. This summer I assisted Marie Borowski in the Educational Programs Office with the Tennessee State University College Bound Program. The Tennessee state University College Bound Program is an intensive two-week summer academic workshop designed to introduce minority students to the profession of engineering. NASA Glenn Research Center sent forty dedicated students on a bus to Nashville, Tennessee to experience college life as a whole. At the college the students day consisted of a math class, aeronautics, ACT/SAT preparation, writing and research, African American Culture, computer science, and study sessions. The students also went on educational field trips to the Fisk Museum, the Space and Rocket Center, and the Parthenon Museum. On the last day of the program the students competed in an oratorical contest where the students made a Powerpoint presentation on the class that they enjoyed the most. There were many processes that had to be put into action for the college bound program to run smoothly. The process started in early January with the preparation of applications. Once prepared, the applications were then sent to schools and past participants in hopes of receiving a well-qualified pool of applicants. Once the applications were received, a prescreening is done which ensures all of the information is complete. Then, they are reviewed by a panel, using a rubric to evaluate them, and the semifinalists are then selected. Interviews are held with the students and their parents had to be interviewed by a panel of judges and graded on a rubric. The scores were added up and the forty students were selected. My job this summer was getting the students ready to leave for Tennessee. My job consisted of working very closely with my mentor, Marie Borowski, compile the student data to provide it to the chaperones, TSU records, and NASA records. I learned about the vital communication between the NASA and the TSU program managers. After all the planning was done and the program had begun I had a chance to fly to Tennessee for six days to observe the students daily activities. The students had adjusted very well to the intense schedule, and seemed very enthusiastic about the activities to follow. The whole group was very attentive and enthusiastic program be longer. My goals for the summer were all met. I wanted to learn and retain all the information I possibly could on the job I was given. I was very happy with the end result.

Neal, Brittany D.↗

An Introduction to Flight Software Development: FSW Today, FSW 2010

Experience and knowledge gained from ongoing maintenance of Space Shuttle Flight Software and new development projects including Cockpit Avionics Upgrade are applied to projected needs of the National Space Exploration Vision through Spiral 2. Lessons learned from these current activities are applied to create a sustainable, reliable model for development of critical software to support Project Constellation. This presentation introduces the technologies, methodologies, and infrastructure needed to produce and sustain high quality software. It will propose what is needed to support a Vision for Space Exploration that places demands on the innovation and productivity needed to support future space exploration. The technologies in use today within FSW development include tools that provide requirements tracking, integrated change management, modeling and simulation software. Specific challenges that have been met include the introduction and integration of Commercial Off the Shelf (COTS) Real Time Operating System for critical functions. Though technology prediction has proved to be imprecise, Project Constellation requirements will need continued integration of new technology with evolving methodologies and changing project infrastructure. Targets for continued technology investment are integrated health monitoring and management, self healing software, standard payload interfaces, autonomous operation, and improvements in training. Emulation of the target hardware will also allow significant streamlining of development and testing. The methodologies in use today for FSW development are object oriented UML design, iterative development using independent components, as well as rapid prototyping . In addition, Lean Six Sigma and CMMI play a critical role in the quality and efficiency of the workforce processes. Over the next six years, we expect these methodologies to merge with other improvements into a consolidated office culture with all processes being guided by automated office assistants. The infrastructure in use today includes strict software development and configuration management procedures, including strong control of resource management and critical skills coverage. This will evolve to a fully integrated staff organization with efficient and effective communication throughout all levels guided by a Mission-Systems Architecture framework with focus on risk management and attention toward inevitable product obsolescence. This infrastructure of computing equipment, software and processes will itself be subject to technological change and need for management of change and improvement,

Gouvela, John↗

First-Generation Jet Propulsion Laboratory "Hockey-Puck" Free-Flying Magnetometers for Distributed In-Situ Multiprobe Measurement of Current Density Filamentation in the Northern Auroral Zone: Enstrophy Mission

The sub-orbital rocket mission was a collaborative project between the University of New Hampshire, Cornell University, and the Jet Propulsion Laboratory (JPL) to study filamentation phenomena in the northern Auroral zone. The Enstrophy mission test flies the JPL Free-Flying Magnetometer (FFM) concept. The FFM technology development task has been funded by NASA develop miniaturized, low-power, integrated "sensorcrafts". JPL's role was to design, integrate, test, and deliver four FFMs for deployment from the sounding rocket, allowing a unique determination of curl-B. This provides a direct measurement of magnetic-field-aligned current density along the rocket trajectory. A miniaturized three-axis fluxgate magnetometer was integrated with a 4-channel 22-bit sigma-delta Analog to Digital Converter (ADC), four temperature sensors, digital control electronics, seven (Li-SOCl2) batteries, two (4 deg x 170 deg field of view) sun-sensors, a fan-shaped-beam laser diode beacon, a (16 MHz) stable Temperature Compensated Crystal Oscillator (TCXO) clock, Radio Frequency (RF) communication subsystem, and an antenna for approximately 15 minutes of operation where data was collected continuously and transmitted in three (3) bursts (approximately 26 seconds each) to ground station antennas at Poker Flat, Alaska. FFMs were stowed within two trays onboard the rocket during the rocket launch and were released simultaneously using the spinning action of the rocket at approximately 300 km altitude (approximately 100 sec. into the flight). FFMs were deployed with spin rate of approximately 17 Hz and approximately 3 m/sec linear velocity with respect to the rocket. For testing purposes while the rocket was in the launch pad and during flight prior to release of FFMs from the rocket, commands (such as "power on", "test", "flight", "power off', and clock "Reset" signal) were transmitted via a infrared Light Emitting Diode to an infrared detector in the FFM. Special attention was paid to low magnetic signature electronic design and choice of materials in packaging. The miniaturized fluxgate magnetometers had a range of 1-60000 nT with 0.1% full-scale linearity. The frequency range of interest for magnetic measurement was 10 mHz - 50 Hz. Digital data from the magnetometer's three axes were placed in a 4MB Static Random Access Memory (SRAM) in data packages (frames) formatted together with time tags and frame ID. After a specified time was elapsed, the data were Viterbi encoded and transmitted at a rate of 100 kbps (BPSK). Each of the four FFMs transmitted at different frequency. These carrier frequencies were in the range of 2200-2300 MHz. The antenna was a single patch on a high dielectric constant substrate covering one end-plate of the hockey-puck-sized unit. The local clocks aboard the FFMs were reset at the start of the mission and stayed synchronized within 3 msec during the mission. Position of each FFM with respect to the rocket is calculated by the knowledge of its release velocity (measured at exit point of the FFM launcher tract) providing an accuracy of 1 m over the maximum range of 3 km. Spatial and temporal nature of observants can be separated to within 3 m in space or 3 msec time interval.

Javadi, H.↗

The Center Master Plan For NASA Glenn Research Center

The Center Master Plan for NASA Glenn Research Center is a comprehensive survey of NASA Glenn's current facility assets and a vision of how we see the facilities will change over the next 20 years in order to support the changing NASA Mission. This Center Master Plan is a vital management tool used by all organizations for making near term decisions and in future planning. During the summer of 2004, I worked with Joseph Morris, the Chief Architect in the Facilities Division, on beginning this Center Master Planning Process. The previous Master Plan was completed by the Center in 1985 and contained general information on the background of the facility as well as maps detailing environmental and historic records, land use, utilities, etc. The new Master Plan is required for the Center by NASA headquarters and will include similar types of information as used in the past. The new study will provide additional features including showing how individual buildings are linked to the programs and missions that they serve. The Master Plan will show practical future options for the facility s assets with a twenty year look ahead. The Plan will be electronically retrievable so that it becomes a communications tool for Center personnel. A Center Master Plan, although required, is very beneficial to NASA Glenn Research Center in aiding management with the future direction of the campus. Keeping up-to-date information and future plans readily available to all of NASA Glenn will insure that future real property development efficiently and effectively supports the missions camed out and supported by the Center. A Center Master Plan will also facilitate coordination with Center supported programs, stakeholders, and customers. In addition, it will provide a basis for cooperative planning with local and other governmental organizations and ultimately ensure that future budgets include the Center program needs described in the plan. This will ensure that development plans are safe, practical, and cost effective. To properly formulate any future plans, background information and research are required. Before bringing in a consultant to tackle the three year process anticipated to prepare a Center Master Plan, my job was to gather information on different organizations contributions to the NASA mission, their facility needs, consistent trends they observe, etc. I conducted numerous interviews with personnel such as Directorate Representatives, Division Chiefs, Branch Chiefs, System Managers and Building Managers. I documented the information I received from them for future use. I used the information to create various color-coded maps layering the different data. This was done with the ending objective being to collect the information and place it in a database that will be linked with Aperture (a computer program that generates color-coded map layers from database information) and made electronically retrievable to the Planning Consultant, NASA personnel, program stakeholders, and other governmental agencies. My goal this summer was to gather information and ideas appropriate for use in NASA Glenn Research Center s Master Plan and organize them for future application by the Planning Consultant. By the end of the summer, after completion of my goal, I will utilize my knowledge and create an array of preliminary future plans for the facility that can be passed along as a guidance tool.

Bigach, Kristin M.↗

NASA's Soil Moisture Active and Passive (SMAP) Mission

The Soil Moisture Active-Passive (SMAP) Mission is one of the first Earth observation satellites being formulated by NASA in response to the 2007 National Research Council s Decadal Survey. SMAP will make global measurements of soil moisture at the Earth's land surface and its freeze-thaw state. These measurements will allow significantly improved estimates of water, energy and carbon transfers between the land and atmosphere. Soil moisture measurements are also of great importance in assessing flooding and monitoring drought. Knowledge gained from SMAP observations can help mitigate these natural hazards, resulting in potentially great economic and social benefits. SMAP observations of soil moisture and freeze/thaw timing over the boreal latitudes will also reduce a major uncertainty in quantifying the global carbon balance and help to resolve an apparent missing carbon sink over land. The SMAP mission concept will utilize an L-band radar and radiometer sharing a rotating 6-meter mesh reflector antenna flying in a 680 km polar orbit with an 8-day exact ground track repeat aboard a 3-axis stabilized spacecraft to provide high-resolution and high-accuracy global maps of soil moisture and freeze/thaw state every two to three days. In addition, the SMAP project will use these surface observations with advanced modeling and data assimilation to provide estimates of deeper root-zone soil moisture and net ecosystem exchange of carbon. SMAP recently completed its Phase A Mission Concept Study Phase for NASA and transitioned into Phase B (Formulation and Detailed Design). A number of significant accomplishments occurred during this initial phase of mission development. The SMAP project held several open meetings to solicit community feedback on possible science algorithms, prepared preliminary draft Algorithm Theoretical Basis Documents (ATBDs) for each mission science product, and established a prototype algorithm testbed to enable testing and evaluation of the performance of candidate algorithms. SMAP conducted an Applications Workshop in September 2009 to coordinate with potential application users interested in the mission data. A draft Applications Plan describing the Project s planned outreach to potential applications users has been prepared and will be updated during Phase B. SMAP made a significant evaluation of the potential terrestrial radio frequency interference (RFI) source environment and established radiometer and radar flight hardware and ground processing mitigation approaches. SMAP finalized its science orbit and orbit injection approach to optimize launch mass and prepared launch and commissioning scenarios and timeline. A science data communications approach was developed to maximize available science data volume to improve science margins while maintaining moderately short data product latencies to support many potential applications using existing ground assets and with minimum impact to the flight system. SMAP developed rigid multi-body and flexible body dynamics and control models and system designs for the 6-meter rotating instrument reflector-boom assembly (RBA) and flight system to confirm pointing and control performance, and devised strategies to efficiently implement on-orbit balancing if needed. Industry partners were selected for the spin mechanism assembly (SMA) and RBA. Preliminary designs for the radar and radiometer were initiated, including constructing breadboards of key assemblies.

Kellogg, Kent↗

Quantification of Uncertainty and Risk Sensitivity for Safety of Emerging Operations

The growing need to develop and deploy small unmanned aerial vehicles (sUAVs) for various applications in the airspace necessitates reliable tools to accurately predict the flight trajectories of the sUAVs. The knowledge of the predicted trajectories help decision makers anticipate potential conflict, assess the risk, and take appropriate risk mitigation actions. In addition, uncertainties in vehicle models, weather, and controller action further highlights the need for reliable prediction tools. In this project, the application of mixed sparse grid-based quadrature and generalized polynomial chaos(gPC) expansion method for uncertainty quantification and collision assessment in air traffic consisting of fixed-wing small unmanned aerial vehicles (sUAV) was studied. From the results obtained, it can be concluded that this provides a reliable framework to carry out quantitative conflict assessment in an unmanned air traffic, which when employed, can improve the functionalities of the unmanned traffic management system. It was observed that the results from the gPC expansion framework developed in the project can be utilized to conduct rapid probabilistic collision assessment for near real-time unmanned traffic management in the airspace. From the vehicle models, position updates, and wind-field data, a priori gPC based 3-σcon-fidence ellipses can provide estimates of potential conflict at some future instants. The computational costs scaled linearly when the uncertain inputs were fewer. Further, the largest allowable distribution of para-metric uncertainties that leads to the smallest risk of collision in traffic of small unmanned aerial vehicles could be calculated. The time of closest approach between two sUAVs can be established paving way for development of proactive mitigation strategies. The separation between the sUAVs was found to be most significantly affected by uncertainties in the maximum available thrusts, zero-lift drag coefficients, and wing planform areas of the sUAVs. The study of uncertain wind-fields indicated that a heterogeneous traffic mix resulted in an increased probability of conflict. Increased measurement update rate reduced the uncertain-ties in the trajectories of the vehicles, further reducing the probability of conflict but rapid updates of all vehicles in the airspace poses a stringent communication limitation. The gPC framework also provided the means to analyze vehicle impact (crash region) due to loss of control resulting from actuator failure in sUAS traffic, essentially to predict impact and crash zones for representative vehicles. The predicted regions when compared with non-participant density, provides a means to develop an early mitigation strategy, should the sUAV detect an imminent actuator failure.

Rajnish Bhusal↗

Algorithms for Learning Preferences for Sets of Objects

A method is being developed that provides for an artificial-intelligence system to learn a user's preferences for sets of objects and to thereafter automatically select subsets of objects according to those preferences. The method was originally intended to enable automated selection, from among large sets of images acquired by instruments aboard spacecraft, of image subsets considered to be scientifically valuable enough to justify use of limited communication resources for transmission to Earth. The method is also applicable to other sets of objects: examples of sets of objects considered in the development of the method include food menus, radio-station music playlists, and assortments of colored blocks for creating mosaics. The method does not require the user to perform the often-difficult task of quantitatively specifying preferences; instead, the user provides examples of preferred sets of objects. This method goes beyond related prior artificial-intelligence methods for learning which individual items are preferred by the user: this method supports a concept of setbased preferences, which include not only preferences for individual items but also preferences regarding types and degrees of diversity of items in a set. Consideration of diversity in this method involves recognition that members of a set may interact with each other in the sense that when considered together, they may be regarded as being complementary, redundant, or incompatible to various degrees. The effects of such interactions are loosely summarized in the term portfolio effect. The learning method relies on a preference representation language, denoted DD-PREF, to express set-based preferences. In DD-PREF, a preference is represented by a tuple that includes quality (depth) functions to estimate how desired a specific value is, weights for each feature preference, the desired diversity of feature values, and the relative importance of diversity versus depth. The system applies statistical concepts to estimate quantitative measures of the user s preferences from training examples (preferred subsets) specified by the user. Once preferences have been learned, the system uses those preferences to select preferred subsets from new sets. The method was found to be viable when tested in computational experiments on menus, music playlists, and rover images. Contemplated future development efforts include further tests on more diverse sets and development of a sub-method for (a) estimating the parameter that represents the relative importance of diversity versus depth, and (b) incorporating background knowledge about the nature of quality functions, which are special functions that specify depth preferences for features.

Wagstaff, Kiri L.↗

VIIP 2017 Clinical Update

INTRODUCTION: NASA's Space Medicine community knowledge regarding the "Vision Impairment Intracranial Pressure", or VIIP.has been evolving over time.. Various measures of occupational health related to this condition had to be determined and then plans/processes put into place. The most robust of these processes were inititated in 2010. This presentation will provide a clinic update of the astronaut occupational health data related to VIIP. METHODS: NASA and its international partners require its astronauts to undergo routine health measures deemed important to monitoring VIIP. The concern is that the spaceflight environment aboard ISS could cause some astronauts to have physiologic changes detrimental to either ongoing mission operations or long-term health related to the ocular system and possibly the CNS. Specific medical tests include but are not limited to brain/orbit MRI (NASA unique protocol), OCT, fundoscopy and ocular ultrasound. Measures are taken prior to spaceflight, in-flight and post-flight. Measures to be reported include incidence of disc edema, globe flattening, choroidal folds, ONSD and change in refractive error. RESULTS: 73 ISS astronauts have been evaluated at least partially for VIIP related measures. Of these individuals, approximately 1 in 7 have experienced disc edema. The prevalence of the other findings is more complicated as the medical testing has changed over time. Overall, 26 separate individuals have experienced at least one of the findings NASA has associated with VIIP Another confounding factor is most of the astronauts have prior spaceflight experience at the time of the "pre-flight" testing. DISCUSSION: In 2010 NASA and its US operating segment (USOS) partners (CSA, ESA and JAXA) began routine occupational monitoring and data collection for most VIIP related changes. Interpretation of that data is extremely challenging for several reasons. For example, the determination of disc edema is the most complete finding as we have had highly qualified optometrists routinely and competently performing post-flight funduscopic exams for the entirety of the ISS program. Yet in 2013 NASA added OCT to our in-flight suite of eye exams. Shortly after routine screening with the OCT, a new term appeared within VIIP vernacular - "subclinical disc edema". OCT has much greater ability to measure change within the retina and provides significantly more data to analyze, understand and communicate out. Communicating VIIP data clearly adds even more challenge. Historically we've reported data per eye and not necessarily per person. This has led to difficulty in understanding how many individuals have experienced "VIIP" within the aerospace medicine community. The presenter will attempt to provide clear and concise communication of VIIP findings.

Tarver, William↗

Basic and clinical immunology

Progress in immunology continues to grow exponentially every year. New applications of this knowledge are being developed for a broad range of clinical conditions. Conversely, the study of primary and secondary immunodeficiencies is helping to elucidate the intricate mechanisms of the immune system. We have selected a few of the most significant contributions to the fields of basic and clinical immunology published between October 2001 and October 2002. Our choice of topics in basic immunology included the description of T-bet as a determinant factor for T(H)1 differentiation, the role of the activation-induced cytosine deaminase gene in B-cell development, the characterization of CD4(+)CD25(+) regulatory T cells, and the use of dynamic imaging to study MHC class II transport and T-cell and dendritic cell membrane interactions. Articles related to clinical immunology that were selected for review include the description of immunodeficiency caused by caspase 8 deficiency; a case series report on X-linked agammaglobulinemia; the mechanism of action, efficacy, and complications of intravenous immunoglobulin; mechanisms of autoimmunity diseases; and advances in HIV pathogenesis and vaccine development. We also reviewed two articles that explore the possible alterations of the immune system caused by spaceflights, a new field with increasing importance as human space expeditions become a reality in the 21st century.

Review↗

NASA System Safety Handbook: System Safety Framework and Concepts for Implementation - Volume 1

System safety assessment is defined in NPR 8715.3C, NASA General Safety Program Requirements as a disciplined, systematic approach to the analysis of risks resulting from hazards that can affect humans, the environment, and mission assets. Achievement of the highest practicable degree of system safety is one of NASA's highest priorities. Traditionally, system safety assessment at NASA and elsewhere has focused on the application of a set of safety analysis tools to identify safety risks and formulate effective controls.1 Familiar tools used for this purpose include various forms of hazard analyses, failure modes and effects analyses, and probabilistic safety assessment (commonly also referred to as probabilistic risk assessment (PRA)). In the past, it has been assumed that to show that a system is safe, it is sufficient to provide assurance that the process for identifying the hazards has been as comprehensive as possible and that each identified hazard has one or more associated controls. The NASA Aerospace Safety Advisory Panel (ASAP) has made several statements in its annual reports supporting a more holistic approach. In 2006, it recommended that "... a comprehensive risk assessment, communication and acceptance process be implemented to ensure that overall launch risk is considered in an integrated and consistent manner." In 2009, it advocated for "... a process for using a risk-informed design approach to produce a design that is optimally and sufficiently safe." As a rationale for the latter advocacy, it stated that "... the ASAP applauds switching to a performance-based approach because it emphasizes early risk identification to guide designs, thus enabling creative design approaches that might be more efficient, safer, or both." For purposes of this preface, it is worth mentioning three areas where the handbook emphasizes a more holistic type of thinking. First, the handbook takes the position that it is important to not just focus on risk on an individual basis but to consider measures of aggregate safety risk and to ensure wherever possible that there be quantitative measures for evaluating how effective the controls are in reducing these aggregate risks. The term aggregate risk, when used in this handbook, refers to the accumulation of risks from individual scenarios that lead to a shortfall in safety performance at a high level: e.g., an excessively high probability of loss of crew, loss of mission, planetary contamination, etc. Without aggregated quantitative measures such as these, it is not reasonable to expect that safety has been optimized with respect to other technical and programmatic objectives. At the same time, it is fully recognized that not all sources of risk are amenable to precise quantitative analysis and that the use of qualitative approaches and bounding estimates may be appropriate for those risk sources. Second, the handbook stresses the necessity of developing confidence that the controls derived for the purpose of achieving system safety not only handle risks that have been identified and properly characterized but also provide a general, more holistic means for protecting against unidentified or uncharacterized risks. For example, while it is not possible to be assured that all credible causes of risk have been identified, there are defenses that can provide protection against broad categories of risks and thereby increase the chances that individual causes are contained. Third, the handbook strives at all times to treat uncertainties as an integral aspect of risk and as a part of making decisions. The term "uncertainty" here does not refer to an actuarial type of data analysis, but rather to a characterization of our state of knowledge regarding results from logical and physical models that approximate reality. Uncertainty analysis finds how the output parameters of the models are related to plausible variations in the input parameters and in the modeling assumptions. The evaluation of unrtainties represents a method of probabilistic thinking wherein the analyst and decision makers recognize possible outcomes other than the outcome perceived to be "most likely." Without this type of analysis, it is not possible to determine the worth of an analysis product as a basis for making decisions related to safety and mission success. In line with these considerations the handbook does not take a hazard-analysis-centric approach to system safety. Hazard analysis remains a useful tool to facilitate brainstorming but does not substitute for a more holistic approach geared to a comprehensive identification and understanding of individual risk issues and their contributions to aggregate safety risks. The handbook strives to emphasize the importance of identifying the most critical scenarios that contribute to the risk of not meeting the agreed-upon safety objectives and requirements using all appropriate tools (including but not limited to hazard analysis). Thereafter, emphasis shifts to identifying the risk drivers that cause these scenarios to be critical and ensuring that there are controls directed toward preventing or mitigating the risk drivers. To address these and other areas, the handbook advocates a proactive, analytic-deliberative, risk-informed approach to system safety, enabling the integration of system safety activities with systems engineering and risk management processes. It emphasizes how one can systematically provide the necessary evidence to substantiate the claim that a system is safe to within an acceptable risk tolerance, and that safety has been achieved in a cost-effective manner. The methodology discussed in this handbook is part of a systems engineering process and is intended to be integral to the system safety practices being conducted by the NASA safety and mission assurance and systems engineering organizations. The handbook posits that to conclude that a system is adequately safe, it is necessary to consider a set of safety claims that derive from the safety objectives of the organization. The safety claims are developed from a hierarchy of safety objectives and are therefore hierarchical themselves. Assurance that all the claims are true within acceptable risk tolerance limits implies that all of the safety objectives have been satisfied, and therefore that the system is safe. The acceptable risk tolerance limits are provided by the authority who must make the decision whether or not to proceed to the next step in the life cycle. These tolerances are therefore referred to as the decision maker's risk tolerances. In general, the safety claims address two fundamental facets of safety: 1) whether required safety thresholds or goals have been achieved, and 2) whether the safety risk is as low as possible within reasonable impacts on cost, schedule, and performance. The latter facet includes consideration of controls that are collective in nature (i.e., apply generically to broad categories of risks) and thereby provide protection against unidentified or uncharacterized risks.

Dezfuli, Homayoon↗

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

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

Crew Performance Support System to Aid in Anomaly Resolution: Concept of Operations

As missions progress into deep space, communication delays and disruptions will disenable the crew’s reliance on Earth experts. There are also limitations in the amount of data that can be downlinked to the ground. It is prudent to assume that critical, complex vehicle or habitat sub-systems will malfunction at a time when a lunar or Mars’ crew cannot rely on the Earth-Support team to detect, diagnose and resolve the problem and it is impractical to expect a small crew to step-in with the same level of expertise as 50+ authorities. The crew will need novel processes and advanced technological support to independently identify and resolve safety- and time-critical anomalies. That a self-reliant crew is unable to respond appropriately to time-critical anomalies is a significant risk to crew safety and mission success. This risk is driven by several factors; novel and unanticipated anomalies would not have been trained pre-flight, the crew could forget their pre-flight training or spaceflight stressors could impair the crew’s problem-solving ability. At last year’s IWS, Beard reported that a single spaceflight stressor (elevated CO2) could undermine the crew’s ability to independently respond to emergencies. Concept of Operations (ConOps) provide a common view of future system functions to all stakeholders. For the current project, a ConOps was developed that describes the operational processes, practices and capabilities needed by a crew of astronauts on deep space missions to autonomously respond to anticipated and unanticipated anomalies. It is crucial to recognize that, as of August 2018 existing technologies are unable to effectively support crew anomaly response to unanticipated events. “Intelligent technology” has not reached a maturity level that permits generalizing a solution to novel situations. For example, to train intelligent technology requires volumes of data that do not exist. The complexities involved in a manned mission to Mars cannot be compared to sending rovers to Mars using scripted software. This ConOps proposes a Crew Performance Support System (CPSS) that will push NASA and its industry partners toward what will be required for a safe and successful manned mission to Mars. Anomaly resolution during a deep space mission will take place within a dynamic, or changing, context. The figure to the left shows five broad contextual variables: the organizational culture, mission context, system characteristics, team characteristics and individual characteristics. The yellow arrow indicates that spaceflight and task-related stressors can affect system, team and individual crewmember characteristics and therefore anomaly response potential. The figure depicts a protective umbrella of Human-System Integration (HSI) principles that should be instituted during CPSS development including a balanced workload, shared situation awareness and building an appropriate level of trust in the automation. The figure also depicts two interrelated and cooperative components, an HSI Data System and other Enabling Capabilities will be required to support crew anomaly response and Earth-Support situation awareness. As we journey from ISS to Gateway to Mars, multiple, simultaneous and integrated research and development efforts (i.e., support systems co-evolution) must be implemented to meet the problem-solving challenges a self-reliant crew will face on a Mars’ mission. The crossovers between the capabilities are just as important as the discrete capabilities themselves. As the capabilities mature, the lines between the support subdomains will blur and an integrated system will emerge. The ConOps summarizes current knowledge about how highly trained people solve anomalies in safety- and time-critical situations, describes a group of capabilities that could help to reduce the extant risk and documents requirements levied on additional systems that provides critical inputs to the CPSS. Scenarios are used to promote a shared understanding of processes, practices and technological goals needed for safe and productive manned missions beyond LEO.

HSIA risk↗

Harnessing Artificial Intelligence for Medical Diagnosis and Treatment During Space Exploration Missions

From May 8th to June 9th, 2023, I had the opportunity to participate in an experiential learning experience at Johnson Space Center in Houston, TX with Exploration Medical Capability (ExMC), an element of the NASA Human Research Program. During this research experience, I was not only able to work on the above titled research project, but also gain an immense exposure to the field of aerospace medicine, make numerous connections within the field, tour NASA facilities, as well as travel to the Aerospace Medical Association Annual Conference (AsMA) in New Orleans. To briefly introduce my project, it is well understood that the medical capabilities available to crew medical officers (CMOs) on the International Space Station will be different than the capabilities available and needed during deep space exploration missions to the Moon, Mars, and beyond. Ground support is particularly limited due to distance, communication delays (or lack of communication), and lack of resupply. Therefore, to support medical care by CMOs on these missions, robust clinical decision support systems (CDSSs) must be designed. The recent publication and public launch of generative artificial intelligence (AI) tools based upon large language models (LLM) such as ChatGPT provides the opportunity to create a smart assistant for onboard triage, diagnosis, and treatment of medical conditions. Ultimately, the overall purpose of the project was to research what AI tools currently exist or are in development, and to see how they might be implemented onboard during exploration class spaceflights of the future. The ExMC element is actively developing several tools to be used in preparation for and during deep space exploration missions. One of those tools, known as IMPACT, is a probabilistic risk assessment model which can be used to propose a desired medical system (based on mass and volume) and suggest the clinical outcomes likely to occur for a design reference mission (DRM). The group recently presented the IMPACT model and a DRM of interest titled “Modified Long Duration Lunar Orbital and Lunar Surface” (mLDLOLS) at the recent AsMA conference. The mLDLOLS mock mission is a 9 month and 6-day deep space exploration mission consisting of time in Moon’s orbit (3 months on the Gateway space station), on the lunar surface (3 months within habitat), and another 3 months on Gateway before return to Earth. For this DRM, IMPACT ultimately outlined a preferred medical system that was then associated with medical conditions considered to be most likely based on frequency, most likely to cause astronaut task time loss (TTL), most likely to cause return to definitive care (RTDC), and most likely cause loss of crew life (LOCL). IMPACT also highlighted the medical capabilities/skills that would be required to care for those medical conditions, such as performing a history of present illness or musculoskeletal exam with ultrasound. The primary objective of the project was to perform a survey of the AI tools and systems applicable to the conditions outlined for the proposed mLDLOLS mission. Using PubMed (including most relevant MeSH terms) and Google Scholar, we then created a robust annotated bibliography organized by condition. The 56-page and over 500 reference annotated bibliography was subsequently used to create a review outline that would become the basis for drafting of a future publication. For the review outline, we took those medical conditions researched within the annotated bibliography (condition-based approach) and deployed a systems-based approach, combining those medical conditions and related tools into ten categories. These categories included general/all-purpose CDSSs, tools to diagnose or manage respiratory, dermatologic, neurologic, auditory and vestibular, ophthalmic, musculoskeletal, infection-associated, and gynecologic conditions, as well as tools that could be deployed in the setting of trauma/emergency. With the completion of the 30-page outline, we then began drafting the review paper. To conclude the research experience, I presented the findings from our survey to the ExMC Clinical and Science team. With these objectives, I ultimately learned about the number of AI tools that exist today to assist medical professionals with the triage, diagnosis, and management of several medical conditions. These tools can span from chatbot assistants to help triage knee pain to vision transformer models that can identify ophthalmic conditions based on ocular surface images captured with a cell phone. We also highlighted the current gaps that exist in the literature alongside the advancements that are needed to make the desired CDSS for deep space exploration missions. With this experience, I certainly confirmed an existing career goal and identified several additional skills needed to become an aerospace medical doctor including knowledge of critical care in an extreme medicine setting, aerospace engineering and human integration systems, artificial intelligence, machine learning, and risk models. I also identified numerous transferable skills for this career goal including the basic knowledge of medicine (MD), deployment of the scientific method for critical thought about new scientific questions (PhD), review of published literature, including creating an annotated bibliography (PhD), as well as detailed scientific writing (PhD). The results of my research will likely guide the design of an all-encompassing onboard medical assistant for use during deep space exploration missions of the future. I plan on sharing the outcomes from this experience with my peers at a student seminar in the Fall semester on August 30th. During the seminar, I will detail the project, my experience at NASA and AsMA, as well as offer best practice guidelines for students entertaining similar experiences or careers. In conclusion, I would like to thank the WVU School of Medicine, Research and Graduate Education office, as well as NASA ExMC for the unwavering support of this life-changing experience.

Ryan A. Lacinski↗