Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “IMPLEMENTATION”

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 1,387 records · Page 77
All sourcesNASA NTRSDOE OSTI
NASA NTRS1973

Implementation of a self-controlling heater

Temperature control of radiation sensors, targets, and other critical components is a common requirement in modern scientific instruments. Conventional control systems use a heater and a temperature sensor mounted on the body to be controlled. For proportional control, the sensor provides feedback to circuitry which drives the heater with an amount of power proportional to the temperature error. It is impractical or undesirable to mount both a heater and a sensor on certain components such as ultra-small parts or thin filaments. In principle, a variable current through the element is used for heating, and the change in voltage drop due to the element's temperature coefficient is separated and used to monitor or control its own temperature. Since there are no thermal propagation delays between heater and sensor, such control systems are exceptionally stable.

Strange, M. G.↗
NASA NTRS1973

Investigation using data from ERTS to develop and implement utilization of living marine resources

The author has identified the following significant results. The feasibility of utilizing ERTS-1 data in conjunction with aerial remote sensing and sea truth information to predict the distribution of menhaden in the Mississippi Sound during a specific time frame has been demonstrated by employing a number of uniquely designed empirical regression models. The construction of these models was made possible through innovative statistical routines specifically developed to meet the stated objectives.

Stevenson, W. H.↗
NASA NTRS1973

NASIS data base management system: IBM 360 TSS implementation. Volume 2: Overviews

The system overviews of the NASA Aerospace Safety Information System (NASIS) are presented. The overviews are directed toward informing management of a systems capabilities and requirements. The intent of the overviews contains a description of the component's activities and role in the overall system. The description includes charts and diagrams and discussions of the performance requirements and growth potential of the module.

Source record↗
NASA NTRS1973

NASIS data base management system: IBM 360 TSS implementation. Volume 3: Data set specifications

The data set specifications for the NASA Aerospace Safety Information System (NASIS) are presented. The data set specifications describe the content, format, and medium of communication of every data set required by the system. All relevant information pertinent to a particular data set is prepared in a standard form and centralized in a single document. The format for the data set is provided.

Source record↗
NASA NTRS1973

NASIS data base management system: IBM 360 TSS implementation. Volume 4: Program design specifications

The design specifications for the programs and modules within the NASA Aerospace Safety Information System (NASIS) are presented. The purpose of the design specifications is to standardize the preparation of the specifications and to guide the program design. Each major functional module within the system is a separate entity for documentation purposes. The design specifications contain a description of, and specifications for, all detail processing which occurs in the module. Sub-models, reference tables, and data sets which are common to several modules are documented separately.

Source record↗
NASA NTRS1973

NASIS data base management system: IBM 360 TSS implementation. Volume 5: Retrieval command system reference manual

The retrieval command subsystem reference manual for the NASA Aerospace Safety Information System (NASIS) is presented. The command subsystem may be operated conversationally or in the batch mode. Retrieval commands are categorized into search-oriented and output-oriented commands. The characteristics of ancillary commands and their application are reported.

Source record↗
NASA NTRS1973

NASIS data base management system: IBM 360 TSS implementation. Volume 6: NASIS message file

The message file for the NASA Aerospace Safety Information System (NASIS) is discussed. The message file contains all the message and term explanations for the system. The data contained in the file can be broken down into three separate sections: (1) global terms, (2) local terms, and (3) system messages. The various terms are defined and their use within the system is explained.

Source record↗
NASA NTRS1973

NASIS data base management system - IBM 360/370 OS MVT implementation. 1: Installation standards

The installation standards for the NASA Aerospace Safety Information System (NASIS) data base management system are presented. The standard approach to preparing systems documentation and the program design and coding rules and conventions are outlined. Included are instructions for preparing all major specifications and suggestions for improving the quality and efficiency of the programming task.

Source record↗
NASA NTRS1973

NASIS data base management system - IBM 360/370 OS MVT implementation. 2: Overviews

The systems overviews of the NASA Aerospace Safety Information System (NASIS) are presented. The overviews are directed toward informing management of a system's capabilities and requirements. The intent of the overviews is to introduce the system features to interested individuals. Each overview contains a description of the component's activities and roles in the overall system. The description includes charts and diagrams and a discussion of the performance requirements and growth potential of the module.

Source record↗
NASA NTRS1973

NASIS data base management system - IBM 360/370 OS MVT implementation. 3: Data set specifications

The data set specifications for the NASA Aerospace Safety Information System (NASIS) are presented. The data set specifications describe the content, format, and medium of communication of every data set required by the system. All relevant information pertinent to a particular set is prepared in a standard form and centralized in a single document. The format for the data set is provided.

Source record↗
NASA NTRS1973

NASIS data base management system - IBM 360/370 OS MVT implementation. 4: Program design specifications

The design specifications for the programs and modules within the NASA Aerospace Safety Information System (NASIS) are presented. The purpose of the design specifications is to standardize the preparation of the specifications and to guide the program design. Each major functional module within the system is a separate entity for documentation purposes. The design specifications contain a description of, and specifications for, all detail processing which occurs in the module. Sub-modules, reference tables, and data sets which are common to several modules are documented separately.

Source record↗
NASA NTRS1973

NASIS data base management system - IBM 360/370 OS MVT implementation. 5: Retrieval command system reference manual

The retrieval command subsystem reference manual for the NASA Aerospace Safety Information System (NASIS) is presented. The output oriented classification of retrieval commands provides the user with the ability to review a set of data items for verification or inspection as a typewriter or CRT terminal and to print a set of data on a remote printer. Predefined and user-definable data formatting are available for both output media.

Source record↗
NASA NTRS1973

NASIS data base management system - IBM 360/370 OS MVT implementation. 6: NASIS message file

The message file for the NASA Aerospace Safety Information System (NASIS) is discussed. The message file contains all the message and term explanations for the system. The data contained in the file can be broken down into three separate sections: (1) global terms, (2) local terms, and (3) system messages. The various terms are defined and their use within the system is explained.

Source record↗