Search NASA⌕ Search

SEARCH · Search NASA

Results for “Python interface”

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.

579 records · Page 33

Advanced Energy System Design (AESD): Technical Manual for the Records API

The Records API (application program interface) for Advanced Energy System Design (AESD) enables software that serves multidimensional record-oriented data to interoperate with software than uses such data. In the context of the Records API, multidimensional data records are simply tuples of real numbers, integers, and character strings, where each data value is tagged by a variable name, according to a pre-defined schema, and each record is assigned a unique integer identifier. Conceptually, these records are isomorphic to rows in a relational database, JSON objects, or key-value maps. Records servers might supply static datasets, sensor measurements that periodically update as new telemetry become available, or the results of simulations as the simulations generate new output. Records client software might display or analyze the data, but in the case of simulations the client request the creation of new ensembles for specified input parameters. It is also possible to chain records clients and servers together so that a client consuming data from a server might transform that data and serve it to further clients. This minimalist API avoids imposing burdensome metadata, structural, or implementation requirements on developers by relying on open-source technologies that is readily available for common programming languages. In particular, the API has been designed to place the smallest possible burden on services that provide data. This document defines the message format for the Records API, a transport mechanism for communicating the data, and semantics for interpreting it. The message format is specified as Google Protocol Buffers and the transport mechanism uses WebSockets. We discuss three major use cases for serving and consuming records data: (i) static data, (ii) dynamically augmented data, (iii) on-demand simulations, (iv) with filters, and (v) with bookmarks. Separate implementations of the API exist in C++, Haskell, JavaScript, Python, and R.

97 MATHEMATICS AND COMPUTING↗

AESD (Advanced Energy System Design) Records API [SWRs-17-50, 17-51, 17-52]

The Records API (application program interface) for Advanced Energy System Design (AESD) enables software that serves multidimensional record-oriented data to interoperate with software than uses such data. In the context of the Records API, multidimensional data records are simply tuples of real numbers, integers, and character strings, where each data value is tagged by a variable name, according to a pre-defined schema, and each record is assigned a unique integer identifier. Conceptually, these records are isomorphic to rows in a relational database, JSON objects, or key-value maps. Records servers might supply static datasets, sensor measurements that periodically update as new telemetry become available, or the results of simulations as the simulations generate new output. Records client software might display or analyze the data, but in the case of simulations the client request the creation of new ensembles for specified input parameters. It is also possible to chain records clients and servers together so that a client consuming data from a server might transform that data and serve it to additional clients. This minimalist API avoids imposing burdensome metadata, structural, or implementation requirements on developers by relying on open-source technologies that are readily available for common programming languages. In particular, the API has been designed to place the least possible burden on services that provide data. This document defines the message format for the Records API, a transport mechanism for communicating the data, and the semantics for interpreting it. The message format is specified as Google Protocol Buffers and the transport mechanism uses WebSockets. We discuss three major use cases for serving and consuming records data: (i) static data, (ii) dynamically augmented data, (iii) on-demand simulations, (iv) with filters, and (v) with bookmarks. Separate implementations of the API exist in C++, Haskell, JavaScript, Python, and R.

Bush, Brian↗

Fuel rod thermo-mechanic analysis of Kuosheng NPP in MSIVC transient with RELAP5 MOD3.3/Fraptran/Python code in SNAP interface

Kuosheng NPP (Nuclear Power Plant) is located on the northern coast of Taiwan. Its nuclear steam supply system (NSSS) is a type of boiling water reactor (BWR/6) designed and built by General Electric on a twin unit concept. Each unit includes two loops of recirculation piping and four main steam lines, with the thermal rated power of 2894 MWt. Unit 1 started SPU (Stretch Power Uprate) from Cycle 24 and Unit 2 started SPU from Cycle 23. The operating power is 104.7% of the OLTP (Original Licensed Thermal Power), which is 3030 MWt now. In order to estimate the safety of Kuosheng NPP, the methodology of Kuosheng NPP SPU safety analysis model was developed. This methodology is shown in Fig. 1. There are three main steps considered in this methodology. The first step is the development of the Kuosheng NPP SPU RELAP5 model. The next step is the main steam line isolation valve closure (MSIVC) analysis of Kuosheng NPP SPU RELAP5 model in order to confirm the maximum pressure of vessel below the acceptance limit of 9.58 MPa. The final step is the fuel rods integrity analysis of FRAPTRAN under the above conditions. From FRAPTRAN analysis results, we find that the peak value of cladding hoop strain is smaller than 0.01, the acceptance limit; furthermore, the fuel enthalpy values are smaller than 150 cal/g. These two results indicate that the fuel rods are still in safe condition after turbine trip accident. (authors)

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗