Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “analysis software”

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 199 records · Page 11

Radar Analysis and Visualization Environment (RAVEN): Software for polarimetric radar analysis

Imaging radar data provides information about the geometric and dielectric properties of the Earth's surface. The Jet Propulsion Laboratory (JPL) polarimetric Airborne Synthetic Aperture Radar (AIRSAR) is currently obtaining imaging radar data for use in geologic, vegetation, snow and ice, and ocean studies. In the near future, the Shuttle Imaging Radar C (SIR-C/X-SAR) and the Earth Observing System Synthetic Aperture Radar (EOS SAR) will also collect polarimetric radar data. A need exists for a user-friendly, interactive software package for analysis of these polarimetric radar data sets. Previous software packages, such as JPL's Multiview, while providing some analysis capabilities for these data, did not allow interactive viewing and were tied to specific image display hardware with operating system dependencies. A prototype software system, the 'Radar Analysis and Visualization Environment' (RAVEN) under development at the Center for the Study of Earth from Space (CSES) at the University of Colorado, is designed to deal with data from the JPL AIRSAR instrument and other proposed polarimetric radar instruments. RAVEN is being developed using the Interactive Data Language (IDL). It takes advantage of high speed disk access and fast processors running under the UNIX operating system in an X-windows environment to allow for rapid, interactive visualization of AIRSAR data in both image and graphical ways. It provides a user-friendly interface through the use of menus, sliders, buttons, and display windows.

Kierein-Young, K. S.↗

Uncertainty Analysis and Software Verification

Uncertainty analyses are an important part of calibrations and testing. They allow researchers insight on how to reduce and mitigate errors in testing. Each device used in testing introduces error in a system, as well as other sources such as environmental conditions, electronics, analog to digital, and random errors. Each source is carefully examined to identify how much error it introduces to a system. These sources are then combined using various methods of uncertainty calculations. To verify and validate software, a manual calculation is required to ensure the software is performing as intended. Using Excel to verify the calculations, we can identify discrepancies within the software. The root of the sum of the squares uncertainty (RSS) is used to find the combined uncertainty of a device at one and two standard deviations of the mean. Calibrations on accelerometers are performed using a vibration system along with a back-toback reference accelerometer. The vibration system takes a reference point at 100Hz frequency at 10g amplitude. The sensitivities are collected at each dialed in frequency. The sensitivity of the device represents the electrical output of the UUT (mV, pC, etc.) per unit of acceleration (g). The full history of sensitivities of selected accelerometers are used to find the averaged, standard deviation, and uncertainty of the device at each frequency tested. The uncertainty calculations from excel and the software are then compared.

97 MATHEMATICS AND COMPUTING↗

Maximization of orbiter altitude at ALT interface airspeed, mission planning, mission analysis and software

The determination of the separation initial conditions (i.e. incidence angle) that maximize orbiter altitude at the ALT interface airspeed is considered. Optimum altitude airspeed profiles are generated for each orbiter incidence angle and tailcone configuration. Results show that the highest separation altitude does not result in the highest altitude at ALT interface airspeed. The altitude attainable at ALT interface airspeed should therefore be considered in the selection of the initial conditions (i.e. incidence angle). Without violating any known constraints, the incidence angles that maximize orbiter altitude at the ALT interface airspeeds are 7.0 deg for ALT free flight 1 and 5.5 deg for ALT free flight 6.

Glenn, G. M.↗

Proposed powered explicit guidance thrust integrals derivation/implementation. Mission planning, mission analysis and software formulation

A new exoatmospheric, powered explicit guidance (PEG) thrust integral formulation and a simple method of implementation are presented. The new thrust integral formulation is significantly simpler than that currently used in PEG. Preliminary estimates indicate a computer storage savings of 220 words, which is approximately 10 percent of the current PEG ascent program. Alternate methods of implementation that could produce even more savings are noted.

Jaggers, R. F.↗

Star tracker constraint violations digital capability description and analysis results. Mission planning, mission analysis, and software formulation

Results of star tracker constraint violation analyses performed with the digital computer program Shuttle Attitude and Pointing Time Line Processor (SAPT) are presented. Results are typical of those utilized to provide the information required to update Baseline Reference Mission Attitude and Pointing Time Lines. Descriptions of SAPT modifications implemented to perform these analyses are also presented.

Poston, P. L.↗

Mission planning, mission analysis and software formulation. Level C requirements for the shuttle mission control center orbital guidance software

The formulation of Level C requirements for guidance software was reported. Requirements for a PEG supervisor which controls all input/output interfaces with other processors and determines which PEG mode is to be utilized were studied in detail. A description of the two guidance modes for which Level C requirements have been formulated was presented. Functions required for proper execution of the guidance software were defined. The requirements for a navigation function that is used in the prediction logic of PEG mode 4 were discussed. It is concluded that this function is extracted from the current navigation FSSR.

Langston, L. J.↗

Error Analysis of the Shuttle Orbital Maneuvering System P-V-T Propellant Gaging Module. Mission Planning, Mission Analysis and Software Formulation

An investigation of the shuttle orbital maneuvering system (OMS) pressure-volume-temperature (P-V-T) propellant gaging module has revealed that the gaging errors due to the combined effects of random instrumentation measurement errors, propellant loading uncertainties, and simplifying assumptions in the software are non-linear over the range of the usable propellant quantity gage (0-100%), with the largest error being at the zero point. When the OMS propellant tanks in the orbiter vehicle pods are filled to contain 100% of the maximum usable propellant, the gaging error at the zero point was determined to be 9.5% for the fuel and 9.5% for the oxidizer. When the OMS propellant tanks initially contain 50% of the maximum usable propellant, the largest gaging error is still 9.5% for the fuel and 9.5% for the oxidizer.

Duhon, D. D.↗

Smoothing of orbital tracking data: Mission planning, mission analysis and software formulation

The problem created by the presence of wild or outlying data points among orbital tracking data, is addressed. Consideration is given to the effects of such outliers on the orbit determination process, and methods for minimizing or even eliminating these effects are proposed. Some preliminary efforts implementing these new methods are described, and the results thus far obtained are summarized. Based on these ideas and results, recommendations are made for future investigation.

Vedder, J. D.↗

Abort Region Determinator (ARD) module feasibility report. Mission planning, mission analysis and software formulation

A detailed performance evaluation of the Abort Region Determinator (ARD) module design was provided in support of OFT-1 ascent and OFT-1 intact launch aborts. The evaluation method used compared ARD results against results obtained using the full-up Space Vehicle Dynamic Simulations program under the same conditions. Results were presented for each of the three major ARD math models: (1) the ascent numerical integrator; (2) the mass model, and (3) the second stage predictor as well as the total ARD module. These results demonstrate that the baselined ARD module meets all design objectives for mission control center orbital flight test launch/abort support.

Draeger, B. G.↗

Remote manipulator system flexibility analysis program: Mission planning, mission analysis, and software formulation

A computer program is described for calculating the flexibility coefficients as arm design changes are made for the remote manipulator system. The coefficients obtained are required as input for a second program which reduces the number of payload deployment and retrieval system simulation runs required to simulate the various remote manipulator system maneuvers. The second program calculates end effector flexibility and joint flexibility terms for the torque model of each joint for any arbitrary configurations. The listing of both programs is included in the appendix.

Kumar, L.↗

Modifications to give HOPE/MDC 2.0 the capability to solve for or consider vent forces: Mission planning, mission analysis, and software formulation

The modifications are described as necessary to give the Houston Operations Predictor/Estimator (HOPE) program the capability to solve for or consider vent forces for orbit determination. The model implemented in solving for vent forces is described along with the integrator problems encountered. A summary derivation of the mathematical principles applicable to solve/consider methodology is provided.

Zyla, L. V.↗

Detection of faults and software reliability analysis

Specific topics briefly addressed include: the consistent comparison problem in N-version system; analytic models of comparison testing; fault tolerance through data diversity; and the relationship between failures caused by automatically seeded faults.

Knight, J. C.↗