Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “dispositive”

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 505 records · Page 28

Considerations for the Next Revision of STRS

Development of NASAs Software Defined Radio architecture, the Space Telecommunication Radio System (STRS), was initiated in 2004 with a goal of reducing the cost, risk and schedule when implementing Software Defined Radios (SDR) for NASA space missions. Since STRS was first flown in 2012 on three Software Defined Radios on the Space Communication and Navigation (SCaN) Testbed, only minor changes have been made to the architecture. Multiple entities have since implemented the architecture and have provided significant feedback for consideration for the next revision of the standard. The focus for the first set of updates to the architecture is items that enhance application portability. Items that require modifications to existing applications before migrating to the updated architecture will only be considered if there is compelling reasons to make the change. The significant suggestions that were further evaluated for consideration include expanding and clarifying the timing Application Programming Interfaces (APIs), improving handle name and identification (ID) definitions and use, and multiple items related to implementation of STRS Devices. In addition to ideas suggested while implementing STRS, SDR technology has evolved significantly and this impact to the architecture needs to be considered. These include incorporating cognitive concepts - learning from past decisions and making new decisions that the radio can act upon. SDRs are also being developed that do not contain a General Purpose Module which is currently required for the platform to be STRS compliant. The purpose of this paper is to discuss the comments received, provide a summary of the evaluation considerations, and examine planned dispositions

waveforms↗

Bladed Terrain on Pluto: Possible Origins and Evolutions

Pluto's Bladed Terrain (centered roughly 20 deg N, 225 deg E) covers the flanks and crests of the informally named Tartarus Dorsa with numerous roughly aligned blade-like ridges oriented approx. North-South; it may also stretch considerably farther east onto the non-close approach hemisphere but that inference is tentative. Individual ridges are typically several hundred meters high, and are spaced 5 to 10 km crest to crest, separated by V-shaped valleys. Many ridges merge at acute angles to form Y-shape junctions in plan view. The principle composition of the blades themselves we suspect is methane or a methane-rich mixture. (Methane is spectroscopically strongly observed on the optical surfaces of blades.) Nitrogen ice is very probably too soft to support their topography. Cemented mixtures of volatile and non-volatile ices may also provide a degradable but relief supporting "bedrock" for the blades, perhaps analogous to Callisto. Currently we are considering several hypotheses for the origins of the deposit from which Bladed Terrain has evolved, including aeolian disposition, atmospheric condensation, updoming and exhumation, volcanic intrusions or extrusions, crystal growth, among others. We are reviewing several processes as candidate creators or sculptors of the blades. Perhaps they are primary depositional patterns such as dunes, or differential condensation patterns (like on Callisto), or fissure extrusions. Or alternatively perhaps they are the consequence of differential erosion (such as sublimation erosion widening and deepening along cracks), variations in substrate properties, mass wasting into the subsurface, or sculpted by a combination of directional winds and solar isolation orientation. We will consider the roles of the long-term increasing solar flux and short periods of warm thick atmospheres. Hypotheses will be ordered based on observational constrains and modeling to be presented at the conference.

methane↗

Kepler Certified False Positive Table

This document describes the Kepler Certied False Positive table hosted at the Exoplanet Archive1, herein referred to as the CFP table. This table is the result of detailed examination by the Kepler False Positive Working Group (FPWG) of declared false positives in the Kepler Object of Interest (KOI) tables (see, for example, Batalha et al. (2012); Burke et al.(2014); Rowe et al. (2015); Mullally et al. (2015); Coughlin et al. (2015b)) at the Exoplanet Archive. A KOI is considered a false positive if it is not due to a planet orbiting the KOI's target star. The CFP table contains all KOIs in the Exoplanet Archive cumulative KOI table. The purpose of the CFP table is to provide a list of certified false positive KOIs. A KOI is certified as a false positive when, in the judgement of the FPWG, there is no plausible planetary interpretation of the observational evidence, which we summarize by saying that the evidence for a false positive is compelling. This certification process involves detailed examination using all available data for each KOI, establishing a high-reliability ground truth set. The CFP table can be used to estimate the reliability of, for example, the KOI tables which are created using only Kepler photometric data, so the disposition of individual KOIs may differ in the KOI and CFP tables. Follow-up observers may find the CFP table useful to avoid observing false positives.

Kepler↗

Automated Spacecraft Communications Service Demonstration Using NASA's SCaN Testbed

The traditional paradigm for space mission operations relies on inefficient, highly scripted pre-planned activities between space communications & navigation service providers and user ground mission operations centers. Typically there is limited or non-existent automation capabilities on the user spacecraft for requesting space communications services, and on the provider network for request dispositioning and service provisioning. In the past, using these processes for space networks was sufficient with the relatively small number of user spacecraft requesting services. However, with an ever increasing number of satellites being launched to orbit, more complex event-driven science objectives, exploration missions involving collaborative platforms, and more distant missions, approaches that improve automation, flexibility and efficiency are needed. This paper describes NASA's recently completed on-orbit demonstration results of a new space communications service concept called User Initiated Service, and a discussion for infusing this innovation into operations.

waveforms↗

Automated Spacecraft Communications Service Demonstration Using NASA's SCaN Testbed

The traditional paradigm for space mission operations relies on inefficient, highly scripted pre-planned activities between space communications and navigation service providers and user ground mission operations centers. Typically there is limited or non-existent automation capabilities on the user spacecraft for requesting space communications services, and on the provider network for request dispositioning and service provisioning. In the past, using these processes for space networks was sufficient with the relatively small number of user spacecraft requesting services. However, with an ever increasing number of satellites being launched to orbit, more complex event-driven science objectives, exploration missions involving collaborative platforms, and more distant missions, approaches that improve automation, flexibility and efficiency are needed. This paper describes NASA's recently completed on-orbit demonstration results of a new space communications service concept called User Initiated Service, and a discussion for infusing this innovation into operations.

transmitters receivers↗

Bladed Terrain on Pluto: Possible Origins and Evolutions

Pluto’s Bladed Terrain (centered roughly 20°N, 225°E) covers the flanks and crests of the informally named Tartarus Dorsa with numerous roughly aligned blade-like ridges oriented ~North-South; it may also stretch considerably farther east onto the non-close approach hemisphere but that inference is tentative. Individual ridges are typically several hundred meters high, and are spaced 5 to 10 km crest to crest, separated by Vshaped valleys. Many ridges merge at acute angles to form Y-shape junctions in plan view. The principle composition of the blades themselves we suspect is methane or a methane-rich mixture. (Methane is spectroscopically strongly observed on the optical surfaces of blades.) Nitrogen ice is very probably too soft to support their topography. Cemented mixtures of volatile and non-volatile ices may also provide a degradable but relief supporting “bedrock” for the blades, perhaps analogous to Callisto. Currently we are considering several hypotheses for the origins of the deposit from which Bladed Terrain has evolved, including aeolian disposition, atmospheric condensation, updoming and exhumation, volcanic intrusions or extrusions, crystal growth, among others. We are reviewing several processes as candidate creators or sculptors of the blades. Perhaps they are primary depositional patterns such as dunes, or differential condensation patterns (like on Callisto), or fissure extrusions. Or alternatively perhaps they are the consequence of differential erosion (such as sublimation erosion widening and deepening along cracks), variations in substrate properties, mass wasting into the subsurface, or sculpted by a combination of directional winds and solar isolation orientation. We will consider the roles of the long-term increasing solar flux and short periods of warm thick atmospheres. Hypotheses will be ordered based on observational constrains and modeling to be presented at the conference.

Nitrogen ice↗

Predicted Yield of Transits of Known Radial Velocity Exoplanets from the TESS Primary and Extended Missions

Radial velocity (RV) surveys have detected hundreds of exoplanets through their gravitational interactions with their host stars. Some will be transiting, but most lack sufficient follow-up observations to confidently detect (or rule out) transits. We use published stellar, orbital, and planetary parameters to estimate the transit probabilities for nearly all exoplanets that have been discovered via the RV method. From these probabilities, we predict that 25.5 (sup +0.7, sub -0.7) of the known RV exoplanets should transit their host stars. 'This prediction is more than double the amount of RV exoplanets that are currently known to transit The Transiting Exoplanet Survey Satellite (TESS) presents a valuable opportunity to explore the transiting nature of many of the known RV exoplanet systems. Based on the anticipated pointing of TESS during its two-year primary mission, we identify the known RV exoplanets that it will observe and predict that 11.7 (sup +0.3, sub -0.3) of them will have transits detected by TESS. However, we only expect the discovery of transits for ~3 of these exoplanets to be novel (i.e., not previously known). We predict that the TESS photometry will yield dispositive null results for the transits of ~ 125 RV exoplanets. This will represent a substantial increase in the effort to refine ephemerides of known RV exoplanets. We demonstrate that these results are robust to changes in the ecliptic longitudes of future TESS observing sectors. Finally, we consider how several potential TESS extended mission scenarios affect the number of transiting RV exoplanets we expect TESS to observe.

Thomas Barclay↗

Chapter 4: Aerospace Neurology

In the practice of medicine, the neurologist is called upon to answer the following questions: (1) Does the patient have neurologic disease? (2) If so, what is the localization of the lesion or lesions? (3) What is the pathophysiology of the process? (4) What is the preliminary differential diagnosis? Utilizing the tools of the neurologic and medical history, the neurologic examination, ancillary studies, and one’s education, training, and experience, the neurologist arrives at a diagnosis. The aerospace medicine physician (evaluator) has the additional challenge of relating the neurologic condition to aviation safety and achieving an appropriate aeromedical disposition. Whether it is the aviation medical examiner (AME), flight surgeon, or Federal Aviation Administration (FAA) regulator, the aerospace medicine physician shoulders the responsibility of a determination that may decide one’s career in aviation or spaceflight. Considering the individual, and yet preserving aerospace safety, is a never-ending challenge for the aerospace medicine physician. The evaluator has the dual responsibility of applying the standards and also considering exceptions to the standards in allowing waivers from standards, while assuring aerospace safety.

Joseph I Sirven↗

A Habitable-zone Earth-sized Planet Rescued from False Positive Status

We report the discovery of an Earth-sized planet in the habitable zone of a low-mass star called Kepler-1649. The planet, Kepler-1649 c, is 1.06(+0.15, -0.10.) times the size of Earth and transits its 0.1977 ± 0.0051 Mʘ “mid” M-dwarf host star every 19.5 days. It receives 74% ± 3% the incident flux of Earth, giving it an equilibrium temperature of 234 ± 20 K and placing it firmly inside the circumstellar habitable zone. Kepler-1649 also hosts a previously known inner planet that orbits every 8.7 days and is roughly equivalent to Venus in size and incident flux. Kepler-1649 c was originally classified as a false positive (FP) by the Kepler pipeline, but was rescued as part of a systematic visual inspection of all automatically dispositioned Kepler FPs. This discovery highlights the value of human inspection of planet candidates even as automated techniques improve, and hints that terrestrial planets around mid to late M-dwarfs may be more common than those around more massive stars.

Andrew Vanderburg↗

More than RBE: Exploring Two Decades of Space Radiation Quality and Carcinogenesis Research and How NASA Manages Cancer Risk

NASA’s Space Radiation Element (SRE), both as a stand-alone entity and as part of the Human Research Program, has invested heavily into investigating how the different qualities of radiation and low dose rates relevant to the space environment and how these factors effect long term carcinogenesis risk. NASA’s current model to assess astronaut excess cancer risk due to radiation exposure utilizes data generated from both in vitro and in vivo models to inform quality factor and dose-rate functions that scales risk estimates originally established from human cohorts exposed to terrestrial radiation, most notably the Lifespan Study of atomic bomb survivors (LSS). As part of an effort to update these quality function, the SRE hosted a workshop in on radiation quality in September 2021 and a workshop on dose-rate at NASA HRP’s Investigators’ Workshop in February 2022 where current and former grantees presented data that could potentially be incorporated into assessing carcinogenic risk. This presentation is intended to both inform the broader research community of the outcome of those workshops and generate a discussion as to what biological data should be generated to better inform NASA’s risk estimates. Additionally, NASA’s current risk disposition for cancer assessment will be discussed and clarified. We look forward to hearing feedback from the Radiation Research Society community!

Brock J Sishc↗

Dare Mighty Things

Winston Churchill once said, “To improve is to change; to be perfect is to change often.” JPL’s Property Accountability objective is to provide superior services related to property accountability, reutilization, and disposition. JPL must report property reutilized and disposed through either sales, donation, or scrap. Implementing the JPL designed and built Property Information Reporting System (PIRS), opened a new perspective with our data and what are we reporting to NASA. With this new depth of visibility, we self-implemented as assessment to validate the fiduciary and stewardship responsibilities of what is being reporting to NASA. JPL strives to perform at a level beyond the basic primary expectations of our NASA requirements. JPL developed the PIRS - which rolled out in 2018 - to simplify the delivery of JPL’s Personal Property and Equipment (PP&E) reporting: PIRS takes the raw data from Oracle to generate the NASA Form (NF) 1018 and Contractor Held Asset Reporting System (CHATS) Reports, and to meet the requirements established for AS9100 compliance. The data presented from PIRS is exportable and used to analyze our property records. JPL is also embarking on an effort to define the JPL of the future with “Enterprise 2.0”. Enterprise 2.0 is the driving force of JPL’s strategy to digitally transform the Laboratory from the current legacy processes and systems to a modern, integrated, information-driven highway of business transactions. This should include automation of routine processes and data-related tasks, integration of data and systems, advanced search and analytics, and improved information sharing and collaboration. As JPL’s evolving landscape of digital technologies advance to meet the future, JPL Property Accountability is making strides to surpass these expectations. For every cause there is an effect: a revealing of something that aids in the further development and transformation of JPL best business practices.

Sucher, Jay M↗

NASA Engineering and Safety Center Technical Bulletin No. 22-06: Treatment of Slosh Stability Margin Reductions for Human-Rated Launch Vehicles

Slosh dynamics pose a stability concern for human-rated launch vehicles during ascent. Historical perspectives on the treatment of slosh dynamics, newly developed rules of thumb, the utility of flight data, and methods for analyzing and dispositioning slosh instability risks should be considered when linear stability margins are lower than typically accepted for human-rated systems.

Fuel Slosh↗

Exploration Medical Capability Clinical Decision Support Use Cases for CDSS Test Bed

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data, and crew time), limited options for evacuation, and those associated with delayed or constrained communications. Each of these challenges necessitates greater degrees of crew autonomy as our distance from Earth increases. Specifically, as communication delays intensify - and evacuation capability diminishes the further we explore space - the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will become key to mission continuation and success. This need will be especially true should a crewmember become ill or injured wherein treatment and disposition “in-situ” ultimately falls to the crew itself to determine. To augment the requisite knowledge, skills, and abilities (KSAs) of a time-constrained exploration mission crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution. A CDSS would facilitate, guide, and inform Earth-independent medical operations while assisting crewmembers through various clinical presentations. The CDSS would allow crewmembers to take advantage of pre-mission training tied to the in-flight/in-mission use of pre-planned protocols that offer both a range of diagnostic options and “just-in-time” (refamiliarization) training and assistance. CDSS will expand such capabilities by improving the utility and effectiveness of various available diagnostic, treatment, and health maintenance tools, techniques, and measures.

ExMC↗

A Catalog of Kepler Habitable Zone Exoplanet Candidates

The NASA Kepler mission ha s discovered thousands of new planetary candidates, many of which have been confirmed through follow-up observations. A primary goal of the mission is to determine the occurrence rate of terrestrial-size planets within the Habitable Zone (HZ) of their host stars. Here we provide a list of HZ exoplanet candidates from the Kepler Q1–Q17 Data Release 24 data-vetting process. This work was undertaken as part of the Kepler HZ Working Group. We use a variety of criteria regarding HZ boundaries and planetary sizes to produce complete lists of HZ candidates, including a catalog of 104 candidates within the optimistic HZ and 20 candidates with radii less than two Earth radii within the conservative HZ. We cross-match our HZ candidates with the stellar properties and confirmed planet properties from Data Release 25 to provide robust stellar parameters and candidate dispositions. We also include false-positive probabilities recently calculated by Morton et al. for each of the candidates within our catalogs to aid in their validation. Finally, we performed dynamical analysis simulations for multi-planet systems that contain candidates with radii less than two Earth radii as a step toward validation of those systems.

Astrobiology↗

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

A Crew and Logistics Lander for the Common Habitat Architecture

The Common Habitat Architecture is a conceptual study that explores the use of a large habitat derived from the Space Launch System (SLS) liquid oxygen tank as a core habitation element that can be used for crew missions or training in 0g, 1/6g, 3/8g, and 1g. This is not part of current NASA Artemis mission planning, but instead represents an architecture that could potentially follow after the Artemis missions and initial human Mars landings. This architecture leverages Starship-derived vehicles for crew landing on and ascent from the Moon and Mars in support of long-duration surface missions with pressurized crew transfer baselined as a nominal capability. This is not the Human Landing System variant of Starship but represents a number of modifications to enable long-duration surface missions with an eight-person crew size. A rapid brainstorming study was conducted in February of 2021, using only public data, to identify options to deliver the 90-ton Common Habitat to the surface and emplace it at the intended habitation site. This study compared three lunar lander concepts and three Mars lander concepts before ultimately selecting the SpaceX Starship as the most viable lander. The Common Habitat Architecture assumes that this Starship variant can further be modified for crew and cargo delivery, assuming that the use of a common system will lead to cost benefits. It is assumed that the Starship will expend too much propellant in landing crew and logistics to be able to launch, given the assumed absence of surface propellant production. Consequently, a separable ascent stage is used for crew ascent. The pressurized elements of this modified Starship are discussed: Starship Ascent Module, Airlock, Transfer Tunnel, Pressurized Crew Transfer Module, and Logistics Modules. For each element, a description, dimensions, rough mass estimates, core capabilities, and design features are presented. Key mechanisms and internal structures of the starship are also discussed. This will include flame diverters for the ascend module, the orbital docking hatch, Pressurized Crew Transfer Module Garage door, Starship Ascent Module fairing, flame diverter blow-out panels, Pressurized Crew Transfer Module lift system, logistics module lift system, contingency crew ascent via the logistics module lift system, internal catwalks, and structural interfaces. Concept of Operations will be discussed for both Moon and Mars. This will include in-space crew rendezvous and transfer, crewed landing, shirtsleeve crew transfer, crew departure, contingency surface operations, and final element disposition. Key differences for Mars will be discussed, such as the Martian atmosphere, dust storms, the absence of crew handover, and Deep Space Exploration Vehicle rendezvous. Contingency microgravity maintenance access will also be discussed. This work will demonstrate viable pressurized crew transfer with a Starship-based lander architecture. Forward work includes Garage lighting and camera systems, Starship Ascent Module propulsion system and docking port trades, contingency habitation trades, and mass/power equipment estimation. Finally, forward work includes developing a heavy cargo return system derived from the Crew and Logistics Starship. The goal of this system is the return of at least 10,000 kg payloads from the surfaces of the Moon and Mars.

Lunar Lander↗

Particle Impact Simulation and Ignition Prediction

An experimentally calibrated tool is needed to predict if a system is susceptible to failure by particle impact ignition (PI) based on use conditions, materials, and flow geometry. This tool will accelerate new components, evaluating existing hardware, and help disposition anomalies. Conduct particle impact testing with in-situ diagnostics and complementary simulations on subset of key engineering materials (IN718, M400, 316L, 6061, Ti64, Zr) to develop a proof-of-concept predictive tool for assessing the risk of PI for idealized geometries (spherical particles) in realistic environments. Assess particle/target interactions (coefficient of restitution, ignition, kindling) using instrumented particle impact rigs while systematically varying key parameters (materials, particle size, environment, target configuration). Determine key field variables (temperature, strain, stress) in particle impacts using Multiphysics finite element and hydrocode simulations validated through comparison with experimental measurements and observations. Synthesize experiments and simulations into constitutive models for PI that can be integrated with existing computational fluid dynamics (CFD) and Debris Transport Analysis (DTA) tools in future efforts

particle impact↗