Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “FLAG”

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.

At least 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
DOE OSTI2024

Analyzing Risks of Virtual Private Network Connections

The use of Splunk for analyzing VPN logs is an effective approach for identifying vulnerabilities in network endpoints. Splunk, a powerful platform for searching, monitoring, and analyzing machine-generated data, enables organizations to aggregate VPN logs in real-time, providing insights into network activity, user behavior, and potential security risks. By indexing VPN traffic and authentication logs, security teams can track abnormal patterns such as multiple failed login attempts, unusual IP addresses, or unexpected changes in bandwidth usage, all of which could indicate potential vulnerabilities or breaches. With Splunk’s advanced search and reporting capabilities, users can create custom dashboards and alerts to detect suspicious activities. Automated searches can flag endpoints exhibiting unusual behavior, while correlation analysis can identify links between compromised devices and broader network vulnerabilities. In particular, Splunk's machine learning capabilities can be leveraged to predict and prevent threats by identifying trends that might otherwise be missed in traditional log analysis. This proactive approach to monitoring VPN logs allows for the early detection of security weaknesses, enabling rapid response and minimizing potential damage to network integrity. By enhancing endpoint visibility, Splunk plays a crucial role in securing remote connections and safeguarding sensitive information. Additionally, Splunk’s automation and alerting features allow teams to create custom workflows that notify them of vulnerable or misconfigured endpoints identified through Shodan. This synergy between Splunk’s log analysis and Shodan’s device intelligence enhances an organization’s ability to proactively identify and mitigate security risks, improving the overall resilience of their VPN infrastructure.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2025

Building Datasets and Training Methods for ML Based Magnet Quench Detection

Detecting quenches in superconducting (SC) magnets during training is a challenging process that involves capturing physical events that occur at different frequencies and appear as various signal features. These events may be correlated across instrumentation type, thermal cycle, and ramp. These events together build a more complete picture of continuous processes occurring in the magnet, and may allow us to flag potential precursors for quench detection. We present our work on building an automatic machine learning (ML) based quench detection system. We build upon our existing work on unsupervised auto-encoders for acoustic sensors and quench antenna (QA) by first establishing a supervised ML training pipeline. We show the results of an event tagging, analysis, and simulation framework on our QA and acoustic data which are used concurrently to build a training dataset for a supervised implementation. We then show how this supervised training can be used as a prior in a semi-supervised framework and compare this to the unsupervised neural network auto-encoder performance.This allows us to have a more concrete understanding of the performance of our algorithms relative to physical events occurring in the magnet, and also provides a baseline software tool to generically evaluate our quench prediction autoencoders under completely unsupervised, supervised, and semi-supervised training conditions.

Khan, Maira [Fermilab]↗
DOE OSTI2025

Regime Characterization of Offshore Wind Resource Using Unsupervised Learning

Predictability of wind resource conditions is critical for offshore wind design and operations. While many studies of extreme wind conditions focus on specific events such as low-level jets or ramps, these rely on threshold definitions that limit generality. Here we present a data-driven framework that combines principal component analysis (PCA), self-organizing maps (SOM), and k-means clustering to classify wind resource conditions as typical and anomalous from climatological data. Anomalies are defined not by fixed thresholds but by flagging samples located far from SOM node centers inside the baseline SOM structure. This reframes extremes as rare ebents and hence, likely difficult to anticipate by numerical weather prediction models. We applied this approach to 23 years (2000–2022) of hourly profiles from the NOW-23 hindcast model at the Humboldt Wind Energy Area. Classification is conducted on a feature space consisting of 10 m wind speed and direction, bulk shear and veer across 30–270 m, and a low-level jet index. Dimensionality reduction is achieved through PC. A 2 × 3 OM lattice trained on the PCA vectors identified six baseline regimes spanning weak to strong flow states. High quantization-error profiles are identified and re-clustered into four anomalous regimes. The baseline regimes exhibited clear seasonal and diurnal cycles. Meanwhile, the anomalous regimes represented <10 % of all hours but showed distinct combinations of speed, shear, and veer, when compared to the baseline regimes. Anomalous regimes are typically short-lived (~few hours), yet their transitions can lead to hub-height wind changes of −18 to +9 m s -1 . For a representative 15 MW turbine, these shifts imply rapid swings in capacity factor from near-full output to negligible generation. Validation with lidar buoy data showed 51% agreement in SOM labels across ~6,000 overlapping hours, with most mismatches confined to adjacent speed classes. HRRR comparisons further revealed that anomalous regimes were disproportionately associated with forecast biases exceeding 5 m s -1 . Together, these results reframe extremes in offshore wind from absolute maxima or minima to weather states that are difficult to anticipate from models.

17 WIND ENERGY↗
DOE OSTI2025

One-Dimensional Multi-Velocity Capabilities for Arbitrary Lagrangian-Eulerian Normal Contact Mechanics

Lagrangian and Arbitrary Lagrangian Eulerian (ALE) hydrodynamics codes such as FLAG form the backbone of many mission-critical multi physics simulations at Los Alamos National Laboratory. Critical to pre forming high fidelity simulations with these codes are Lagrangian and ALE contact algorithms, which allow materials to collide, slide, and sep arate throughout a simulation.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2025

Hazard Detection Detector Cards

This report presents a comprehensive summary of five advanced anomaly detection tools developed and deployed by Oak Ridge National Laboratory in support of the VA’s Health Information Technology modernization. These detectors—Order Path Tracker, Trend Watcher, Pain Pointer, Performance Monitor, and Patient Record Flag Detector—leverage statistical and machine learning methods to monitor workflow disruptions, detect anomalies in care sequences and volumes, identify bottlenecks, and track system-level performance metrics across VistA and Millennium systems. All detectors have been integrated into the Health Data Analytics Platform (HDAP), with most having completed deployment and testing using live data from targeted stations in cardiology and oncology domains. This work enhances VA’s capacity for proactive system surveillance, promotes patient safety, and informs data-driven operational improvements across the EHR ecosystem.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2025

CLEAP Project: OR-SAGE Analysis for MT, UT, and CO States

The OR-SAGE tool is designed to use industry-accepted practices in screening sites and then employ the proper array of data sources through the considerable computational capabilities of GIS technology available at ORNL. The tool was developed to screen the potential for NPP siting on a national and regional basis. However, because of the tool granularity, it is often focused specifically on the immediate area around user sites of interest. If data center siting parameters can be added to OR-SAGE, the ability to evaluate data center siting on a localized scale will be beneficial.1 More than 60 data sets have been collected and processed by ORNL to develop exclusionary, avoidance, and suitability criteria for screening sites for a variety of power generation types, including nuclear power plants. Available site evaluation parameters include population density, slope, seismic activity, proximity to cooling-water sources, proximity to hazard facilities, avoidance of protected lands and floodplains, susceptibility to landslide hazards, and many others. All siting parameters should be considered as flags to inform siting decisions and should not be used to rule in or rule out any NPP site. Once data center siting parameters are identified, appropriate data sets will be collected and processed. The OR-SAGE process is very versatile. Essentially, OR-SAGE is a visual, relational database. The database partitions the contiguous United States, a total of 720 million hectares (~1.8 billion acres), into 100-m by 100-m (1 hectare or ~2.5 acre) cells. The database is tracking just under 700 million individual land cells. Successive suitability criterion is applied to each cell in the database. User-specified thresholds can be applied to each siting parameter data layer. In this manner, a variety of scenarios can be quickly and thoroughly evaluated. Data can be added and/or revised within OR-SAGE to address user interests. Siting security assessment capability is currently being added to OR-SAGE. Security is expected to be of concern at data centers whether it is collocated with a nuclear power generating technology or not. If data center is collocated with a nuclear power generating source, the security threat attractiveness level of both will likely increase. It will be of additional benefit if a potential data center site is also assessed for security vulnerability.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2023

Quantification of LEU Holdup using gamma ray imaging and inverse transport solver

Holdup is the residual amount of special nuclear material (SNM) remaining in a processing facility after the bulk materials have been cleaned out. In commercial uranium processing facilities, quantification of holdup is a major challenge because of the highly variable shapes and sizes of the deposits. Any method that attempts to generalize and calibrate deposit shapes in order to quantify holdup will be prone to high uncertainties. Uncertainties on the order of ±50% are typical in holdup results. In international safeguards applications, a ±50% uncertainty can result in a large amount of material unaccounted for (MUF) thereby increasing the difficulty of detecting material diversion and facility misuse. An imaging-based methodology has been developed with the objective of significantly reducing this uncertainty by using the true deposit shape, instead of relying on oversimplified geometric assumptions. The project is a collaboration between ORNL, Y-12, and the University of Tennessee, Knoxville, TN. Uranium sources of known masses were measured using the Germanium Gamma-ray Imager (GeGI), a high-resolution imaging spectrometer, creating a pixelated map for each spectral bin. Two different gamma imaging methods are employed in this work: coded aperture imaging and Compton imaging. A validated MonteCarlo model of the detector has been developed using the GEANT4 code for determining the intrinsic response of the detector, its enclosure, and the coded aperture mask. An inverse transport solver based on the Markov Chain Monte-Carlo approach known as Differential Evolution Adaptive Metropolis (DREAM) is employed to use the measurement data from the image pixels (coded aperture or Compton) to solve for the mass of 235 U in the deposit. A reliable method based on the DREAM solver has been developed to flag the infinite thickness condition of a uranium deposit. The project team is working towards improving the image reconstruction for Compton imaging so that a better localization of the source can be achieved. Besides treating the coded aperture and Compton imaging methods independently, the project is also evaluating a combined method that uses the Compton scatter data from a coded aperture measurement. GEANT4 simulations are being performed to evaluate the combined approach. The impact on the DREAM optimization as the source thickness progressively approaches infinite thickness is being evaluated. A number of uranium sources available at ORNL have been measured, and the DREAM results have been tested and validated for the coded aperture imaging. A similar effort will be carried out to validate the Compton based method once the development of algorithms for better localization are complete. The imaging based quantification is very amenable to unattended monitoring of holdup accumulation at key measurement points. A proof of concept measurement has been completed to demonstrate this capability The current work used the high energy resolution imager GeGI. However, the approach and methodologies are applicable to other imagers such as the cadmium zin telluride (CZT) based imager manufactured by H3D, Inc.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence Q - Raw Data

Sequence Q: Dynamic Inflow (P) This sequence was designed to characterize the dynamic inflow variation using the five-hole probes that extend upwind of the leading edge of the blade. This test sequence used an upwind, rigid turbine with a 0° cone angle. The wind speeds ranged from 5 m/s to 15 m/s, and data were collected at a 0° yaw angle. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to -99999.99 Nm. The teeter link load cell was pretensioned to 40,000 N. The blade pitch angle was changed from the initial tip pitch angle to the final tip pitch angle at the maximum rate of 67°/s. This angle was maintained for the specified delay time duration. Then the blade was pitched back to the initial pitch angle and held for the specified hold time. This was repeated 20 times. The campaign at 15 m/s was aborted early due to excessive low-speed shaft torque loads. The file length varied depending on the time required to obtain 20 pitch cycles for the specified range of angles. The name convention was the standard format, except for the short campaigns collected to ascertain the functionality of the instrumentation. These points were collected at a 3° pitch angle and use the characters REF in the four digits that normally represent yaw angle.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence W - Raw Data

Sequence W: Extended Blade (F) This test sequence used an upwind, rigid turbine with a 0° cone angle. The wind speed ranged from 5 m/s to 21 m/s, and the yaw angle was held at 0°. The blade pitch angle was 3°. The rotor rotated at 72 RPM. Blade pressure measurements were collected. The five-hole probes were removed and the plugs were installed. Plastic tape 0.03-mm thick was used to smooth the interface between the plugs and the blade. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pretensioned to 40,000 N. During postprocessing, the probe channels were set to read –99999.99. The standard tip blocks were replaced with blade extensions that created a 5.532-m radius rotor as shown in Appendix A. The extension used the S809 airfoil throughout, and the linear taper of the blade continued along the extension. Note that the blade radius was not changed during post-processing so the pressure tap locations are at the same radial location, but the reference to 30% represents 30% of 5.029 m, not 5.532 m. Throughout this report, references to the blade span are made for the 5.029-m radius, not the 5.532-m radius.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence 5 - Raw Data

Sequence 5: Sweep Wind Speed (F,P) This test sequence used an upwind, rigid turbine with a 0° cone angle. The wind speed was ramped from 5 m/s to 25 m/s by the wind tunnel operator. This was repeated with a decreasing ramp. The yaw angle was maintained at 0°. The blade tip pitch was 3° or 6°. The rotor rotated at 72 RPM. Blade pressure and probe measurements were collected for both pitch angles. The five-hole probes were removed and the plugs were installed for another 3° pitch case. Plastic tape 0.03 mm thick was used to smooth the interface between the plugs and the blade. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. During post-processing, the probe channels were set to read -99999.99. The 6- minute campaigns were named using the sequence designation 5, followed by DN or UP, which indicates the wind speed ramp direction. The next four digits are 0000, and the sequence digit is at the end.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence E - Raw Data

Sequence E: Yaw Releases (P) This test sequence used a downwind, rigid turbine with a 3.4° cone angle. The wind speeds ranged from 7 m/s to 17 m/s. Initial yaw angles of ±90° were achieved. The blade tip pitch was 3°. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. The turbine was positioned at each specified yaw angle. A 30- second data set was collected with the yaw brake engaged. These points used a letter for the last digit beginning with A and proceeding through the alphabet as repeat points were needed. These points were plotted and compared to ascertain the functionality of the instrumentation. The files ending in numbers beginning with 0 and increasing with each repetition represent yaw release points. Once the fixed-position yaw test was complete, the yaw drive was engaged to hold the turbine. The yaw brake was released, and the yaw drive was disabled allowing the turbine to yaw freely. The yaw drive was disabled about 5 seconds into the campaign, and the turbine was allowed to yaw freely for the rest of the 30-second duration. When the yaw drive is disabled, no torque is applied to the motor, and the inertia and yawing force of the nacelle and rotor overcomes the friction and inertia of the yaw gear and motor. The yaw releases were repeated five times at each condition. Four additional campaigns were collected to determine the turbine’s natural yaw error by releasing the brake at 0° yaw error. These file names use the E designation, followed by two digits for wind speed, followed by XXXX, followed by the repetition digit.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence K - Raw Data

Sequence K: Step AOA, Probes (P) This sequence was designed to quantify the 3-D blade static angle-of-attack response in the presence of rotational influences by varying the blade pitch angle. Sequence K used an upwind, rigid turbine with a 0° cone angle. The wind speeds ranged from 6 m/s to 20 m/s, and data were collected at yaw angles of 0° and 30°. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to -99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. The blade pitch angle ramped continuously at 0.18°/s over a wide range of increasing and decreasing pitch angles. A step sequence was also performed. The blade pitch was stepped 5°, the flow was allowed to stabilize, and the pitch angle was held for 8 seconds. Then the pitch angle step was repeated. Again, a wide range of pitch angles was obtained, both increasing and decreasing. The file lengths for this sequence varied from 96 seconds to 6 minutes, depending on the pitch angle range. Some short points were collected at 0° yaw and 3° pitch to verify the functionality of the instrumentation. The file name convention used the initial letter K, followed by two digits specifying wind speed, followed by two digits for yaw angle, followed by RU, RD, or ST, followed by the repetition digit. The angle-of-attack motion was differentiated by RU (ramp up), RD (ramp down), and ST (step down then step up). This sequence is related to sequences L and R.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence 7 - Raw Data

Sequence 7: Shroud Operating (P) This test sequence used a downwind, rigid turbine with a 3.4° cone angle. The wind speed ranged from 5 m/s to 25 m/s. Turntable angles from 0° to 30° were achieved, but the yaw error angle was maintained at 0° by adjusting the nacelle yaw. The blade tip pitch was 3°. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. An airfoil-shaped aluminum shroud was placed on the tower below the 34% span five-hole probe. It extended below the 91% span five-hole probe. The turntable angle was adjusted to position the shroud at various angles relative to the flow, but the turbine yaw error angle was maintained at 0°. Two additional points were collected where the turntable angle was 0°, and the turbine yaw angle was 20° (71000200) or -20° (710M0200).

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence H - Raw Data

Sequences H, I, and J: Upwind Baseline (F), Upwind Low Pitch (F), Upwind High Pitch (F) This test sequence used an upwind, rigid turbine with a 0° cone angle. The wind speed ranged from 5 m/s to 25 m/s. Yaw angles of –30 to 180° were achieved at low wind speeds, and angles of ±10° were achieved for high wind speeds. The blade tip pitch was 3° for sequence H, 0° for sequence I, and 6° for sequence J. These three sequences were interleaved during testing because the pitch angle change was easily made by the turbine operator. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pretensioned to 40,000 N. In addition to the standard 30-second campaigns, yaw sweeps were done at 7 m/s and 10 m/s. These 6-minute campaigns were collected while the yaw drive rotated the turbine 360° at a rate of 1°/s. The file names for these campaigns use the letter designation, followed by two digits for wind speed, followed by YS, followed by 000.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence I - Raw Data

Sequences H, I, and J: Upwind Baseline (F), Upwind Low Pitch (F), Upwind High Pitch (F) This test sequence used an upwind, rigid turbine with a 0° cone angle. The wind speed ranged from 5 m/s to 25 m/s. Yaw angles of –30° to 180° were achieved at low wind speeds, and angles of ±10° were achieved for high wind speeds. The blade tip pitch was 3° for sequence H, 0° for sequence I, and 6° for sequence J. These three sequences were interleaved during testing because the pitch angle change was easily made by the turbine operator. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. In addition to the standard 30-second campaigns, yaw sweeps were done at 7 m/s and 10 m/s. These 6-minute campaigns were collected while the yaw drive rotated the turbine 360° at a rate of 1°/s. The file names for these campaigns use the letter designation, followed by two digits for wind speed, followed by YS, followed by 000.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence J - Raw Data

Sequences H, I, and J: Upwind Baseline (F), Upwind Low Pitch (F), Upwind High Pitch (F) This test sequence used an upwind, rigid turbine with a 0° cone angle. The wind speed ranged from 5 m/s to 25 m/s. Yaw angles of –30° to 180° were achieved at low wind speeds, and angles of ±10° were achieved for high wind speeds. The blade tip pitch was 3° for sequence H, 0° for sequence I, and 6° for sequence J. These three sequences were interleaved during testing because the pitch angle change was easily made by the turbine operator. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to –99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. In addition to the standard 30-second campaigns, yaw sweeps were done at 7 m/s and 10 m/s. These 6-minute campaigns were collected while the yaw drive rotated the turbine 360° at a rate of 1°/s. The file names for these campaigns use the letter designation, followed by two digits for wind speed, followed by YS, followed by 000.

17 WIND ENERGY↗
DOE OSTI2022

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence L - Raw Data

Sequence L: Step AOA, Parked (P) This sequence was designed to quantify the 3-D blade static angle-of-attack response in the absence of rotational influences by varying the blade pitch angle. This test sequence used an upwind, rigid turbine with a 0° cone angle. Wind speeds of 20 m/s and 30 m/s were used, and all data were collected at a yaw angle of 0°. The rotor was parked with the instrumented blade fixed at 0° azimuth, and the rotor lock was installed (see Appendix A). Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to -99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. The blade pitch angle ramped continuously at 0.18°/s over a wide range of increasing and decreasing pitch angles. A step sequence was also performed. The blade pitch was stepped 5°, the flow was allowed to stabilize, and the pitch angle was held for 8 seconds. Then the pitch angle step was repeated. Again, a wide range of pitch angles was obtained, both increasing and decreasing. The file lengths for this sequence varied from 5 to 10 minutes, depending on the pitch angle range. The file name convention used the initial letter L followed by two digits specifying wind speed, followed by 00 for yaw angle, followed by RU, RD, or ST, followed by the repetition digit. The angle-of-attack motion was differentiated by RU (ramp up), RD (ramp down), and ST (step down, then step up). This sequence is related to sequences K and R.

17 WIND ENERGY↗