Refine Your Search

Date

Date

Topic

Topic

Author

Author

Affiliation

Affiliation

Search Results

Viewing 125201 to 125220 of 197012
<< First< Previous62596260626162626263Next >Last >>
Sort by relevance
Standard

Function-Based API for Gas Turbine Engine Performance Programs
2016-08-01
CURRENT
ARP4868C
The SAE Aerospace Standard document AS681 is the parent document of this SAE Aerospace Recommended Practice (ARP). AS681 applies to Engine programs written to conform to this document. This ARP specifies a set of functions and their expected behaviors that constitute a function based Application Program Interface (API) for gas turbine engine customer programs. The functions specified in this API are delivered by the Supplier as part of the Engine model. This document defines generic language independent functions and specific appendices for implementations in C and Fortran. The function based API specified in this ARP represents an alternative to the Fortran COMMON block structure, as specified in AS4191, historically used to communicate with an engine program. The customer may request emulation of the AS4191 interface if desired.
Standard

Function-Based API for Gas Turbine Engine Performance Programs
2011-05-23
HISTORICAL
ARP4868A
The SAE Aerospace Standard document AS681 is the parent document of this SAE Aerospace Recommended Practice (ARP). AS681 applies to Engine programs written to conform to this document. This ARP specifies a set of functions and their expected behaviors that constitute a function based Application Program Interface (API) for gas turbine engine customer programs. The functions specified in this API are delivered by the Supplier as part of the Engine model. This document defines generic language independent functions and specific appendices for implementations in C and Fortran. The function based API specified in this ARP represents an alternative to the Fortran COMMON block structure, as specified in AS4191, historically used to communicate with an engine program. The customer may request emulation of the AS4191 interface if desired.
Standard

Function-Based API for Gas Turbine Engine Performance Programs
2013-05-07
HISTORICAL
ARP4868B
The SAE Aerospace Standard document AS681 is the parent document of this SAE Aerospace Recommended Practice (ARP). AS681 applies to Engine programs written to conform to this document. This ARP specifies a set of functions and their expected behaviors that constitute a function based Application Program Interface (API) for gas turbine engine customer programs. The functions specified in this API are delivered by the Supplier as part of the Engine model. This document defines generic language independent functions and specific appendices for implementations in C and Fortran. The function based API specified in this ARP represents an alternative to the Fortran COMMON block structure, as specified in AS4191, historically used to communicate with an engine program. The customer may request emulation of the AS4191 interface if desired.
Standard

Application Programming Interface Requirements for the Presentation of Gas Turbine Engine Performance on Digital Computers
2001-10-01
HISTORICAL
ARP4868
This SAE Aerospace Recommended Practice (ARP) specifies a set of functions and their expected behavior that constitute an Application Programming Interface (API) for gas turbine engine customer programs. The main body of this document contains a description of each of the API function calls and of the data that passes through these functions. Implementations of this API in specific programming languages are contained in separate appendices. These appendices include language specific details and the definitions for each function as required for the given language. AS681 is the parent document of ARP4868. All of AS681 applies to customer engine programs written to conform to this document.
Standard

Gas Turbine Engine Performance Presentation and Nomenclature for Object-Oriented Computer Programs
2023-01-03
WIP
ARP5571D
This document provides recommendations for several aspects of air-breathing gas turbine engine performance modeling using object-oriented programming systems. Nomenclature, application program interface, and user interface are addressed with the emphasis on nomenclature. The Numerical Propulsion System Simulation (NPSS) modeling environment is frequently used in this document as an archetype. Many of the recommendations for standards are derived from NPSS standards. NPSS was chosen because it is an available product. The practices recommended herein may be applied to other object-oriented systems. While this document applies broadly to any gas turbine engine, the great majority of engine performance computer programs have historically been written for aircraft propulsion systems. Aircraft and propulsion terminology and examples appear throughout.
Standard

Gas Turbine Engine Performance Presentation and Nomenclature For Object-Oriented Computer Programs
2013-10-04
HISTORICAL
ARP5571B
This document provides recommendations for several aspects of air-breathing gas turbine engine performance modeling using object-oriented programming systems. Nomenclature, application program interface, and user interface are addressed with the emphasis on nomenclature. The Numerical Propulsion System Simulation (NPSS) modeling environment is frequently used in this document as an archetype. Many of the recommendations for standards are derived from NPSS standards. NPSS was chosen because it is an available product. The practices recommended herein may be applied to other object-oriented systems. While this document applies broadly to any gas turbine engine, the great majority of engine performance computer programs have historically been written for aircraft propulsion systems. Aircraft and propulsion terminology and examples appear throughout.
Standard

Gas Turbine Engine Performance Presentation and Nomenclature For Object-Oriented Computer Programs
2018-05-07
CURRENT
ARP5571C
This document provides recommendations for several aspects of air-breathing gas turbine engine performance modeling using object-oriented programming systems. Nomenclature, application program interface, and user interface are addressed with the emphasis on nomenclature. The Numerical Propulsion System Simulation (NPSS) modeling environment is frequently used in this document as an archetype. Many of the recommendations for standards are derived from NPSS standards. NPSS was chosen because it is an available product. The practices recommended herein may be applied to other object-oriented systems. While this document applies broadly to any gas turbine engine, the great majority of engine performance computer programs have historically been written for aircraft propulsion systems. Aircraft and propulsion terminology and examples appear throughout.
Standard

Gas Turbine Engine Performance Presentation and Nomenclature for Digital Computers Using Object-Oriented Programming
2005-01-11
HISTORICAL
ARP5571
This document provides recommendations for several aspects of air-breathing gas turbine engine performance modeling using object-oriented programming systems. Nomenclature, application program interface, and user interface are addressed with the emphasis on nomenclature. The Numerical Propulsion System Simulation (NPSS) modeling environment is frequently used in this document as an archetype. Many of the recommendations for standards are derived from NPSS standards. NPSS was chosen because it is an available, production system. The practices recommended herein may be applied to other object-oriented systems. While this document applies broadly to any gas turbine engine, the great majority of engine performance computer programs have historically been written for aircraft propulsion systems. Aircraft and propulsion terminology and examples appear throughout.
Standard

Gas Turbine Engine Performance Presentation and Nomenclature For Object-Oriented Computer Programs
2008-12-17
HISTORICAL
ARP5571A
This document provides recommendations for several aspects of air-breathing gas turbine engine performance modeling using object-oriented programming systems. Nomenclature, application program interface, and user interface are addressed with the emphasis on nomenclature. The Numerical Propulsion System Simulation (NPSS) modeling environment is frequently used in this document as an archetype. Many of the recommendations for standards are derived from NPSS standards. NPSS was chosen because it is an available product. The practices recommended herein may be applied to other object-oriented systems. While this document applies broadly to any gas turbine engine, the great majority of engine performance computer programs have historically been written for aircraft propulsion systems. Aircraft and propulsion terminology and examples appear throughout.
Standard

EMBEDDED INTERCHANGE FORMAT FOR AIRPORT MAPPING DATABASE
2016-08-31
CURRENT
ARINC816-3
This document defines an open encoding format for airport databases which are loaded in airborne systems. This format, when designed and implemented, will enable a quick, economic, and efficient use of AMDB. However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.
Standard

Control of Aviation Critical Safety Items
2017-03-17
CURRENT
AS9017
This document is intended to prescribe consistent requirements for CSI management for organizations and suppliers who perform work for prime contractors receiving direct contracts from U.S. government agencies (i.e., first-tier or prime suppliers).
Standard

Hand Winches—Boat Trailer Type
2008-10-03
HISTORICAL
J1853_200810
This SAE Standard includes spur gear and direct drive type hand-cranked winches as used on boat trailers. This does not include brake type winches as used in boat lift, davit, or industrial applications.
Standard

Hand Winches—Boat Trailer Type
2014-06-02
CURRENT
J1853_201406
This SAE Standard includes spur gear and direct drive type hand-cranked winches as used on boat trailers. This does not include brake type winches as used in boat lift, davit, or industrial applications.
Standard

HAND WINCHES - BOAT TRAILER TYPE
1987-04-01
HISTORICAL
J1853_198704
This standard includes spur gear and direct drive type hand cranked winches as used on boat trailers. This does not include brake type winches as used in boat lift, davit, or industrial applications.
Standard

Hand Winches—Boat Trailer Type
2000-06-28
HISTORICAL
J1853_200006
This SAE Standard includes spur gear and direct drive type hand-cranked winches as used on boat trailers. This does not include brake type winches as used in boat lift, davit, or industrial applications.
Collection

SAE EDGE™ Research Reports - Infrastructure Enablers
2023-06-28
The deployment of automated vehicles (AVs)—especially driverless cars—has fallen significantly short of expectations. Some specific use cases possess momentum; however, production numbers generally appear to be more hopeful than realistic. Even before the COVID-19 pandemic, automated freight applications gained greater traction. For the most part, currently deployed freight-focused AVs are limited to narrowly defined operational design domains (ODDs) and may require human intervention to exit a highway or interact with law enforcement officers and weigh stations. Remaining business cases are often built around the so-called structural AVs—or AVs that operate in relatively constrained environments. In these scenarios, a narrow use case may support an investor’s requirements; however, this is not the case for infrastructure owners and operators (IOOs).
<< First< Previous62596260626162626263Next >Last >>
X