SEARCH · Search NASA
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.
Overall objectives of the project are: Develop a science & engineering basis for the release, ignition, and combustion behavior of hydrogen across its range of use (including high pressure and cryogenic); and, Facilitate the assessment of the safety (risk) of hydrogen systems and enable use of that information for revising regulations, codes, and standards (RCS), and permitting hydrogen fueling stations.
Reed-Solomon (RS) encoder based on Berlekamp bit-serial multiplier algorithm. RS code standard, based on code words of 255 8-bit symbols, of which 223 symbols convey information and remaining 32 are check symbols. This code enables correction of up to 16 erroneous information symbols per word. Berlekamp algorithm based on code-generating polynomial with 32 roots that occur in reciprocal pairs. Choice of algorithm permits compact design.
Fiber-reinforced ceramic matrix composites are attractive for high-temperature nuclear applications due to excellent thermal and mechanical properties as well as reasonable-to-outstanding radiation resistance. Over the past 20 years, the use of ceramic matrix composite applications expanded to many commercial non-nuclear industries as fabrication and application of the technologies mature. The ASME Boiler Pressure Vessel Code, under Section III Division 5, provides the design and construction rules for High Temperature Reactor components. It published the first rules for ceramic matrix composites to be used for reactor core components. The rules lay out the quality requirements together with the design and materials criteria for the use and application of silicon carbide- and carbon-based matrix material technologies. As with the established graphite rules, the ceramic composite material rules are structured in Subsection HH (from Section III), that addresses the criteria for class SN nonmetallic core components. The code rules rely heavily on the development and publication of standards for composite specification, classification, and testing of mechanical, thermal, and other properties. These test methods are developed in ASTM Committee C28 on Advanced Ceramics, with a current focus on ceramic composite tubes. This article describes the detail of the composites code, the design methodology and similarities to the graphite code, the guidance for the development of specifications for ceramic composites (for nuclear applications) including recent standard developments, and it mentions the next steps to support licensing aspects by validating the code with benchmarking data.
Many commercial buildings have a vast network of sensors as part of their building automation systems (BAS) that allows opportunities for energy consumption and cost savings by deploying advanced control sequences. However, this resource is often underutilized since BAS are typically programmed with simple control sequences with limited potential to deliver on these opportunities. The recent availability of ASHRAE Guideline 36 (G36) with advanced HVAC control sequences supports control retrofits in existing buildings to unlock much of the savings potential. However, barriers such as the lack of standard naming convention of building assets and data points, proprietary equipment and BAS, and the inherent uniqueness of buildings and their systems prevent building stakeholders from adopting any “plug-and-play” implementation of G36. Instead, control vendors must often undertake the manual and labor-intensive point mapping process to identify a data stream’s functional and spatial relationship within the HVAC system along with other relevant contexts and map it to the new control sequences. The vendor must carry out the point mapping process in each individual building since the mapping is unlikely to port over to another building. Even for the same building, the point mapping process can occur multiple times if various control vendors implement different control retrofits and/or multiple control retrofits happen over the lifecycle of the building. Then, there is the likelihood that G36 control sequences are programmed uniquely to the building, preventing the same implementation from being reused in another. Therefore, this paper presents a field demonstration of how we leveraged the Brick ontology with BACnet, OpenBuildingControl’s Control Description Language (CDL), and open-source support tools to implement scalable and portable advanced building controls. These tools provide standardized semantic descriptions and relationships of the building’s assets and data points (Brick), standardized communication protocol to read from and write to the building’s BAS (BACnet), and standardized code implementations (CDL) of standardized advanced control strategies (G36). We implemented G36’s hot water supply temperature setpoint reset in a Berkeley, CA building for this field demonstration. This field demonstration aims to show how integrating these tools may streamline the deployment of advanced control sequences such as G36 in a consistent manner regardless of differences found across buildings.
Abstract not provided.
Abstract not provided.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
A simple encoder/decoder implementation scheme is described for the (63,56) BCH code which can be used to correct single errors and to detect any even-number of errors. The scheme is feasible for onboard-spacecraft implementation.
In an earlier report, the LINKABIT Corporation studied the performance of the (2,1,6) convolutional code on the radio frequency interference (RFI)/burst channel using analytical methods. Using an R(sub 0) analysis, the report concluded that channel interleaving was essential to achieving reliable performance. In this report, Monte Carlo simulation techniques are used to study the performance of the convolutional code on the RFI/burst channel in more depth. The basic system model under consideration is shown. The convolutional code is the NASA standard code with generators g(exp 1) = 1+D(exp 2)+D(exp 3)+D(exp 5)+D(exp 6) and g(exp 2) = 1+D+D(exp 2)+D(exp 3)+D(exp 6) and d(sub free) = 10. The channel interleaver is of the convolutional or periodic type. The binary output of the channel interleaver is transmitted across the channel using binary phase shift keying (BPSK) modulation. The transmitted symbols are corrupted by an RFI/burst channel consisting of a combination of additive white Gaussian noise (AWGN) and RFI pulses. At the receiver, a soft-decision Viterbi decoder with no quantization and variable truncation length is used to decode the deinterleaved sequence.
In the Virtual Observatory (VO), software tools will perform the functions that have traditionally been performed by physical observatories and their instruments. These tools will not be adjuncts to VO functionality but will make up the very core of the VO. Consequently, the tradition of observatory and system independent tools serving a small user base is not valid for the VO. For the VO to succeed, we must improve software collaboration and code sharing between projects and groups. A significant goal of the Scientist's Expert Assistant (SEA) project has been promoting effective collaboration and code sharing between groups. During the past three years, the SEA project has been developing prototypes for new observation planning software tools and strategies. Initially funded by the Next Generation Space Telescope, parts of the SEA code have since been adopted by the Space Telescope Science Institute. SEA has also supplied code for SOFIA, the SIRTF planning tools, and the JSky Open Source Java library. The potential benefits of sharing code are clear. The recipient gains functionality for considerably less cost. The provider gains additional developers working with their code. If enough users groups adopt a set of common code and tools, defacto standards can emerge (as demonstrated by the success of the FITS standard). Code sharing also raises a number of challenges related to the management of the code. In this talk, we will review our experiences with SEA - both successes and failures - and offer some lessons learned that may promote further successes in collaboration and re-use.
This manuscript presents the results of a multi-lateral international activity intended to understand how to execute a cycle stress test as specified in a chosen standard (GTR, SAE, ISO, EIHP...). The purpose of this work was to establish a harmonized test method protocol to ensure that the same results would be achieved regardless of the testing facility. It was found that accurate temperature measurement of the working fluid is necessary to ensure the test conditions remain within the tolerances specified. Continuous operation is possible with adequate cooling of the working fluid but this becomes more demanding if the cycle frequency increases. Recommendations for future test system design and operation are presented.
Abstract not provided.
Abstract not provided.