Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “data management”

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 379 records · Page 21
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

Developing and Managing Data Acquisition Software Using Spack

The Data Acquisition systems of particle physics experiments regularly push the boundaries of high-throughput computing, demanding low-latency collection of data from thousands of devices, collating data into time-sliced events, processing these events and making trigger decisions, and writing the selected data streams to disk. To accomplish these tasks, the DAQ Engineering and Operations department at Fermilab leverages multiple software libraries and builds reusable DAQ frameworks on top. These libraries must be delivered in well-defined bundles and are thoroughly tested for compatibility and functionality before being deployed to live detectors. We have several techniques used to ensure that a consistent set of dependencies can be delivered and re-created at need. We must also support active development of DAQ software components, ideally in an environment as close as possible to that of the detectors. This development often occurs across multiple packages which have to be built in concert and features tested in a consistent and reproducible manner. I will present our scheme for accomplishing these goals using Spack environments, bundle packages, and Github Actions-based CI.

Flumerfelt, Eric [Fermilab]↗
NASA NTRS1972

Advanced software techniques for data management systems. Volume 3: Programming language characteristics and comparison reference

A comparative evaluation was made of eight higher order languages of general interest in the aerospace field: PL/1; HAL; JOVIAL/J3; SPL/J6; CLASP; ALGOL 60; FORTRAN 4; and MAC360. A summary of the functional requirements for a language for general use in manned aerodynamic applications is presented. The evaluation supplies background material to be used in assessing the worth of each language for some particular application.

James, T. A.↗
NASA NTRS1974

Life sciences payload definition and integration study. Volume 4: Appendix, costs, and data management requirements of the dedicated 30-day laboratory

The results of the updated 30-day life sciences dedicated laboratory scheduling and costing activities are documented, and the 'low cost' methodology used to establish individual equipment item costs is explained in terms of its allowances for equipment that is commerical off-the-shelf, modified commercial, and laboratory prototype; a method which significantly lowers program costs. The costs generated include estimates for non-recurring development, recurring production, and recurring operations costs. A cost for a biomedical emphasis laboratory and a Delta cost to provide a bioscience and technology laboratory were also generated. All cost reported are commensurate with the design and schedule definitions available.

Source record↗
NASA NTRS1977

Data-management and information system

User command language consists of unabbreviated English words. System allows user to create, delete, sort, merge, update, punch, or transfer all or portion of any file in system without programmer assistance.

Long, J. J.↗
NASA NTRS1975

AMPS data management requirements study, appendix 1

Flow charts and display formats for the simulation of five experiments are given. The experiments are: (1) electromagnetic wave transmission; (2) passive observations of ambient plasma; (3) ionospheric measurements with subsatellite; (4) electron accelerator beam measurements; and (5) measurement of acoustical gravity waves in the sodium layer using lasers. A detailed explanation of the simulation procedure, definition of variables, and an explanation of how the experimenter makes display choices is also presented. A functional description is included on each flow chart and the assumptions and definitions of terms and scope of the flow charts and displays are presented.

Source record↗