Foundation Models for Science: Potential, Challenges, and the Path Forward
Explore the source record for details and available documents.
Rahul Ramachandran↗
SEARCH · Search NASA
Results for “foundation”
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.
Surya - Generalist Foundation Model on SDO Data
Explore the source record for details and available documents.
Sujit Roy↗
In Space Manufacturing and Extraterrestrial Construction: How Did We Get Here? Where Are We? Where Should We Be Going? The Challenge: Establish the Foundation for Mission Readiness
Explore the source record for details and available documents.
regolith↗
Foundational women in planetary geomorphology: Some contributions in fluvial, aeolian, and (cryo)volcanic subdisciplines
Explore the source record for details and available documents.
Devon M. Burr↗
Astronomical random numbers for quantum foundations experiments
Explore the source record for details and available documents.
Calvin Leung↗
The physical foundation of the reconnection electric field
Explore the source record for details and available documents.
M. Hesse↗
Evaluation of Fieldbus and OPC for Advanced Life Support
FOUNDATION(Tm) Fieldbus and OP(TM) (OLE(TM)for Process Control) technologies were integrated into an existing control system for a crop growth chamber at NASA Ames Research Center. FOUNDATION(TM) Fieldbus is a digital, bi-directional, multi-drop, serial communications network which functions essentially as a LAN for sensors. FOUNDATION(TM) Fieldbus is heterarchical, with publishers and subscribers of data performing complex control functions at low levels without centralized control and its associated overhead. OPC(TM) is a set of interfaces which replace proprietary drivers with a transparent means of exchanging data between the fieldbus and applications. The objectives were: (1) to integrate FOUNDATION(TM) Fieldbus into existing ALS hardware and determine its overall effectiveness and reliability and, (2) to quantify any savings produced by using fieldbus and OPC technologies. We encountered several problems with the FOUNDATION(TM) Fieldbus hardware chosen. Our hardware exposed 100 data for each channel of the fieldbus. The fieldbus configurator software used to program the fieldbus was simply not adequate. The fieldbus was also not inherently reliable. It lost its settings twice during our tests for unknown reasons. OPC also had issues. It did not function at all as supplied, requiring substitution of some of its components with those from other vendors. It would stop working after a fixed period of time. Certain database calls eventually lock the machine. Overall, we would not recommend FOUNDATION(TM) Fieldbus: it was too difficult to implement with little overall added value. It also seems unlikely that FOUNDATION(TM) Fieldbus will gain sufficient penetration into the laboratory instrument market to ever be cost effective for the ALS community. OPC had good reliability and performance once a stable installation was achieved. It allowed a rapid change to an alternative software strategy when our first strategy failed. It is a cost effective solution to distributed control systems development.
Boulanger, Richard P.↗
Mars Technologies Spawn Durable Wind Turbines
Sometimes referred to as regenerative life support systems, the concept includes an enclosed self-sufficient habitat that can independently support life for years on end. Such a system aims not only to produce its own food and water but to purify air and convert waste into useful byproducts. In the early 1990s, NASA was planning for an extended stay on Mars, and Bubenheim and his Ames colleagues were concentrating efforts on creating a complete ecological system to sustain human crewmembers during their time on the Red Planet. The main barrier to developing such a system, he says, is energy. Mars has no power plants, and a regenerative system requires equipment that runs on electricity to do everything from regulating humidity in the atmosphere to monitoring the quality of recycled water. The Ames group started looking at how to best make power on a planet that is millions of miles away from Earth and turned to a hybrid concept combining wind and solar power technologies. The reason was that Mars experiences frequent dust storms that can block nearly all sunlight. When theres a dust storm and the wind is blowing, the wind system could be the dominant power source. When the wind is not blowing and the sun is out, photovoltaics could be the dominant source, says Bubenheim.To develop and test the wind power technology, Ames turned to a remote, harsh environment here on Earth: the South Pole. The South Pole was a really good analog for Mars, says Bubenheim. The technology features for going to Mars were the same technology features needed to make something work at the South Pole.Around the same time that NASA started investigating energy technologies for the Red Planet, the National Science Foundation (NSF) was working on a redesign of their station at the South Pole. To power its operations, NSF used fuel that it flew to the remote location, but the Foundation recognized the benefits of also using onsite renewable energy technologies. In the winter they have small crews and their power requirements are less, says Bubenheim. In the summers, they bring in larger groups and photovoltaics could supply a lot of power. Using renewable energy technology could be a way of reducing the amount of fuel they have to fly in.Technology TransferTo advance wind turbine technology to meet the requirements of extremely harsh environments like that on Mars, Ames partnered with NSF and the Department of Energy. It was clear that a lot of the same features were also desirable for the cold regions of the Earth, says Bubenheim. NASA took the leadership on the team because we had the longest-term technology a Mars turbine. Years before, NSF had worked with a company called Northern Power Systems (NPS), based in Barre, Vermont, to deploy a 3-kilowatt wind turbine on Black Island off the coast of Antarctica.Sometimes referred to as regenerative life support systems, the concept includes an enclosed self-sufficient habitat that can independently support life for years on end. Such a system aims not only to produce its own food and water but to purify air and convert waste into useful byproducts. In the early 1990s, NASA was planning for an extended stay on Mars, and Bubenheim and his Ames colleagues were concentrating efforts on creating a complete ecological system to sustain human crewmembers during their time on the Red Planet. The main barrier to developing such a system, he says, is energy. Mars has no power plants, and a regenerative system requires equipment that runs on electricity to do everything from regulating humidity in the atmosphere to monitoring the quality of recycled water. The Ames group started looking at how to best make power on a planet that is millions of miles away from Earth and turned to a hybrid concept combining wind and solar power technologies. The reason was that Mars experiences frequent dust storms that can block nearly all sunlight. When there's a dust storm and the wind is blowing, the wind system could be the dominant power source. When the wind is not blowing and the sun is out, photovoltaics could be the dominant source, says Bubenheim.To develop and test the wind power technology, Ames turned to a remote, harsh environment here on Earth: the South Pole. The South Pole was a really good analog for Mars, says Bubenheim. The technology features for going to Mars were the same technology features needed to make something work at the South Pole.Around the same time that NASA started investigating energy technologies for the Red Planet, the National Science Foundation (NSF) was working on a redesign of their station at the South Pole. To power its operations, NSF used fuel that it flew to the remote location, but the Foundation recognized the benefits of also using onsite renewable energy technologies. In the winter they have small crews and their power requirements are less, says Bubenheim. In the summers, they bring in larger groups and photovoltaics could supply a lot of power. Using renewable energy technology could be a way of reducing the amount of fuel they have to fly in.Technology Transfer To advance wind turbine technology to meet the requirements of extremely harsh environments like that on Mars, Ames partnered with NSF and the Department of Energy. It was clear that a lot of the same features were also desirable for the cold regions of the Earth, says Bubenheim. NASA took the leadership on the team because we had the longest-term technology a Mars turbine.
Mars Technologies↗
A Model-Based Systems Engineering Journey to Developing a Concept of Operations
Starting in 2017, NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) element began a systems engineering transition from traditional, document-centric development to model-centric development when defining its foundation medical systems. These foundation medical systems define a Concept of Operations (ConOps) and identify the generic requirements for a medical system based on assumptions about a generic crew and mission environments and guidance from NASA standards (e.g., Medical “Levels of Care”). By making the transition, ExMC intends to improve communication among stakeholders about foundation medical system requirements and content. In addition, this transition will enable ExMC to lower both development and crew treatment risks for future, mission-specific medical systems. ExMC followed a Model Based Systems Engineering (MBSE) paradigm when developing the foundation medical systems. A model-based approach provides several advantages over a traditional, document-centric approach. First, when Systems Engineers (SE) develop diagrams in a model using a standard modeling language, they produce information dense pictures that facilitate understanding much more efficiently with less room for misinterpretation than text. Second, due to the evolving nature of projects, documentation becomes out of date the minute it is published. This can result in people making decisions based on information that is no longer current, especially if they are referencing a locally-stored copy of a document. A model, on the other hand, is always up to date with the latest approved changes and information. It serves as a single point of truth. Third, a model-centric approach centralizes all important information in one place. Rather than having to flip through separate ConOps documents, design specifications, requirements specifications, and the like to coordinate information, a model captures the content in one, integrated spot. This integration makes tracing information from end-to-end easier with greater reliability. The ExMC Systems Engineering Lifecycle follows a well-defined process. ExMC Systems Engineers perform all major steps of the process, regardless of the development methodology. One of the first steps in the process is developing the ConOps that describes the operation of the system from the point of view of the users. It includes a list of the users and their needs, the goals of the medical system, key assumptions about the system, and definitions of the medical system’s operational environments. For this development effort, ExMC chose to replace the traditional text-based ConOps document with a model. While the decision to change the development workflow was not difficult, implementing the structural and organizational workflows were. It required showing ExMC’s users, most of whom are not Systems Engineers, how the information they require would be presented in the model and to gain their acceptance of this approach. This paper documents key lessons learned during the ConOps transformation by focusing on how the model represents information, the agile workflow used by SEs when developing the model and how it integrates into a project plan, how leadership influenced key users to accept the transformation, and how the users interact with the model information.
Jeffrey Robert Cohen↗
Study of the physical properties of crystalline rocks in the southeast Voronezh anteclise
The physical properties of rocks, in the crystalline mass of the Voronezh anteclise, were studied. The study of the physical properties of rocks is important for the improvement of geophysical methods for mapping crystalline rocks in the foundation and exploration of different geological objects which are associated with the crystalline foundation, covered by the sedimentary mantle. It is found that: (1) rocks in the crystalline foundation are very different in physical properties; (2) the physical properties are closely related to their substance composition and genesis; (3) petrographic properties give clues of rock afficiation to certain complexes; and (4) physical and magnetic properties should be examined by petrography, chemical and X-ray analysis.
Dmitriyevskiy, V. S.↗
Simultaneous analysis and design for eigenvalue maximization
A simultaneous analysis and design approach to the maximization of buckling or vibration eigenvalues is presented. Both unimodal and bimodal optimum solutions are considered. A discretization of the structure and response is used to obtain sets of nonlinear algebraic equations which are solved numerically. The formulation is applied to the solution of the optimum design of a beam-column supported by an elastic foundation for maximum buckling load. Two cases are considered: the optimum design of the column for a given foundation and the optimum design of the foundation for a given column. Results are compared to published solutions when possible.
Plaut, Raymond H.↗
Tracing structural optima as a function of available resources by a homotopy method
Optimization problems are typically solved by starting with an initial estimate and proceeding iteratively to improve it until the optimum is found. The design points along the path from the initial estimate to the optimum are usually of no value. The present work proposes a strategy for tracing a path of optimum solutions parameterized by the amount of available resources. The paper specifically treats the optimum design of a structure to maximize its buckling load. Equations for the optimum path are obtained using Lagrange multipliers, and solved by a homotopy method. The solution path has several transitions from unimodal to bimodal solutions. The Lagrange multipliers and second-order optimality conditions are used to detect branching points and to switch to the optimum solution path. The procedure is applied to the design of a foundation which supports a column for maximum buckling load. Using the total available foundation stiffness as a homotopy parameter, a set of optimum foundation designs is obtained.
Haftka, Raphael T.↗
Buckling Analysis of Debonded Sandwich Panel Under Compression
A sandwich panel with initial through-the-width debonds is analyzed to study the buckling of its faceskin when subject to an in-plane compressive load. The debonded faceskin is modeled as a beam on a Winkler elastic foundation in which the springs of the elastic foundation represent the sandwich foam. The Rayleigh-Ritz and finite-difference methods are used to predict the critical buckling load for various debond lengths and stiffnesses of the sandwich foam. The accuracy of the methods is assessed with a plane-strain finite-element analysis. Results indicate that the elastic foundation approach underpredicts buckling loads for sandwich panels with isotropic foam cores.
Sleight, David W.↗
TBCC Discipline Overview. Hypersonics Project
The "National Aeronautics Research and Development Policy" document, issued by the National Science and Technology Council in December 2006, stated that one (among several) of the guiding objectives of the federal aeronautics research and development endeavors shall be stable and long-term foundational research efforts. Nearly concurrently, the National Academies issued a more technically focused aeronautics blueprint, entitled: the "Decadal Survey of Civil Aeronautics - Foundations for the Future." Taken together these documents outline the principles of an aeronautics maturation plan. Thus, in response to these overarching inputs (and others), the National Aeronautics and Space Administration (NASA) organized the Fundamental Aeronautics Program (FAP), a program within the NASA Aeronautics Research Mission Directorate (ARMD). The FAP initiated foundational research and technology development tasks to enable the capability of future vehicles that operate across a broad range of Mach numbers, inclusive of the subsonic, supersonic, and hypersonic flight regimes. The FAP Hypersonics Project concentrates on two hypersonic missions: (1) Air-breathing Access to Space (AAS) and (2) the (Planetary Atmospheric) Entry, Decent, and Landing (EDL). The AAS mission focuses on Two-Stage-To-Orbit (TSTO) systems using air-breathing combined-cycle-engine propulsion; whereas, the EDL mission focuses on the challenges associated with delivering large payloads to (and from) Mars. So, the FAP Hypersonic Project investments are aligned to achieve mastery and intellectual stewardship of the core competencies in the hypersonic-flight regime, which ultimately will be required for practical systems with highly integrated aerodynamic/vehicle and propulsion/engine technologies. Within the FAP Hypersonics, the technology management is further divided into disciplines including one targeting Turbine-Based Combine-Cycle (TBCC) propulsion. Additionally, to obtain expertise and support from outside (including industry and academia) the hypersonic uses both NASA Research Announcements (NRAs) and a jointly sponsored, Air Force Office of Scientific Research and NASA, National Hypersonic Science Center that are focused on propulsion research. Finally, these two disciplines use selected external partnership agreements with both governmental agencies and industrial entities. The TBCC discipline is comprised of analytic and experimental tasks, and is structured into the following two research topic areas: (1) TBCC Integrated Flowpath Technologies, and (2) TBCC Component Technologies. These tasks will provide experimental data to support design and analysis tool development and validation that will enable advances in TBCC technology.
Thomas, Scott R.↗
NASA Space Technology Roadmaps and Priorities: Restoring NASA's Technological Edge and Paving the Way for a New Era in Space
Success in executing future NASA space missions will depend on advanced technology developments that should already be underway. It has been years since NASA has had a vigorous, broad-based program in advanced space technology development, and NASA's technology base is largely depleted. As noted in a recent National Research Council report on the U.S. civil space program: Future U.S. leadership in space requires a foundation of sustained technology advances that can enable the development of more capable, reliable, and lower-cost spacecraft and launch vehicles to achieve space program goals. A strong advanced technology development foundation is needed also to enhance technology readiness of new missions, mitigate their technological risks, improve the quality of cost estimates, and thereby contribute to better overall mission cost management. Yet financial support for this technology base has eroded over the years. The United States is now living on the innovation funded in the past and has an obligation to replenish this foundational element. NASA has developed a draft set of technology roadmaps to guide the development of space technologies under the leadership of the NASA Office of the Chief Technologist. The NRC appointed the Steering Committee for NASA Technology Roadmaps and six panels to evaluate the draft roadmaps, recommend improvements, and prioritize the technologies within each and among all of the technology areas as NASA finalizes the roadmaps. The steering committee is encouraged by the initiative NASA has taken through the Office of the Chief Technologist (OCT) to develop technology roadmaps and to seek input from the aerospace technical community with this study.
Source record↗
Assessment Environment for Complex Systems Software Guide
This Software Guide (SG) describes the software developed to test the Assessment Environment for Complex Systems (AECS) by the West Virginia High Technology Consortium (WVHTC) Foundation's Mission Systems Group (MSG) for the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD). This software is referred to as the AECS Test Project throughout the remainder of this document. AECS provides a framework for developing, simulating, testing, and analyzing modern avionics systems within an Integrated Modular Avionics (IMA) architecture. The purpose of the AECS Test Project is twofold. First, it provides a means to test the AECS hardware and system developed by MSG. Second, it provides an example project upon which future AECS research may be based. This Software Guide fully describes building, installing, and executing the AECS Test Project as well as its architecture and design. The design of the AECS hardware is described in the AECS Hardware Guide. Instructions on how to configure, build and use the AECS are described in the User's Guide. Sample AECS software, developed by the WVHTC Foundation, is presented in the AECS Software Guide. The AECS Hardware Guide, AECS User's Guide, and AECS Software Guide are authored by MSG. The requirements set forth for AECS are presented in the Statement of Work for the Assessment Environment for Complex Systems authored by NASA Dryden Flight Research Center (DFRC). The intended audience for this document includes software engineers, hardware engineers, project managers, and quality assurance personnel from WVHTC Foundation (the suppliers of the software), NASA (the customer), and future researchers (users of the software). Readers are assumed to have general knowledge in the field of real-time, embedded computer software development.
tests↗
Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations
One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.
M Kaetzer↗
Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations
One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.
Mary Susan Kaetzer↗