NCSD Benchmark Tutorial: Section 2, Evaluation of Experimental Data.
Abstract not provided.
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.
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.
As part of the DOE/NRC Collaboration for Criticality Safety Support for Commercial-Scale HALEU for Fuel Cycles and Transportation (DNCSH), a workshop was held on Teams on how to write a ICSBEP benchmark that meets modern standards. The workshop prepared people performing experiments and writing benchmarks so that they have an increased chance of submitting a benchmark that will be accepted. The workshop was led by experts from LANL, LLNL and Sandia.
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.
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.
This document provides common best practices for the efficient utilization of parallel file systems for analysts and application developers. A multi-program, parallel supercomputer is able to provide effective compute power by aggregating a host of lower-power processors using a network. The idea, in general, is that one either constructs the application to distribute parts to the different nodes and processors available and then collects the result (a parallel application), or one launches a large number of small jobs, each doing similar work on different subsets (a campaign). The I/O system on these machines is usually implemented as a tightly-coupled, parallel application itself. It is providing the concept of a 'file' to the host applications. The 'file' is an addressable store of bytes and that address space is global in nature. In essence, it is providing a global address space. Beyond the simple reality that the I/O system is normally composed of a small, less capable, collection of hardware, that concept of a global address space will cause problems if not very carefully utilized. How much of a problem and the ways in which those problems manifest will be different, but that it is problem prone has been well established. Worse, the file system is a shared resource on the machine - a system service. What an application does when it uses the file system impacts all users. It is not the case that some portion of the available resource is reserved. Instead, the I/O system responds to requests by scheduling and queuing based on instantaneous demand. Using the system well contributes to the overall throughput on the machine. From a solely self-centered perspective, using it well reduces the time that the application or campaign is subject to impact by others. The developer's goal should be to accomplish I/O in a way that minimizes interaction with the I/O system, maximizes the amount of data moved per call, and provides the I/O system the most information about the I/O transfer per request.
Wind turbines are often sited together in wind farms as it is economically advantageous. However, the wake inevitably created by every turbine will lead to a time-varying interaction between the individual turbines. Common practice in industry has been to control turbines individually and ignore this interaction while optimizing the power and loads of the individual turbines. However, turbines that are in a wake experience reduced wind speed and increased turbulence, leading to a reduced energy extraction and increased dynamic mechanical loads on the turbine, respectively. Neglecting the dynamic interaction between turbines in control will therefore lead to suboptimal behaviour of the total wind farm. Therefore, wind farm control has been receiving an increasing amount of attention over the past years, with the focus on increasing the total power production and reducing the dynamic loading on the turbines. In this paper, wind farm control-oriented modeling and control concepts are explained. In addition, recent developments and literature are discussed and categorized. This paper can serve as a source of background information and provides many references regarding control-oriented modeling and control of wind farms.
Within the rapidly growing wind energy sector, floating offshore wind turbines are expected to be the fastest growing portion. This is largely driven by the immense offshore wind resources that are mostly over deep water, where fixed-bottom concepts become cost prohibitive. However, compared to fixed-bottom wind turbines, floating wind turbines are more dynamic and exhibit potential instabilities, which requires advanced control technologies to ensure a safe and efficient operation. Beyond their existing objectives of maximizing power production while minimizing structural loads, floating wind turbine controllers must also avoid large platform oscillations and accommodate wave disturbances. This paper provides an overview of the challenges and opportunities in the control of floating offshore wind energy systems.