Search

More inclusive open science can help solve society’s most pressing problems—and at a faster pace—but making it mainstream requires systemic institutional change.

This report describes work performed on Contract NAS3–27720 AoI 13 as part of the NASA Advanced Subsonic Transport (AST) Noise Reduction Technology effort. Computer codes were developed to provide quantitative prediction, design, and analysis capability for several aircraft engine noise sources. The objective was to provide improved, physics-based tools for the exploration of noise-reduction concepts and the understanding of experimental results. Methods and codes focused on fan broadband and “buzz saw” noise and on low-emissions combustor noise and complement work done by other contractors under the NASA AST program to develop methods and codes for fan harmonic tone noise and jet noise. The methods and codes developed and reported herein employ a wide range of approaches, from the strictly empirical to the completely computational, with some being semiempirical, analytical, and/or analytical/computational. Emphasis was on capturing the essential physics while still considering method or code utility as a practical design and analysis tool for everyday engineering use. Codes and prediction models were developed for: (1) an improved empirical correlation model for fan rotor exit flow mean and turbulence properties, for use in predicting broadband noise generated by rotor exit flow turbulence interaction with downstream stator vanes; (2) fan broadband noise models for rotor and stator/turbulence interaction sources including 3D effects, noncompact-source effects, directivity modeling, and extensions to the rotor supersonic tip-speed regime; (3) fan multiple-pure-tone in-duct sound pressure prediction methodology based on CFD analysis; and (4) low-emissions combustor prediction methodology and computer code based on CFD and actuator disk theory. In addition, the relative importance of dipole and quadrupole source mechanisms was studied using direct CFD source computation for a simple cascade/gust interaction problem, and an empirical combustor-noise correlation model was developed from engine acoustic test results. This work provided several insights on potential approaches to reducing aircraft engine noise. Code development is described in Volume I, and those insights are discussed. Volume II documents the computer codes developed and gives instructions on how to use them.

These Data Release Notes provide information on the processing and export of data from the Transiting Exoplanet Survey Satellite (TESS). The data products included in this data release are full frame images (FFIs), target pixel files, light curve files, collateral pixel files, cotrending basis vectors (CBVs), and Data Validation (DV) reports, time series, and associated xml files.

These Data Release Notes provide information on the processing and export of data from the Transiting Exoplanet Survey Satellite (TESS). This data release is a combined, multi-sector transit search only. The underlying data products from individual observing sectors have been previously released. The data products included in this data release are the Data Validation (DV) reports, time series, and associated xml files for the threshold crossing events (TCEs) found by searching a combined data set including data from multiple observing sectors.

These Data Release Notes provide information on the processing and export of data from the Transiting Exoplanet Survey Satellite (TESS). This data release is a combined, multi-sector transit search only. The underlying data products from individual observing sectors have been previously released. The data products included in this data release are the Data Validation (DV) reports, time series, and associated xml files for the threshold crossing events (TCEs) found by searching a combined data set including data from multiple observing sectors

The Information Fusion & Data Analytics (IFDA) project commenced in FY20, continued through FY21, and its final platform development phase continues in FY22. The objective remains the fusion and rapid accessibility of large quantities of disparate sourced human spaceflight data. IFDA is a platform tailored for NA (S&MA) to develop highly advanced operational data integration and analysis techniques. IFDA leverages the JSC ER7 modeling, simulation,and data fusion capabilities to collect, warehouse, and augment data human exploration data integration and analysis techniques. The IFDA project’s integrated data visualizations have been demonstrated in two validation scenarios in FY21, and provided the architecture and platform basis for development of a full-scale data analysis suite and storage solution useful to all JSC organizations engaged in real time operations and safety tasks. Scenarioand prototypical development including the construction of a full scale data analysis suite and storage solution, useful to all JSC organizations engaged in real time operations and safety tasks, is central to IFDA Phase 3 and provides a demonstrable pathway for the Digital Transformation Program. IFDA Phase 3 is focused on data provider, data utilizer, and SME hands-on workshops that will conclude the Dem / Valphase and deliver a program-ready data integration tool as a product.

The NASA Orbital Debris Engineering Model (ORDEM) 3.1 Model Verification and Validation (V&V) document accompanies the delivery of the latest ORDEM 3.1 model (Vavrin & Manis, 2019) and provides a detailed description of the V&V activities used to verify that the model was built correctly and validate the model against independent, real world sources of data obtained from sampling the orbital debris environment. This ORDEM 3.1 Model V&V document, along with the related ORDEM 3.1 Model Process document – which covers details of the mathematical, statistical, and physical basis of the model – are intended to inform credibility assessments, risk analyses, uncertainty characterizations, and other applications derived from use of the model by the ORDEM 3.1 user community.

The 2021 Marshall Faculty Fellowship Program involved 4 faculty virtually working in the laboratories and departments at Marshall Space Flight Center. These faculty engineers and scientists worked with NASA collaborators on NASA projects, bringing new perspectives and solutions to bear. This Technical Memorandum is a compilation of the research reports of the 2021 Marshall Faculty Fellowship program, along with the Program Announcement (Appendix A) and the Program Description (Appendix B).

According to the World Health Organization (WHO), vector-borne diseases such as malaria and dengue account for 17% of all infectious disease cases and lead to more than 700,000 deaths per year. Tracking and predicting the spread of vector-borne diseases is a vital task that could save hundreds of thousands of lives annually. Oftentimes, the first reports of vector-borne disease outbreaks occur through emails and online reporting systems long before they are officially documented. Tracking and predicting the emergence and spread of vector-borne disease outbreaks requires extracting data from these unstructured sources in combination with historical weather and climate data to understand the underlying background triggers and disease dynamics. In this work, we develop a data extraction pipeline for the online outbreak reporting website ProMED-mail that utilizes a web scraper, transformer neural network summarizer, and named entity recognizer to obtain a dataset of malaria, dengue, zika, and chikungunya outbreaks over the last 30 years. This scraped dataset was further analyzed in association with global rainfall anomalies derived from NASA’s Integrated Multi-satellitE Retrievals for GPM [Global Precipitation Mission] (IMERG) dataset. This preliminary analysis was to understand the effect of global rainfall patterns on the spread of vector-borne diseases. Analysis of the ProMED-mail and GPM data shows that vector-borne disease outbreaks are clustered towards the tropics and outbreaks are often amplified during the rainy seasons. Our scraped dataset can be a valuable tool in creating comprehensive georeferenced disease records for modeling and predicting future outbreaks.

The purpose of this handbook is intended to be a how-to guide to prepare for, conduct, and close-out an Integrated Baseline Review (IBR). It discusses the steps that should be considered, describes roles and responsibilities, tips for tailoring the IBR based on risk, cost, management insight benefits, and provides lessons learned from past IBRs. The appendices contain example documentation typically used in connection with an IBR. Note: Appendices are examples only, and should be tailored to meet the needs of individual projects and contracts. Following the guidance in this handbook will help customers and suppliers preparing for an IBR understand the expectations of the IBR, and ensure that the IBR meets the requirements for both in-house and contract efforts.

The purpose of this Earned Value Management (EVM) System Description is to provide guidance in NASA’s Earned Value Management Capability for the effective application, implementation, and utilization of EVM on NASA programs, projects, major contracts and subcontracts. EVM is a project management process that effectively integrates a project’s scope of work with schedule and cost elements for optimum project planning and control. The goal is to achieve timely and accurate quantification of progress that will facilitate management by exception and enable early visibility into the nature and the magnitude of technical problems as well as the intended course and success of corrective actions. This system description contains detailed information on implementation of EVM processes, procedures, roles and responsibilities.

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for WBS and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule and budget development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

The purpose of this guide is intended to be a quick reference for a Project-Control Account Manager (P-CAM) or technical manager empowered with a project’s cost, schedule, and technical responsibilities of a control account(s) when Earned Value Management (EVM) is required. The overall objective is to support the P-CAM in performing their responsibilities as they relate to EVM. In addition, the reference guide describes at a summary level how the scope, schedule, and budget of a project integrate for optimal planning and control of prime contracts and in-house projects. Because NASA implements a diverse and unique portfolio of projects, those projects have traditionally created project-specific systems to manage planning and performance analysis. However, establishment and implementation of a project management system that is common across all centers and mission directorates will facilitate the adoption of best business practices. In addition, the application of timely and predictive analysis, as well as, providing all stakeholders with greater insight into project performance will enhance opportunities for project success. For more detailed information, refer to the NASA EVM System Description; Integrated Baseline Review (IBR) Handbook; EVM Implementation Handbook; Schedule Management Handbook; Work Breakdown Structure (WBS) Handbook; and other agency/industry documentation. In addition, you may contact your local center’s EVM Focal Points. All this information and more can be found at and/or the NASA Engineering Network located at https://nen.nasa.gov/web/pm.

Words matter—that old adage that many of us may have heard as children, Sticks and stones may break my bones, but words will never hurt me, is a harmful fallacy. In reality, the language we use has tremendous power to alienate, exclude, deride, humiliate, and wound. On the other hand, thoughtful use of language can signal openness, inclusivity, admiration, and celebration, or simply be an expression of empathy and care for our fellow humans. As part of The Oceanography Society (TOS) Justice, Equity, Diversity, and Inclusion Committee’s series of columns in Oceanography, here we provide a glossary of terms that are often used while discussing topics such as race, ethnicity, gender, sexual orientation, and gender identity. It should be explicitly stated that this list is neither definitive nor exhaustive. Indeed, the terms included here are likely heavily influenced by the authors’ own lived experiences and the lenses through which we see the world. Language is a living entity, a fluid social construct subject to rapid changes and overlaid with regional nuances. Indeed, what may be accurate and acceptable terminology for one person may be entirely unacceptable for another. Keeping this in mind, the following glossary is an attempt to group together some of the acronyms and phrases that are most commonly used today in social justice studies and bodies of work and that may have particular relevance to our community of ocean-related scientists, technologists, and stakeholders. We have borrowed heavily from a wide range of excellent existing scholarship and activism and have cited all sources used. We encourage the reader to follow the links to these multimedia resources and, perhaps, use them as teaching and discussion materials with your students, colleagues, and mentees. Finally, it is our hope that this glossary, along with the links provided to more comprehensive definitions and discussions, helps to define terms that you may have heard used, but not understood, and that it will serve to remind us of the power of the words we use in our everyday professional and personal lives. We begin by defining the very words that form the name of our committee: Justice, Equity, Diversity, and Inclusion (JEDI)

In the early history of life, RNA might have had many catalytic functions as ribozymes that do not exist today. To explore this possibility, catalytically active RNAs can be identified by in vitro selection experiments. Some of these experiments are best performed in nanodroplets to prevent diffusion between individual RNA sequences. In order to explore the suitability for the large-scale in emulsio selection of water-in-oil emulsions made by passing a mixture of mineral oil, the emulsifier ABIL-EM90, and a few percent of an aqueous phase through a microfluidizer, we used dynamic light scattering to characterize the size of aqueous droplets dispersed throughout the oil. We found that seven or more passes through the microfluidizer at 8000 psi with close to half molar inorganic salts and 10% polyethylene glycol produced droplets with sizes below 100 nm that were ideal for our purposes. We also identified conditions that would produce larger or smaller droplets, and we demonstrate that the emulsions are stable over weeks and months, which is desirable for different types of in vitro selection experiments.

The Spatio-Temporal Asset Catalog (STAC) specification provides a common language to describe a range of geospatial information, so it can more easily be indexed and discovered. A 'spatiotemporal asset' is any file that represents information about the earth captured in a certain space and time. STAC provides a standards-based, web and cloud friendly cataloging specification that has seen a large amount of adoption in the cloud geospatial information system space. This presentation will demonstrate how NASA EOSDIS leverages STAC technology to provide value-added features to both our data discovery and transformation services. Finally, we will propose a way to improve our federated discovery capabilities using STAC.

Established in 2017, the Microgravity Simulation Support Facility (MSSF) at NASA’s Kennedy Space Center is the only centralized, dedicated facility supporting ground microgravity research in the United States. The MSSF offers the research community the ability to conduct simulated microgravity research with experimental conditions functionally resembling those aboard the International Space Station (ISS) and in other flight-based experimental environments. Since its inception, the MSSF has supported numerous studies and has since collected an extensive library of relevant and pertinent literature. The goal of our research was to develop and implement a sustainable, user-friendly literature database to better house this literature at the MSSF. To achieve this, our team focused on sorting, optimizing, and analyzing preexisting literature libraries to determine a best suitable and sustainable platform for the MSSF. After establishing initial database platforms, the team worked to develop descriptive and structural metadata categories to best sort the literature, which was followed by rigorous testing and optimization of the database as it was implemented. The MSSF has now been outfitted with a reliable, accessible database that effectively houses literature and provides diverse analysis to the user. Our team is continuing to test and update our platform and parameters as we aim for the formal implementation, expansion, and evolution of our database to better sustain future research ventures at the MSSF and beyond.

Tutorial describing how to use NEQAIR v15.1 User Tutorial: NEQAIR was NASA’s first radiative heating code and has been the go-to-tool for 30+ years.

Crystal Ball is an application being developed that accesses multiple safety databases as a means to improve prediction of safety incidents. Year 1 was data integration, year 2 was predictive modeling, and then year 3(FY20), was the merging of those two prior year efforts into the final application, Crystal Ball (ssc.crystalball.insight.nasa.gov). Crystal Ball sits on the Insight platform (Insight is a NASA platform used to process, manage, integrate, analyze and visualize data at scale, insight.nasa.gov). InFY20, the project focus concentrated on the larger vision of Prediction of Safety Incidents using Crystal Ball as the data source. The Insight platform developer incorporated the predictive modeled data sets, and included a graphical user interface, resulting in a Dashboard for the Crystal Ball application; This application is a one-stop-shop for SMA employees working across data sets and provides a snapshot of current relative risk in different types of locations across the center. The ultimate goal is to have a tool that management can use to aid in decisions that are based on data already being collected. Ideally, the tool would highlight areas of increased risk for any given day. SMA will be conducting case studies to further refine the process of identifying higher areas of risk and potentially strategically direct resources where needed more. Our partners who leveraged funds for this project may consider use at other NASA organizations.

This NASA technical standard provides uniform engineering and technical requirements for processes, procedures, practices, and methods that have been endorsed as standard for NASA facilities, programs, and projects, including requirements for selecting, applying, and designing hardware for manufacturability and reliability. This standard establishes NASA workmanship requirements, and clarifications, additions, and exceptions to requirements specified in NASA adopted industry consensus standards identified as required for use by NPR 8735.2, Hardware Quality Assurance Program Requirements for Programs and Projects

This project leverages the Concept Exploration Laboratory (CEL) to collect, warehouse, and augment data relevant to human lunar exploration as a platform for NA (S&MA) to develop operational data integration techniques. The project capitalizes on 16+ years of CEL experience applied to NASA, DoD, the City of Houston, the State of Texas, and private industry. The integrated data will be utilized in the two scenarios described in a definition of concept for development of a full scale data analysis suite and storage solution, useful to all JSC organizations engaged in real time operations and safety tasks, and may be useful as pathfinders for the Digital Transformation Program.

This report details the process of document management within the KSC Integration Office throughout my internship in the fall term of the year 2020. During this term, I was mentored by Felix A. Soto-Toro and my main objective was to support the Audit Liaison Representatives (ALR) in their documentation processes. I worked alongside the members of the KSC Integration Office to streamline the auditing process in order to facilitate the interchangement of documents and communication between auditors and our agency. My approach to this situation was to document the events of each audit in a report, which would be updated weekly every Monday following a specific format. As support I was required to gather, organize, and release data relevant to current audits in an online server for ALRs to use across the entire NASA Agency.

I worked as a NASA OSTEM virtually during the Fall 2020 term. Working in the IT division under my mentor Dr. Ali Shaykhian, our overall goal for the duration of this internship is to get a better understanding of the Visual Basic Language and how it can be used to make forms and collaboration with other workers to be more dynamics. I also worked with 3 other interns throughout this internship, using Microsoft Office to help each other to get a better understanding of how we approached our projects individually. Every week, my mentor Dr. Ali assigned me a task and a goal to finish by the end of each week. My overall project was figuring out a way to make email submissions and emails in general more dynamic for the NASA database. For example, instead of only using the same generic email for hundreds of different workers, a code can be used to send an individual email with more personalization such as each recipient’s name and personal info. I have also been assigned to create an email graphical user interface by the end of this internship. For these tasks to be made possible, I had to learn more about the capabilities of Microsoft Office, such as Macros in Microsoft Excel and Visual Basic in both Microsoft Excel and Word. Although it was challenging at first, I developed new programming skilled in a new language and actually made it possible to create this code along the way. Alongside doing the individual assignments, Dr. Ali also assigned up to replicate other intern’s work to get a better understanding of their approach and learn how to do it ourselves.

NASA's Integrated Demand Management research activity developed a concept for a novel use of the FAA's Collaborative Trajectory Options Program (CTOP) decision support software to support a particular type of traffic management use case. The research team used an emulation of CTOP software to prototype and test the concept, and developed several enhancements to the CTOP user interface that were well received by the stakeholder community. This document provides a detailed description of these enhancements and their operation that could be used to support their incorporation into the official CTOP software.

TRACLabs’ PRIDE software was the first collaborative and highly-customizable tool designed to allow astronauts to document and mark progress on procedures in real-time, display system data, and issue commands—all from a single application. The versatility of the software caught the eye of a major oil field service company, who bought licenses and support from TRACLabs for $3.3M

NASA’s missions, engineering accomplishments, and scientific findings have inspired generations and advanced our understanding of the world we live in. NASA’s Earth science data are acquired by various sources, including satellites, aircraft, and field measurements. Captured data, their by-products, and their visual representations developed by research teams become available within few hours after satellite overpass or processing through a variety of NASA’s imaging, mapping services, and portals. Such online services as the Global Imagery Browse Services (GIBS), Worldview, LANCE, and LAADS DAAC are freely and openly available thanks to NASA’s Earth-Observing Satellite Data and Information Systems (EOSDIS). These services provide access to products created over the last 30 years, support a broad range of users from the scientific community to the general public, and cover a multitude of applications such as basic and applied scientific research, natural hazard and disaster monitoring, and social and educational outreach. In order to illustrate the significance of the overall work, the visualization products, and the broad range of users, we present three case studies: NASA’s Black Marble Product Suite, the Global Imagery Browse Services (GIBS) and Worldview, and the scientific visualization production process to communicate results to the scientific community and the general public.

CHIANTI is an atomic database and software package for modeling emission lines and continua from hot astrophysical plasmas. It is freely available to all researchers and has been widely used in the Heliophysics and Astrophysics communities for almost 25 years. In this review, we summarize the properties of the current version of the database and give an overview of the relevant atomic processes. We also discuss progress towards a complete implementation of collisional-radiative modeling, simultaneously solving for atomic level and ion populations for individual elements.

During the Summer 2020 session, I worked with intern Destani S. Van Arsdalen of EGS Software. Together, we co-created a tool to aid the dynamic investigation, updated over time,of the security compliance of LCS COTS and open source software. We originally planned touse spreadsheet software for management and analysis, but through this exploratoryproject, chose to use Python and JSON after receiving feedback on our project’s current anddesired capabilities at that time.At first, the project was solely designed to help on-board new COTS software, based on aquestionnaire that could be filled out for each software package. This, combined with usingthe spreadsheet application’s web-query capabilities to fetch information from the NVD,allowed presentation and analytics cells to automatically populate as elements of themanually-filled questionnaire changed. While this system was promising, we decided tochange technologies for a few reasons. In the spreadsheet, single cells could not hold complexdata like arrays and objects. The automatic population of cells and dynamic updates made itdifficult to manage and add new features. And finally, it had limited extensibility sinceadding new software required significant understanding of how both the spreadsheet wasconstructed, and the more obscure, proprietary scripting languages packaged with it.The pivot to a standard computer science database language of JSON, aided by thescripting capabilities of Python, greatly helped to improve the project’s functionality. First,and most importantly, the script’s import and analysis of database data is easilyreproducible. Additional data analysis can be modularly added without requiringmodification of the script and is capable of routine scheduling. The revised process can besplit into three parts. First, the conversion of LCS asset and software documentation into theJSON hierarchical database format. Second, the merging of this database with the NVD,forming a new data structure, using CPEs of the CVE object as a linking element betweenthem. And third, the automatically performed analytics and analysis of the combined data,in a modular and extensible format, to produce better informed business decisions. The outputted graphs, for example, are automatically generated by the Python script inconnection with the combined database. This allows updated graphs and any analytics to be re-rendered automatically following updates to the LCS’s initial asset documentation. Afinal report can then be programmatically and easily constructed from these sources to allow fully reproducible metrics for heavily evidenced risk management decisions.

The Apollo Lunar Surface Experiments Package (ALSEP) is the name used to collectively represent the geophysical instruments deployed on the lunar surface by the astronauts on Apollo 12, 14, 15, 16, and 17. These instruments were active from the times of their deployment (November 1969 – December 1972) to September 1977. During that time, fourteen types of experiments were conducted, and their data were transmitted to Earth. The experiment PIs processed them. At the conclusion of the experiments, some of these data were submitted to the NASA Space Science Data Coordinated Archive (NSSDCA) for archiving, while others were not. The raw instrument data received from the Moon prior to March 1976 were not archived, either. The unarchived data, resided on open-reel magnetic tapes, became lost in the decades since, along with much of the metadata (the information necessary/useful in properly processing/analyzing the data). This article retraces the history of the ALSEP data archiving efforts in the 1970s, the subsequent loss of the data tapes, and the search, recovery, and restoration of the lost data by contemporary researchers in the 21st century. In 2006, NSSDCA began reformatting some of the ALSEP data archived in the 1970s to conform with the current Planetary Data System (PDS). In 2010, 440 of the previously lost magnetic tapes containing the raw ALSEP data were recovered. From these tapes, the data were extracted, re-packaged for individual experiments, and, for those with sufficient metadata, processed into higher order data readily usable by researchers. All of these data products have been recently archived with either PDS or NSSDCA. These newly restored data fill a number of gaps in the previously existing archive of the ALSEP data. In addition, tens of thousands of pages of Apollo era documents have been optically scanned and compiled into an online searchable catalog. This article also describes the content, organization, and usage of the restored raw ALSEP data and metadata.

These Data Release Notes provide information on the processing and export of data from the Transiting Exoplanet Survey Satellite (TESS). The data products included in this data release are full frame images (FFIs), target pixel fi�les, light curve fi�les, collateral pixel fi�les, cotrending basis vectors (CBVs), and Data Validation (DV) reports, time series, and associated xml fi�les. These data products were generated by the TESS Science Processing Operations Center (SPOC, Jenkins et al., 2016) at NASA Ames Research Center from data collected by the TESS instrument, which is managed by the TESS Payload Operations Center (POC) at Massachusetts Institute of Technology (MIT). The format and content of these data products are documented in the Science Data Products Description Document (SDPDD). The SPOC science algorithms are based heavily on those of the Kepler Mission science pipeline, and are described in the Kepler Data Processing Handbook (Jenkins, 2019).2 The Data Validation algorithms are documented in Twicken et al. (2018) and Li et al. (2019). The TESS Instrument Handbook (Vanderspek et al., 2018) contains more information about the TESS instrument design, detector layout, data properties, and mission operations. The TESS Mission is funded by NASA's Science Mission Directorate.

This Implementation Work Plan (IWP) presents detailed design elements for the air sparging (AS) Interim Measure (IM) design provided in the IM Work Plan (IMWP) within the High Concentration Plume (HCP) at the Former Central Heat Plan (CHP) located at Kennedy Space Center (KSC), Florida. The IMWP presented an approach to implement an AS IM to reduce chlorinated volatile organic compound concentrations to concentrations that facilitate a transition to long-term monitoring. CHP has been designated Solid Waste Management Unit 045 under KSC’s Resource Conservation and Recovery Act Corrective Action Program.

This document provides guidelines for legal, policy, and ethical issues; standards for citizen science data collection and management; information on ensuring usability of citizen science data and communication regarding its use; and best practices for long-term archival of citizen science data.Section1 contains a detailed discussion of policy, ethical, and legal considerations influencing citizen science data collection. Section 2 considers standards for documentation, including documentation of instrumentation, procedures, and the data itself. It concludes with a discussion of how citizen science data should be attributed. Section 3 provides guidance about how to ensure citizen science data are collected and stored in a useable way. It also considers how NASA and data producers should notify the scientific community, including citizen scientists and the public, about citizen science datasets and the scientific conclusions reached using them. Finally, Section 4 provides detailed information regarding what should be archived from projects using a citizen science approach, including data and code. It provides guidance about archive location, process, and timeframe, as well as information about data access and distribution services provided by NASA that may be relevant to data producers working with citizen scientists.

In an engineering note published in the Journal of Aircraft in the year 2000, Thomas A. Zeiler made generally known that some of the early works on aeroelastic flutter by Theodore Theodorsen and I.E. Garrick (NACA Report Nos. 496, 685, and 741) contained numerical errors in some of their numerical examples. Some of the plots containing numerical errors were later reproduced in two classic aeroelasticity texts (BAH and BA). Because these foundational papers and texts are often used in graduate courses on aeroelasticity, Zeiler recommended that an effort be undertaken to employ the computational resources available today (digital computers) to recompute the example problems in these early works and to publish the results to provide a complete and error-free set of numerical examples. This paper presents recomputed theoretical results contained in NACA Report No. 685 (NACA 685), “Mechanism of Flutter, A Theoretical and Experimental Investigation of the Flutter Problem,” by Theodore Theodorsen and I.E. Garrick. The recomputations were performed employing the solution method described in NACA 685, but using modern computational tools. With some exceptions, the magnitudes and trends of the original results were in good-to-excellent agreement with the recomputed results, a surprising but gratifying result considering that the NACA 685 results were computed “by hand” using pencil, paper, slide rules, and mechanical calculators called comptometers. Checks on the recomputations (about 25% were checked) were performed using the so-called 𝑝𝑝-method of flutter solution. In all cases, including those where the original and recomputed results differed significantly, the checks were in excellent agreement with the recomputed results.

This users manual provides in-depth information concerning installation and execution of Laura, version 5. Laura is a structured, multiblock, computational aerothermodynamic simulation code. Version 5 represents a major refactoring of the original Fortran 77 Laura code toward a modular structure afforded by Fortran 95. The refactoring improved usability and maintainability by eliminating the requirement for problem-dependent recompilations, providing more intuitive distribution of functionality, and simplifying inter- faces required for multi-physics coupling. As a result, Laura now shares gas-physics modules, MPI modules, and other low-level modules with the Fun3D unstructured-grid code. In addition to internal refactoring, several new features and capabilities have been added, e.g., a GNU-standard installation process, parallel load balancing, automatic trajectory point sequencing, free-energy minimization, and coupled ablation and flow field radiation.

THREE is an encyclopedic website (http://three.jsc.nasa.gov) about the space radiation environment and its health risks to humans. The goal for the site is threefold: 1. to serve as a starting point for researchers new to either space, radiation, or both; 2. to serve as a source of useful information for established investigators; 3. to serve as a teaching tool for students; and, 4. to serve as a NASA reference source on all scientific aspects of space radiation and health. THREE is funded by the Space Radiation (SR) Element within NASA’s Human Research Program (HRP). The THREE Editorial Board is responsible for oversight of the content and policies for the website. The website is hosted by the NASA Johnson Space Center.

Loss of control inflight continues to be the leading contributor to airline accidents worldwide and unreliable airspeed has been a contributing factor in many of these accidents. Airlines and the FAA developed training programs for pilot recognition of these airspeed events and many checklists have been designed to help pilots troubleshoot. In addition, new aircraft designs incorporate features to detect and respond in such situations. NASA has been using unreliable airspeed events while conducting research recommended by the Commercial Aviation Safety Team. Even after significant industry focus on unreliable airspeed, research and other evidence shows that highly skilled and trained pilots can still be confused by the condition and there is a lack of understanding of what the associated checklist(s) attempts to uncover. Common mode failures of analog sensors designed for measuring airspeed continue to confound both humans and automation when determining which indicators are correct. This paper describes failures that have occurred in the past and where/how pilots may still struggle in determining reliable airspeed when confronted with conflicting information. Two latest generation aircraft architectures will be discussed and contrasted. This information will be used to describe why more sensors used in classic control theory will not solve the problem. Technology concepts are suggested for utilizing existing synoptic pages and a new synoptic page called System Interactive Synoptic (SIS). SIS details the flow of flight critical data through the avionics system and how it is used by the automation. This new synoptic page as well as existing synoptics can be designed to be used in concert with a simplified electronic checklist (sECL) to significantly reduce the time to configure the flight deck avionics in the event of a system or sensor failure.

To help users of the 2020 Taxonomy navigate changes from the 2015 Technology Area Breakdown Structure (TABS), this companion document provides a crosswalk between the 2015 Technology Areas (TAs) and the updated 2020 Taxonomy areas (TXs).