Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Deep Lynx”

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.

Deep Lynx MOOSE Adapter

The Deep Lynx MOOSE Adapter connects the Deep Lynx data warehouse with any MOOSE executable. The Adapter can receive events from Deep Lynx and will take incoming data to format a template input file for the MOOSE executable. Returns from the MOOSE run are sent back to Deep Lynx for use by other applications.

Browning, JerenM↗

Deep Lynx Unidirectional Network Connector

The Deep Lynx UNC is a small utility written in Python that uses only basic Python libraries and the Deep Lynx Python Software Development Kit (SDK). It queries Deep Lynx for tasks that indicate some data to be run in the UNC's environment. Once a task is acquired, the UNC retrieves the associated data and provides it to some other application for processing, waits for output, and sends the output from the other application to Deep Lynx. As data flows only from the UNC to Deep Lynx, this software solves the problem of connecting Deep Lynx with applications and resources that exist in a network where the network can reach Deep Lynx, but Deep Lynx cannot reach that network (unidirectional network).

Browning, JerenM↗

Deep Lynx Matlab Adapter

The Deep Lynx MATLAB Adapter is a Python application that connects the Deep Lynx data warehouse with any MATLAB simulation.

Wilsdon, KatherineN [Idaho National Laboratory] (0↗

Deep-Lynx-ML-Adapter

The Deep Lynx Machine Learning (ML) Adapter is a generic adapter that programmatically runs the ML as continuous data is received. Then, Jupyter Notebooks can be customized according to the project for pre-processing the data, building the machine learning models, prediction analysis of incoming data using an existing model, and forecasting anomalies / failures of the physical asset.

Wilsdon, KatherineN↗

Deep-Lynx-Python-Package

This software is a python package that interacts with the Application Programming Interface (API) suite provided by Deep Lynx. A python codebase may import this package in order to have access to these methods for communicating with a Deep Lynx instance.

Browning, JerenM↗

Deep Lynx Javascript Package

This software is a JavaScript package that interacts with the Application Programming Interface (API) suite provided by Deep Lynx. A JavaScript or TypeScript codebase may import this package in order to have access to these methods for communicating with a Deep Lynx instance.

Browning, JerenM↗

Deep Lynx Data Historian

This software is intended to facilitate the ingestion of data from some data historian into Deep Lynx. A data historian in this instance is any location where sensor and operational data from some live asset is gathered. The data can be either manual retrieved by this software or the data historian source can push to a listening endpoint provided by this software.

Browning, JerenM↗

Deep Lynx: Digital Engineering Integration Hub

The construction of megaprojects has consistently demonstrated challenges for project managers in regard to meeting cost, schedule, and performance requirements. Megaproject construction challenges are common place within megaprojects with many active projects in the United States failing to meet cost and schedule efforts by significant margins. Currently, engineering teams operate in siloed tools and disparate teams where connections across design, procurement, and construction systems are translated manually or over brittle point-to-point integrations. The manual nature of data exchange increases the risk of silent errors in the reactor design, with each silent error cascading across the design. These cascading errors lead to uncontrollable risk during construction, resulting in significant delays and cost overruns. Deep Lynx allows for an integrated platform during design and operations of mega projects.

Darrington, JohnW↗

Real-Time Optimization Workflow Status Update

Economically optimal and safe operation of integrated energy systems (IES) requires optimization at many different time scales. A real-time optimization (RTO) workflow will attempt to maximize revenue and minimize operational costs on a time scale of minutes to hours. Such a workflow requires the use of a digital twin (DT), which is a virtual representation of a physical system. The DT is updated using real-time data from the physical system, and serves as a model in an optimization framework. The optimization results are then sent back to the physical system to complete the loop. This report details the progress made in developing building blocks for a DT/RTO framework. The Risk Analysis Virtual Environment (RAVEN) platform within the Framework for Optimization of Resources and Economics (FORCE) tool suite can perform many of the tasks required for building a DT and performing RTO. The first item of this report details RAVEN enhancements that enable RAVEN workflows to be run in various environments. Data communication between the physical system and its DT is essential for successful RTO. This includes preprocessing real-time data, loading data into a data warehouse, and querying the stored data. The second section of this report describes the progress made in implementing an adapter in Python in order for Deep Lynx to handle the data communication. Typical dispatch optimization frameworks are built on linear programming (LP). The prototype RTO workflow developed in this report uses an LP problem as a part of a receding-horizon- or economic model predictive control (EMPC) based optimization. The third section of this report details the framework of an RTO workflow in which the system consists of a simple electrical storage device. A DT can be built from a reduced-order model (ROM). Integrating a ROM into a typical LP optimization framework has been challenging because most optimization packages require the user to write algebraic expressions for the system model. The final section of this report shows how an externally built RAVEN ROM can be integrated in an RTO framework by using the Python package Pyomo. This demonstrates the RTO workflow capability from a software-only perspective and is an important step in demonstrating the capability to implement an RTO workflow for a physical system.

97 MATHEMATICS AND COMPUTING↗

Initial results from a ROSAT deep survey in Lynx

Preliminary results from a deep (70 ksec) Rosat survey of the high galactic latitude selected area Lynx.3A are presented. Lynx.3A sensitivity was previously studied in both the optical radio, with deep Westerbork surveys and deep multicolor Charge Couple Device (CCD) images form the Palomar 200 inch Four-Shooter. About 70 x-ray sources were detected within the central 40 foot diameter region of the Position Sensitive Proportional Counter (PSPC), observed surface densities of approximately 200 x-ray sources/sq deg are suggested, and these x-ray sources alone account for approximately 30 percent of the cosmic x-ray background (0.9 to 2.2 keV). An initial look at the observed x-ray logN - logS curve is presented, but a detailed assessment requires further study. The 4 sigma limit of about 7 times 10 to the minus 15th power erg/s.sq cm (0.5 to 2.0 keV) is considerably deeper then the Einstein deep surveys, and of comparable sensitivity to the deepest current Rosat surveys. Cross correlation with our Four Shooter optical catalogs yields at least one likely optical candidate for nearly all of the Rosat x-ray sources; a number of the likely optical identifications have colors of quasi-stellar objects (and stellar PSF), but in other cases galaxies/groups are also viable candidates.

Anderson, S. F.↗

Cyote Insights

CyOTE Insights leverages React, Vite, Typescript, Tailwind, and Daisy UI for the Graphical User Interface. It was designed in a particular style with a dark mode and a light mode. All code is broken down into components and reusable wrapper components for efficiency. All data is stored in Deep Lynx as a central data repository using an ontology based schema. The application serves as a main endpoint for the data in the COREII and CyOTE programs. The main purpose of the application is to display historical attack data in the Operational Technology space. At the time of this writing, it supports 27 historical attack reports compiled from OSINT sources. All of the data is publicly available, but what this application offers is the ability to see many years worth of publications in a detailed dashboard. It will also support future reports that are written using the other applications in the COREII program.

Pluth, AdamJ [Idaho National Laboratory (INL), Ida↗

Digital Engineering & Data Acquisition

This is an Intern Poster submission regarding my research in the digital engineering team. My task was to create a software adapter to communicate between a data acquisition system (LabVIEW) and a data warehouse (Deep Lynx) as described in the poster.

99 GENERAL AND MISCELLANEOUS↗

Summary of Work on a Software Adapter for Project Requirements and MBSE

The National Reactor Innovation Center (NRIC) has funded the development of a digital pipeline to pull a project’s requirements from IBM’s Rational Dynamic Object Oriented Requirements System (DOORS), save them to Deep Lynx, then push them into the corresponding project in Innoslate. These utilities are accessible from a web browser and allow a project’s functional and business requirements to be tied to its tree of model-based systems engineering (MBSE) data.

99 GENERAL AND MISCELLANEOUS↗

EARLY-TYPE GALAXIES AT z {approx} 1.3. IV. SCALING RELATIONS IN DIFFERENT ENVIRONMENTS

We present the Kormendy and mass-size relations (MSR) for early-type galaxies (ETGs) as a function of environment at z {approx} 1.3. Our sample includes 76 visually classified ETGs with masses 10{sup 10} < M/M{sub Sun} < 10{sup 11.5}, selected in the Lynx supercluster and in the Great Observatories Origins Deep Survey/Chandra Deep Field South field; 31 ETGs in clusters, 18 in groups, and 27 in the field, all with multi-wavelength photometry and Hubble Space Telescope/Advanced Camera for Surveys observations. The Kormendy relation, in place at z {approx} 1.3, does not depend on the environment. The MSR reveals that ETGs overall appear to be more compact in denser environments: cluster ETGs have sizes on average around 30%-50% smaller than those of the local universe and a distribution with a smaller scatter, whereas field ETGs show an MSR with a similar distribution to the local one. Our results imply that (1) the MSR in the field did not evolve overall from z {approx} 1.3 to present; this is interesting and in contrast to the trend found at higher masses from previous works; (2) in denser environments, either ETGs have increased in size by 30%-50% on average and spread their distributions, or more ETGs have been formed within the dense environment from non-ETG progenitors, or larger galaxies have been accreted to a pristine compact population to reproduce the MSR observed in the local universe. Our results are driven by galaxies with masses M {approx}< 2 Multiplication-Sign 10{sup 11} M{sub Sun} and those with masses M {approx} 10{sup 11} M{sub Sun} follow the same trends as that of the entire sample. Following the Valentinuzzi et al. definition of superdense ETGs, {approx}35%-45% of our cluster sample is made up of superdense ETGs.

79 ASTRONOMY AND ASTROPHYSICS↗

RX J0848.6+4453: The evolution of galaxy sizes and stellar populations in A z = 1.27 cluster

RX J0848.6+4453 (Lynx W) at redshift 1.27 is part of the Lynx Supercluster of galaxies. We present an analysis of the stellar populations and star formation history for a sample of 24 members of the cluster. Our study is based on deep optical spectroscopy obtained with Gemini North combined with imaging data from Hubble Space Telescope. Focusing on the 13 bulge-dominated galaxies for which we can determine central velocity dispersions, we find that these show a smaller evolution with redshift of sizes and velocity dispersions than reported for field galaxies and galaxies in poorer clusters. Our data show that the galaxies in RX J0848.6+4453 populate the fundamental plane (FP) similar to that found for lower-redshift clusters. The zero-point offset for the FP is smaller than expected if the cluster's galaxies are to evolve passively through the location of the FP we established in our previous work for z = 0.8-0.9 cluster galaxies and then to the present-day FP. The FP zero point for RX J0848.6+4453 corresponds to an epoch of last star formation at z{sub form}=1.95{sub −0.15}{sup +0.22}. Further, we find that the spectra of the galaxies in RX J0848.6+4453 are dominated by young stellar populations at all galaxy masses and in many cases show emission indicating low-level ongoing star formation. The average age of the young stellar populations as estimated from the strength of the high-order Balmer line Hζ is consistent with a major star formation episode 1-2 Gyr prior, which in turn agrees with z {sub form} = 1.95. These galaxies dominated by young stellar populations are distributed throughout the cluster. We speculate that low-level star formation has not yet been fully quenched in the center of this cluster, possibly because the cluster is significantly poorer than other clusters previously studied at similar redshifts, which appear to have very little ongoing star formation in their centers. The mixture in RX J0848.6+4453 of passive galaxies with young stellar populations and massive galaxies still experiencing some star formation appears similar to the galaxy populations recently identified in two z ≈ 2 clusters.

79 ASTRONOMY AND ASTROPHYSICS↗

Development of Space-Flight Compatible Room-Temperature Electronics for the Lynx X-Ray Microcalorimeter

We are studying the development of space-flight compatible room-temperature electronics for the Lynx x-ray microcalorimeter (LXM) of the Lynx mission. The baseline readout technique for the LXM is microwave SQUID multiplexing. The key modules at room temperature are the RF electronics module and the digital electronics and event processor (DEEP). The RF module functions as frequency converters and mainly consists of local oscillators and I/Q mixers. The DEEP performs demultiplexing and event processing, and mainly consists of field-programmable gate arrays, ADCs, and DACs. We designed the RF electronics and DEEP to be flight ready, and estimated the power, size, and mass of those modules. There are two boxes each for the RF electronics and DEEP for segmentation, and the sizes of the boxes are 13 in: × 13 in: × 9 in: for the RF electronics and 15.5 in: × 11.5 in: × 9.5 in: for the DEEP. The estimated masses are 25.1 kg∕box for the RF electronics box and 24.1 kg∕box for the DEEP box. The maximum operating power for the RF electronics is 141 W or 70.5 W∕box, and for the DEEP box is 615 W or 308 W∕box. The overall power for those modules is 756 W. We describe the detail of the designs as well as the approaches to the estimation of resources, sizes, masses, and powers.

Sakai, Kazuhiro↗