Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Verification of data”

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 109 records · Page 6

GFO-1 Geophysical Data Record and Orbit Verifications for Global Change Studies

This final report summarizes the research work conducted under NASA's Physical Oceanography Program, entitled, GFO-1 Geophysical Data Record And Orbit Verifications For Global Change Studies, for the investigation time period from December 1, 1997 through November 30, 2000. The primary objectives of the investigation include providing verification and improvement for the precise orbit, media, geophysical, and instrument corrections to accurately reduce U.S. Navy's Geosat-Followon-1 (GFO-1) mission radar altimeter data to sea level measurements. The status of the GFO satellite (instrument and spacecraft operations, orbital tracking and altimeter) is summarized. GFO spacecraft has been accepted by the Navy from Ball Aerospace and has been declared operational since November, 2000. We have participated in four official GFO calibration/validation periods (Cal/Val I-IV), spanning from June 1999 through October 2000. Results of verification of the GFO orbit and geophysical data record measurements both from NOAA (IGDR) and from the Navy (NGDR) are reported. Our preliminary results indicate that: (1) the precise orbit (GSFC and OSU) can be determined to approx. 5 - 6 cm rms radially using SLR and altimeter crossovers; (2) estimated GFO MOE (GSFC or NRL) radial orbit accuracy is approx. 7 - 30 cm and Operational Doppler orbit accuracy is approx. 60 - 350 cm. After bias and tilt adjustment (1000 km arc), estimated Doppler orbit accuracy is approx. 1.2 - 6.5 cm rms and the MOE accuracy is approx. 1.0 - 2.3 cm; (3) the geophysical and media corrections have been validated versus in situ measurements and measurements from other operating altimeters (T/P and ERS-2). Altimeter time bias is insignificant with 0-2 ms. Sea state bias is about approx. 3 - 4.5% of SWH. Wet troposphere correction has approx. 1 cm bias and approx. 3 cm rms when compared with ERS-2 data. Use of GIM and IRI95 provide ionosphere correction accurate to 2-3 cm rms during medium to high solar activities; (4) the noise of the GFO altimeter data (uncorrected SSH) is about 15 mm, compared to 19 min for ERS-2, and 12 min for TOPEX. It is anticipated that the operational GFO-1 altimeter data will contribute to a number of researches in physical oceanography. A list of relevant presentations and publications is attached.

Shum, C. K.↗

Design and Development of a Model to Simulate 0-G Treadmill Running Using the European Space Agency's Subject Loading System

Develop a model that simulates a human running in 0 G using the European Space Agency s (ESA) Subject Loading System (SLS). The model provides ground reaction forces (GRF) based on speed and pull-down forces (PDF). DESIGN The theoretical basis for the Running Model was based on a simple spring-mass model. The dynamic properties of the spring-mass model express theoretical vertical GRF (GRFv) and shear GRF in the posterior-anterior direction (GRFsh) during running gait. ADAMs VIEW software was used to build the model, which has a pelvis, thigh segment, shank segment, and a spring foot (see Figure 1).the model s movement simulates the joint kinematics of a human running at Earth gravity with the aim of generating GRF data. DEVELOPMENT & VERIFICATION ESA provided parabolic flight data of subjects running while using the SLS, for further characterization of the model s GRF. Peak GRF data were fit to a linear regression line dependent on PDF and speed. Interpolation and extrapolation of the regression equation provided a theoretical data matrix, which is used to drive the model s motion equations. Verification of the model was conducted by running the model at 4 different speeds, with each speed accounting for 3 different PDF. The model s GRF data fell within a 1-standard-deviation boundary derived from the empirical ESA data. CONCLUSION The Running Model aids in conducting various simulations (potential scenarios include a fatigued runner or a powerful runner generating high loads at a fast cadence) to determine limitations for the T2 vibration isolation system (VIS) aboard the International Space Station. This model can predict how running with the ESA SLS affects the T2 VIS and may be used for other exercise analyses in the future.

Caldwell, E. C.↗

Matrix Theory for Data Association in PVS

Consider a collection of data generated by sensors from a set of aircraft. Data association is the process of connecting each sensor measurement with its corresponding aircraft. Furthermore once the data association has taken place, the state of the aircraft can be approximated using a Kalman filter. This talk aims to explore formal specification and verification of data association in the Prototype Verification System (PVS). Formal specification and verification of data association includes development of Kalman filters, Mahalanobis distance, and other topics of matrix analysis in PVS.

Linear Algebra↗

Study of plate-fin heat exchanger and cold plate for the active thermal control system of Space Station

Plate-fin heat exchangers will be employed in the Active Thermal Control System of Space Station Freedom. During ground testing of prototypic heat exchangers, certain anomalous behaviors have been observed. Diagnosis has been conducted to determine the cause of the observed behaviors, including a scrutiny of temperature, pressure, and flow rate test data, and verification calculations based on such data and more data collected during the ambient and thermal/vacuum tests participated by the author. The test data of a plate-fin cold plate have been also analyzed. Recommendation was made with regard to further tests providing more useful information of the cold plate performance.

Chyu, MING-C.↗

Develop a Model Component

During my internship at NASA, I was a model developer for Ground Support Equipment (GSE). The purpose of a model developer is to develop and unit test model component libraries (fluid, electrical, gas, etc.). The models are designed to simulate software for GSE (Ground Special Power, Crew Access Arm, Cryo, Fire and Leak Detection System, Environmental Control System (ECS), etc. ~.) before they are implemented into hardware. These models support verifying local control and remote software for End-Item Software Under Test (SUT). The model simulates the physical behavior (function, state, limits and 110) of each end-item and it's dependencies as defined in the Subsystem Interface Table, Software Requirements & Design Specification (SRDS), Ground Integrated Schematic (GIS), and System Mechanical Schematic.(SMS). The software of each specific model component is simulated through MATLAB's Simulink program. The intensiv~ model development life cycle is a.s follows: Identify source documents; identify model scope; update schedule; preliminary design review; develop model requirements; update model.. scope; update schedule; detailed design review; create/modify library component; implement library components reference; implement subsystem components; develop a test script; run the test script; develop users guide; send model out for peer review; the model is sent out for verific~tionlvalidation; if there is empirical data, a validation data package is generated; if there is not empirical data, a verification package is generated; the test results are then reviewed; and finally, the user. requests accreditation, and a statement of accreditation is prepared. Once each component model is reviewed and approved, they are intertwined together into one integrated model. This integrated model is then tested itself, through a test script and autotest, so that it can be concluded that all models work conjointly, for a single purpose. The component I was assigned, specifically, was a fluid component, a discrete pressure switch. The switch takes a fluid pressure input, and if the pressure is greater than a designated cutoff pressure, the switch would stop fluid flow.

Ensey, Tyler S.↗

Verification and analysis of TOVS satellite data

A study which involves the verification of TOVS (TIROS Operational Vertical Soundings) stratospheric temperature information and derived geopotential heights, as well as the higher order derivations of wind, heat flux, and momentum flux, is discussed. Rocketsondes were launched daily at the times of NOAA-7 overpasses of Wallops Island during February 23-March 24, 1982, and resources made available by NASA were used to provide in-situ field measurements and additional analysis. The TOVS satellite products from hemispheric analyses are compared with unsmoothed rocketsonde data. Some of the benefits provided by the comparisons are considered.

Gelman, M. E.↗

Use of an Existing Airborne Radon Data Base in the Verification of the NASA/AEAP Core Model

The primary objective of this project was to apply the tropospheric atmospheric radon (Rn222) measurements to the development and verification of the global 3-D atmospheric chemical transport model under development by NASA's Atmospheric Effects of Aviation Project (AEAP). The AEAP project had two principal components: (1) a modeling effort, whose goal was to create, test and apply an elaborate three-dimensional atmospheric chemical transport model (the NASA/AEAP Core model to an evaluation of the possible short and long-term effects of aircraft emissions on atmospheric chemistry and climate--and (2) a measurement effort, whose goal was to obtain a focused set of atmospheric measurements that would provide some of the observational data used in the modeling effort. My activity in this project was confined to the first of these components. Both atmospheric transport and atmospheric chemical reactions (as well the input and removal of chemical species) are accounted for in the NASA/AEAP Core model. Thus, for example, in assessing the effect of aircraft effluents on the chemistry of a given region of the upper troposphere, the model must keep track not only of the chemical reactions of the effluent species emitted by aircraft flying in this region, but also of the transport into the region of these (and other) species from other, remote sources--for example, via the vertical convection of boundary layer air to the upper troposphere. Radon, because of its known surface source and known radioactive half-life, and freedom from chemical production or loss, and from removal from the atmosphere by physical scavenging, is a recognized and valuable tool for testing the transport components of global transport and circulation models.

Kritz, Mark A.↗

Remote Sensing Product Verification and Validation at the NASA Stennis Space Center

Remote sensing data product verification and validation (V&V) is critical to successful science research and applications development. People who use remote sensing products to make policy, economic, or scientific decisions require confidence in and an understanding of the products' characteristics to make informed decisions about the products' use. NASA data products of coarse to moderate spatial resolution are validated by NASA science teams. NASA's Stennis Space Center (SSC) serves as the science validation team lead for validating commercial data products of moderate to high spatial resolution. At SSC, the Applications Research Toolbox simulates sensors and targets, and the Instrument Validation Laboratory validates critical sensors. The SSC V&V Site consists of radiometric tarps, a network of ground control points, a water surface temperature sensor, an atmospheric measurement system, painted concrete radial target and edge targets, and other instrumentation. NASA's Applied Sciences Directorate participates in the Joint Agency Commercial Imagery Evaluation (JACIE) team formed by NASA, the U.S. Geological Survey, and the National Geospatial-Intelligence Agency to characterize commercial systems and imagery.

Stanley, Thomas M.↗

Geos 3 wave height measurements - An assessment during high sea state conditions in the North Atlantic

The sea state in the North Atlantic Ocean has been monitored in February, 1977 to obtain data for verification of Geos 3 radio altimeter wave form data. The altimeter sea state data were found to be in good agreement with in situ sea state measurements and with aircraft remote sensing measurements of wave height. The average difference between the supporting data and Geos 3 was 0.34 m, and the standard deviation 0.61 m. Contour maps of sea state constructed for large regions of the earth's oceans on the basis of Geos 3 altimeter measurements exhibited systematic differences from operationally available computerized maps. It is thought that the underestimation of significant wave height maxima in the operational maps and the underestimation of the speed of movement of oceanic cyclones may be due to basic errors in the output of atmospheric primitive-equation models. Because of the narrow swath width of the Geos-3 sensor, data from several satellite orbits must be combined to construct contour maps, leading to low values of significant wave heights.

Parsons, C. L.↗

Transonic wind tunnel tests of A.015 scale space shuttle orbiter model, volume 1

Transonic wind tunnel tests were run on a 0.015 scale model of the Space Shuttle Orbiter Vehicle in an eight-foot tunnel during August 1975. The purpose of the program was to obtain basic shuttle aerodynamic data through a full range of elevon and aileron deflections, verification of data obtained at other facilities, and effects of Reynolds numbers. The first part of a discussion of test procedures and results in both tabular and graphical form were presented. Tests were performed at Mach numbers from 0.35 to 1.20, and at Reynolds numbers for 3.5 million to 8.2 million per foot. The angle of attack was varied from -1 to +20 degrees at sideslip angles of -2, 0, +2 degrees. Sideslip was varied from -6 to +8 degrees at constant angles of attack from 0 to +20 degrees. Various aileron and ailevon settings were tested for various angles of attack.

Struzynski, N. A.↗

Transonic wind tunnel tests of a .015 scale space shuttle orbiter model, volume 2

Transonic wind tunnel tests were run on a 0.015 scale model of the Space Shuttle Orbiter Vehicle in an eight-foot tunnel during August 1975. The purpose of the program was to obtain basic shuttle aerodynamic data through a full range of elevon and aileron deflections, verification of data obtained at other facilities, and effects of Reynolds numbers. The second part of a discussion of test procedures and results in both tabular and graphical form were presented. Tests were performed at Mach numbers from 0.35 to 1.20, and at Reynolds numbers from 3.5 million to 8.2 million per foot. The angle of attack was varied from -2 to +20 degrees at sideslip angles of -2, 0, +2 degrees. Sideslip was varied from -6 to +8 degrees at constant angles of attack from 0 to +20 degrees. Various aileron and ailevon settings were tested for various angles of attack.

Struzynski, N. A.↗

Transonic high Reynolds number stability and control characteristics of a 0.015-scale remotely controlled elevon model (44-0) of the space shuttle orbiter tested in calspan 8-foot TWT (LA70)

Transonic Wind Tunnel tests were run on a .015 scale model of the space shuttle orbiter vehicle in the 8-foot transonic wind tunnel. Purpose of the test program was to obtain basic shuttle aerodynamic data through a full range of elevon and aileron deflections, verification of data obtained at other facilities, and effects of Reynolds number. Tests were performed at Mach numbers from .35 to 1.20 and Reynolds numbers from 3,500,000 to 8,200,000 per foot. The high Reynolds number conditions (nominal 8,000,000/foot) were obtained using the ejector augmentation system. Angle of attack was varied from -2 to +20 degrees at sideslip angles of -2, 0, and +2 degrees. Sideslip was varied from -6 to +8 degrees at constant angles of attack from 0 to +20 degrees. Aileron settings were varied from -5 to +10 degrees at elevon deflections of -10, 0, and +10 degrees. Fixed aileron settings of 0 and 2 degrees in combination with various fixed elevon settings between -20 and +5 degrees were also run at varying angles of attack.

Parrell, H.↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

Geometric verification

Present LANDSAT data formats are reviewed to clarify how the geodetic location and registration capabilities were defined for P-tape products and RBV data. Since there is only one geometric model used in the master data processor, geometric location accuracy of P-tape products depends on the absolute accuracy of the model and registration accuracy is determined by the stability of the model. Due primarily to inaccuracies in data provided by the LANDSAT attitude management system, desired accuracies are obtained only by using ground control points and a correlation process. The verification of system performance with regards to geodetic location requires the capability to determine pixel positions of map points in a P-tape array. Verification of registration performance requires the capability to determine pixel positions of common points (not necessarily map points) in 2 or more P-tape arrays for a given world reference system scene. Techniques for registration verification can be more varied and automated since map data are not required. The verification of LACIE extractions is used as an example.

Grebowsky, G. J.↗

Flexible rotor dynamics analysis

A digital computer program was developed to analyze the general nonaxisymmetric and nonsynchronous transient and steady-state rotor dynamic performance of a bending- and shear-wise flexible rotor-bearing system under various operating conditions. The effects of rotor material mechanical hysteresis, rotor torsion flexibility, transverse effects of rotor axial and torsional loading and the anisotropic, in-phase and out-of-phase bearing stiffness and damping force and moment coefficients were included in the program to broaden its capability. An optimum solution method was found and incorporated in the computer program. Computer simulation of experimental data was made and qualitative agreements observed. The mathematical formulations, computer program verification, test data simulation, and user instruction was presented and discussed.

Shen, F. A.↗

Shuttle Laser Altimeter (SLA): A pathfinder for space-based laser altimetry and lidar

The Shuttle Laser Altimeter (SLA) is a Hitchhiker experiment now being integrated for first flight on STS-72 in November 1995. Four Shuttle flights of the SLA are planned at a rate of about a flight every 18 months. They are aimed at the transition of the Goddard Space Flight Center airborne laser altimeter and lidar technology to low Earth orbit as a pathfinder for operational space-based laser remote sensing devices. Future alser altimeter sensors such as the Geoscience Laser Altimeter System (GLAS), an Earth Observing System facility instrument, and the Multi-Beam Laser Altimeter (MBLA), the land and vegetation laser altimeter for the NASA TOPSAT (Topography Satellite) Mission, will utilize systems and approaches being tested with SLA. The SLA Instrument measures the distance from the Space Shuttle to the Earth's surface by timing the two-way propagation of short (approximately 10 na noseconds) laser pulses. laser pulses at 1064 nm wavelength are generated in a laser transmitter and are detected by a telescope equipped with a silicon avalanche photodiode detector. The SLA data system makes the pulse time interval measurement to a precision of about 10 nsec and also records the temporal shape of the laser echo from the Earth's surface for interpretation of surface height distribution within the 100 m diam. sensor footprint. For example, tree height can be determined by measuring the characteristic double-pulse signature that results from a separation in time of laser backscatter from tree canopies and the underlying ground. This is accomplished with a pulse waveform digitizer that samples the detector output with an adjustable resolution of 2 nanoseconds or wider intervals in a 100 sample window centered on the return pulse echo. The digitizer makes the SLA into a high resolution surface lidar sensor. It can also be used for cloud and atmospheric aerosol lidar measurements by lengthening the sampling window and degrading the waveform resolution. Detailed test objectives for the STS-72 mission center on the acquisition of sample data sets for land topography and vegetation height, waveform digitizer performance, and verification of data acquisition algorithms. The operational concept of SLA is illustrated in Fig. 1 where a series of 100 m footprints stretch in a profile of Earth surface topography along the nadir track of the Space Shuttle. The location of SLA as a dual canister payload on the Hitchhiker Bridge Assembly in Bay 12 of the Space Shuttle Endeavor can also be noted in this figure. Full interpretation of the SLA range measurement data set requires a 1 m knowledge of the Orbiter trajectory and better than 0.1 deg knowledge of Orbiter pointing angle. These ancillary data sets will be acquired during the STS-72 mission with an on-board Global Positioning System (GPS) receiver, K-band range and range-rate tracking of the Orbiter through TDRSS, and use of on-board inertial measurement units and star trackers. Integration and interpretation of all these different data sets as a pathfinder investigation for accurate determination of Earth surface elevation is the overall science of the SLA investigation.

Bufton, Jack↗