Search NASA⌕ Search

SEARCH · Search NASA

Results for “open-source software design”

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.

187 records · Page 11

Retrofitting Holcim Ste. Genevieve Cement Plant with CO2 Capture Plant Using Air Liquide Cryocap™ FG Technology

The global cement manufacturing industry is a major contributor to carbon dioxide emissions. The International Energy Agency's "Net Zero Emissions by 2050 Scenario" identifies CCS as a major strategy for meeting that goal. This project is among the first attempts to transfer capture technology developed at coal-fired power plants to the cement industry. The main objective of the project is to execute and complete a front-end engineering and design (FEED) studies for commercial-scale, carbon capture projects that separates 95% of the total CO2 emissions at the Holcim (US) Ste. Genevieve cement manufacturing facility using Air Liquide’s Pressure Swing Adsorption system (PSA) assisted Cryocap™ technology. The Holcim Ste. Genevieve cement plant in Missouri, US, boasts one of the largest single cement production lines in the world, with a capacity of approximately 12,000 t/day. The plant currently uses traditional fuels, namely coal and petcoke. The captured CO2 will be pipeline and geological storage grade. The industrial host site emits approximately 3.0 million tonne CO2/yr. Air Liquide’s Cryocap™ technology has been developed over the last 18+ years for CO2 capture applications. It has been shown to be applicable to a variety of industrial applications (e.g., steel, cement, SMR, Fluidized Catalytic Crackers (FCCs)). Cryocap™ FG consists of a Pressure Swing Adsorption (PSA) unit coupled with a Cryogenic System. The PSA pre-concentrates the CO2 from the flue gas, while the cryogenic unit enables the CO2 purity to be increased to the desired level. The project team is led by the Prairie Research Institute at the University of Illinois at Urbana-Champaign. The tasks include: complete FEED study for retrofitting the industrial facility with a carbon capture system to support developing a detailed cost estimate; business case analysis outlining the anticipated revenue and credits if projects was built and operated; technoeconomic analysis (TEA) outlining how capture system achieves DOE capture goals; and life cycle (LCA) analysis demonstrating zero net carbon emissions. The FEED study was successfully completed. This includes completing the process basis of design; preliminary engineering; outside battery limits (OSBL) detailed engineering including a Zero Liquid Discharge (ZLD) wastewater treatment system; inside battery limits (ISBL) detailed engineering [1]. An overall project capital cost estimate within a -20%/+30% accuracy was developed. The major contributors to the Total Plant Cost (TPC), by system, are the costs associated with the Outside Battery Limit (OSBL) section of the plant which includes a new river water intake structure and a Zero Liquid Discharge (ZLD) system. By cost category, the major contributors to the TPC are equipment and subcontractor costs, followed closely by engineering, construction management, home office and contractor fees. The TEA has been created to reflect the findings of the project. It analyzes the economic performance of the Cryocap™ technology by reviewing the estimated capital costs, operating cost, and revenue. The Cost of Capture (COC) associated with the Cryocap™ technology for 95% CO2 capture, when considering NETL 2018 economic assumptions (42/58 debt/equity ratio, 5.15% interest on debt and 1.42% return on equity in real dollars) and 2022 economic assumptions (42/58 debt/equity ratio, 8.82% interest on debt and 4.90% return on equity in real dollars) was found to be much lower than that for the DOE-NETL’s base-line cases. The highest contributors to the COC are annualized capital expenditures (CAPEX) and electricity consumption which can be offset by using lower cost renewable sources. The LCA was conducted using OpenLCA which is an open-source software that is recommended by NETL. The database utilized for this study was a modified version of TRACI 2.1 (developed by the US. Environmental Protection Agency’s National Risk Management Research Laboratory and modified by NETL). The Cryocap™ FG technology does not consume fuels in significant quantities and does not utilize specialized chemical solvents subject to decomposition, such as those utilized in amine-based carbon capture systems. The Cryocap™ FG technology mainly utilizes electricity as its energy input; hence, its calculated emissions are mainly associated with the generation of electricity offsite and are dependent on the energy matrix of the grid at the time of project implementation. The water consumption impact of the Cryocap™ FG is mostly for makeup of the water lost by evaporation in the cooling tower; however, the carbon capture plant will be equipped with a ZLD system to avoid effluent streams and minimize water consumption. The successful construction and operation of this plant based on this study results will provide a means to demonstrate an economically attractive and transformational capture technology that can be used to retrofit existing plants and be deployed at new plants.

01 COAL, LIGNITE, AND PEAT↗

Evolution of International Space Station Program Safety Review Processes and Tools

The International Space Station Program at NASA is constantly seeking to improve the processes and systems that support safe space operations. To that end, the ISS Program decided to upgrade their Safety and Hazard data systems with 3 goals: make safety and hazard data more accessible; better support the interconnection of different types of safety data; and increase the efficiency (and compliance) of safety-related processes. These goals are accomplished by moving data into a web-based structured data system that includes strong process support and supports integration with other information systems. Along with the data systems, ISS is evolving its submission requirements and safety process requirements to support the improved model. In contrast to existing operations (where paper processes and electronic file repositories are used for safety data management) the web-based solution provides the program with dramatically faster access to records, the ability to search for and reference specific data within records, reduced workload for hazard updates and approval, and process support including digital signatures and controlled record workflow. In addition, integration with other key data systems provides assistance with assessments of flight readiness, more efficient review and approval of operational controls and better tracking of international safety certifications. This approach will also provide new opportunities to streamline the sharing of data with ISS international partners while maintaining compliance with applicable laws and respecting restrictions on proprietary data. One goal of this paper is to outline the approach taken by the ISS Progrm to determine requirements for the new system and to devise a practical and efficient implementation strategy. From conception through implementation, ISS and NASA partners utilized a user-centered software development approach focused on user research and iterative design methods. The user-centered approach used on the new ISS hazard system utilized focused user research and iterative design methods employed by the Human Computer Interaction Group at NASA Ames Research Center. Particularly, the approach emphasized the reduction of workload associated with document and data management activities so more resources can be allocated to the operational use of data in problem solving, safety analysis, and recurrence control. The methods and techniques used to understand existing processes and systems, to recognize opportunities for improvement, and to design and review improvements are described with the intent that similar techniques can be employed elsewhere in safety operations. A second goal of this paper is to provide and overview of the web-based data system implemented by ISS. The software selected for the ISS hazard systemMission Assurance System (MAS)is a NASA-customized vairant of the open source software project Bugzilla. The origin and history of MAS as a NASA software project and the rationale for (and advantages of) using open-source software are documented elsewhere (Green, et al., 2009).

Ratterman, Christian D.↗

SOAREX-8 Suborbital Experiments 2015 - A New Paradigm for Small Spacecraft Communication

In 2015 NASA plans to launch a payload to 280 Km altitude on a sounding rocket from the Wallops Flight Facility. This payload will contain several novel technologies that work together to demonstrate methodologies for space sample return missions and for nanosatellite communications in general. The payload will deploy and test an Exo-Brake, which slows the payload aerodynamically, providing eventual de-orbit and recovery of future ISS samples through a Small Payload Quick Return project. In addition, this flight addresses future Mars mission entry technology, space-to-space communications using the Iridium Short Messaging Service (SMS), GPS tracking, and wireless sensors using the ZigBee protocol. SOAREX-8 is being assembled and tested at Ames Research Center (ARC) and the NASA Engineering and Safety Center (NESC) is funding sensor and communications work. Open source Arduino technology and software are used for system control. The ZigBee modules used are XBee units that connect analog sensors for temperature, air pressure and acceleration measurement wirelessly to the payload telemetry system. Our team is developing methods for power distribution and module mounting, along with software for sensor integration, data assembly and downlink. We have demonstrated relaying telemetry to the ground using the Iridium satellite constellation on a previous flight, but the upcoming flight will be the first time we integrate useful flight test data from a ZigBee wireless sensor network. Wireless sensor data will measure the aerodynamic efficacy of the Exo-Brake permitting further on orbit flight tests of improved designs. The Exo-Brake is 5 sq m in area and will be stored in a container and deployed during ascent once the payload is jettisoned from the launch vehicle. We intend to further refine the hardware and continue testing on balloon launches, future sounding rocket flights and on nanosatellite missions. The use of standards-based and open source hardware/software has allowed for this project to be completed with a very modest budget and a challenging schedule. There is a wealth of hardware and software available for both the Arduino platform and the XBee, all low-cost or open-source. Along with the Exo-Brake hardware and deployment discussion, this paper will describe in detail the system architecture emphasizing the successful use of open source hardware and software to minimize effort and cost. Testing procedures, radio frequency interference (RFI) mitigation, success criteria and expected results will also be discussed. The use of Iridium short messaging capability for space-to-space links, standards-based wireless sensor networks, and other innovative communications technology are also presented.

aerobrake↗

INCREASING THE TRANSPARENCY AND REPRODUCIBILITY OF SPACE RADIATION SCIENCE: THE RADIATION BIOLOGY ONTOLOGY

Among the primary objectives of the Open/Open-Source Science paradigm are making scientific investigation data transparent and results reproducible [1], objectives shared by the FAIR principles [2]. To accomplish this, the conceptual framework that includes all the investigation objects needs to be accurately captured and communicated to all data consumers. A large part of this requires using metadata standards to annotate data collected. These standards should be readily accessible, informed by scientific community consensus and sufficiently specific to encompass all of the important aspects of the investigation. Starting in 2020 we have been co-leading an open consortium to develop a new metadata standard, the Radiation Biology Ontology (RBO), through the Open Biological and Biomedical Ontologies (OBO) Foundry [3]. We began by transforming many of the terms from the National Council on Radiation Protection and Measurement into concepts that can be formally related to existing OBO Foundry classes or attributes. We then identified and imported into the RBO existing OBO Foundry classes that have obvious relevance for radiation biomedicine (for example, concepts from the Environment Ontology that describe radiative processes, and concepts from the Gene Ontology dealing with molecular and cellular responses to radiation). Finally, we scrutinized datasets from investigations of radiation effects held in NASA GeneLab and LSDA repositories and added additional classes, instances, and attributes into the RBO that should be used to annotate these data. We developed the RBO using the open-source tools of GitHub and publish the RBO periodically through the NIH/NCBI BioPortal website, so systems worldwide can leverage the knowledge it contains [4]. This initial phase of concept modeling has yielded an RBO that at present has more than 300 declared concepts, with more than 3500 additional concepts imported from other OBO Foundry ontologies. While this first phase has focused on concepts for annotating samples, environments, exposures, and measurements, the next phase will center on supporting annotation of results and findings, such as concept models of molecular, cellular and tissue effects. The value of the RBO will be determined in part by our ability to engage the community in its development, and we have established a Radiobiology Informatics Consortium with unrestricted membership as the owner of the RBO in order to encourage investigators, system owners and other to join in this effort. Anyone can report issues or request new concept modeling or other features directly on GitHub. By using the BioPortal application programming interface, systems can pose dynamic queries to the latest version of the RBO for information on individual classes or entire hierarchies; this design eliminates the need for systems to be updated in order to use newer versions of the RBO. We hope to contribute to the advancement of open radiobiological science through the continued, open development of the RBO, that will provide more precise, machine-interpretable descriptions of investigations, as well as support data meta-analysis through machine learning or other artificial intelligence methods. REFERENCES [1] Open science in space. Nature Medicine, 2021. 27(9): p. 1485-1485. [2] Wilkinson, M.D., et al., The FAIR Guiding Principles for scientific data management and stewardship. Sci Data, 2016. 3: p. 160018. [3] Smith, B., et al., The OBO Foundry: coordinated evolution of ontologies to support biomedical data integration. Nat Biotechnol, 2007. 25(11): p. 1251-5. [4] Whetzel, P.L., et al., BioPortal: enhanced functionality via new Web services from the National Center for Biomedical Ontology to access and use ontologies in software applications. Nucleic Acids Res, 2011. 39(Web Server issue): p. W541-5.

informatics↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service.Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations.The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-to-station handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an in-orbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service. Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations. The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-tostation handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an inorbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

FENIX: An Open-Source Multiphysics Integrated Framework Enabling Collaborative Development of Plasma Facing Component Modeling Capabilities

Advanced modeling and simulation tools have a crucial role to play in accelerating fusion energy deployment as a sustainable power source. Multiphysics, high-fidelity computational tools can help understand, model, and quantify the complex interactions between materials performance, plasma and neutron exposure, and engineering processes. As a result, they accelerate the design, safety analysis, and performance evaluation of fusion systems. This webinar introduces the Fusion ENergy Integrated multiphys-X (FENIX) framework, an open-source multiphysics tool for plasma facing component modeling. FENIX leverages the Multiphysics Object-Oriented Simulation Environment (MOOSE) framework, which has been developed by the United States Department of Energy Nuclear Energy Advanced Modeling and Simulation (NEAMS) program. FENIX couples various MOOSE capabilities such as heat transfer, thermomechanics, thermal hydraulics, electromagnetics, and plasma kinetics with the MOOSE-based applications Cardinal (neutronics) and TMAP8 (tritium transport). During the webinar, we will present FENIX and discuss how its modularity, openness, software quality assurance processes, and licensing approach supports effective collaborations, including public-private partnerships.

11 - NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗