Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Performance Analysis”

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 397 records · Page 22
All sourcesNASA NTRSDOE OSTI
NASA NTRS1971

Solid Rocket Motor Performance Analysis and Prediction

Current design practices are reviewed and assessed, and guidance is established for achieving greater consistency in design, reliability in the end product, and efficiency in the design effort. The total problem is discussed, and design elements involved in successful design are identified. Design criteria are described, and the rule, guide, limitation, or standard which must be imposed on each essential design element is given. Recommended practices are presented for satisfying each of the criteria.

Source record↗
NASA NTRS1972

Performance Analysis and Design Synthesis (PADS) computer program. Volume 1: Formulation

The program formulation for PADS computer program is presented. It can size launch vehicles in conjunction with calculus-of-variations optimal trajectories and can also be used as a general-purpose branched trajectory optimization program. In the former use, it has the Space Shuttle Synthesis Program as well as a simplified stage weight module for optimally sizing manned recoverable launch vehicles. For trajectory optimization alone or with sizing, PADS has two trajectory modules. The first trajectory module uses the method of steepest descent; the second employs the method of quasilinearization, which requires a starting solution from the first trajectory module.

Source record↗
NASA NTRS1973

Thermoelectric pump performance analysis computer code

A computer program is presented that was used to analyze and design dual-throat electromagnetic dc conduction pumps for the 5-kwe ZrH reactor thermoelectric system. In addition to a listing of the code and corresponding identification of symbols, the bases for this analytical model are provided.

Johnson, J. L.↗
NASA NTRS1972

Apollo 15 mission report: Apollo 15 guidance, navigation, and control system performance analysis report (supplement 1)

This report contains the results of additional studies which were conducted to confirm the conclusions of the MSC Mission Report and contains analyses which were not completed in time to meet the mission report deadline. The LM IMU data were examined during the lunar descent and ascent phases. Most of the PGNCS descent absolute velocity error was caused by platform misalignments. PGNCS radial velocity divergence from AGS during the early part of descent was partially caused by PGNCS gravity computation differences from AGS. The remainder of the differences between PGNCS and AGS velocity were easily attributable to attitude reference alignment differences and tolerable instrument errors. For ascent the PGNCS radial velocity error at insertion was examined. The total error of 10.8 ft/sec was well within mission constraints but larger than expected. Of the total error, 2.30 ft/sec was PIPA bias error, which was suspected to exist pre-lunar liftoff. The remaining 8.5 ft/sec is most probably satisified with a large pre-liftoff planform misalignment.

Source record↗
NASA NTRS1972

Design and performance analysis of solid-propellant rocket motors using a simplified computer program

An analysis and a computer program are presented which represent a compromise between the more sophisticated programs using precise burning geometric relations and the textbook type of solutions. The program requires approximately 900 computer cards including a set of 20 input data cards required for a typical problem. The computer operating time for a single configuration is approximately 1 minute and 30 seconds on the IBM 360 computer. About l minute and l5 seconds of the time is compilation time so that additional configurations input at the same time require approximately 15 seconds each. The program uses approximately 11,000 words on the IBM 360. The program is written in FORTRAN 4 and is readily adaptable for use on a number of different computers: IBM 7044, IBM 7094, and Univac 1108.

Sforzini, R. H.↗