Results for “base station cooperation” — Page 6

NASA NTRS1993

The GPS Topex/Poseidon precise orbit determination experiment - Implications for design of GPS global networks

Topex/Poseidon, a cooperative satellite mission between United States and France, aims to determine global ocean circulation patterns and to study their influence on world climate through precise measurements of sea surface height above the geoid with an on-board altimeter. To achieve the mission science aims, a goal of 13-cm orbit altitude accuracy was set. Topex/Poseidon includes a Global Positioning System (GPS) precise orbit determination (POD) system that has now demonstrated altitude accuracy better than 5 cm. The GPS POD system includes an on-board GPS receiver and a 6-station GPS global tracking network. This paper reviews early GPS results and discusses multi-mission capabilities available from a future enhanced global GPS network, which would provide ground-based geodetic and atmospheric calibrations needed for NASA deep space missions while also supplying tracking data for future low Earth orbiters. Benefits of the enhanced global GPS network include lower operations costs for deep space tracking and many scientific and societal benefits from the low Earth orbiter missions, including improved understanding of ocean circulation, ocean-weather interactions, the El Nino effect, the Earth thermal balance, and weather forecasting.

Lindqwister, Ulf J.↗

NASA NTRS1986

Using Ada to implement the operations management system in a community of experts

An architecture is described for the Space Station Operations Management System (OMS), consisting of a distributed expert system framework implemented in Ada. The motivation for such a scheme is based on the desire to integrate the very diverse elements of the OMS while taking maximum advantage of knowledge based systems technology. Part of the foundation of an Ada based distributed expert system was accomplished in the form of a proof of concept prototype for the KNOMES project (Knowledge-based Maintenance Expert System). This prototype successfully used concurrently active experts to accomplish monitoring and diagnosis for the Remote Manipulator System. The basic concept of this software architecture is named ACTORS for Ada Cognitive Task ORganization Scheme. It is when one considers the overall problem of integrating all of the OMS elements into a cooperative system that the AI solution stands out. By utilizing a distributed knowledge based system as the framework for OMS, it is possible to integrate those components which need to share information in an intelligent manner.

Frank, M. S.↗

NASA NTRS1997

Microgravity Environment Characterization Program

The Microgravity Science and Applications Division (MSAD), a division within NASA's Office of Life and Microgravity Science and Applications, sponsors a broad range of space-based research in biotechnology, combustion science, fluid physics, fundamental physics, and materials science. To better understand and exploit the orbital environment, MSAD has developed methods and hardware to characterize accelerations on microgravity experiment carriers. MSAD supports research to verify analytically derived acceleration requirements for experiments and provides vibration isolation for sensitive experiments. The Microgravity Measurement and Analysis Project (MMAP), supported by MSAD, incorporates four projects: the Space Acceleration Measurement System (SAMS), the Orbital Acceleration Research Experiment (OARE), the SAMS for International Space Station (SAMS-II), and the Principal Investigator Microgravity Services (PIMS). SAMS was developed to record microgravity accelerations and the OARE was developed to record very low-frequency microgravity accelerations on-board the NASA Orbiters. The SAMS is also used for cooperative investigations on the Russian Mir space station. The SAMS-II is being developed for the same function on-board the International Space Station (ISS). PIMS utilizes microgravity acceleration data to develop a description of each microgravity mission's acceleration environment and to support microgravity investigators in interpreting possible effects of the acceleration environment on their experiments. These elements of the MSAD program will be used to define acceleration requirements for future Orbiter and ISS payloads. This paper describes the MMAP and summarizes the products and services available to principal investigators and other users. This paper also presents some microgravity acceleration characterization results from the last six years of Orbiter microgravity missions.

DeLombard, Richard↗

NASA NTRS1987

Interdisciplinary analysis procedures in the modeling and control of large space-based structures

The paper describes a computer software system called the Integrated Multidisciplinary Analysis Tool, IMAT, that has been developed at NASA Langley Research Center. IMAT provides researchers and analysts with an efficient capability to analyze satellite control systems influenced by structural dynamics. Using a menu-driven interactive executive program, IMAT links a relational database to commercial structural and controls analysis codes. The paper describes the procedures followed to analyze a complex satellite structure and control system. The codes used to accomplish the analysis are described, and an example is provided of an application of IMAT to the analysis of a reference space station subject to a rectangular pulse loading at its docking port.

Cooper, Paul A.↗

NASA NTRSDate not supplied

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 NTRSDate not supplied

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 NTRS1999

An Evolvable Multi-Agent Approach to Space Operations Engineering

A complex system of spacecraft and ground tracking stations, as well as a constellation of satellites or spacecraft, has to be able to reliably withstand sudden environment changes, resource fluctuations, dynamic resource configuration, limited communication bandwidth, etc., while maintaining the consistency of the system as a whole. It is not known in advance when a change in the environment might occur or when a particular exchange will happen. A higher degree of sophistication for the communication mechanisms between different parts of the system is required. The actual behavior has to be determined while the system is performing and the course of action can be decided at the individual level. Under such circumstances, the solution will highly benefit from increased on-board and on the ground adaptability and autonomy. An evolvable architecture based on intelligent agents that communicate and cooperate with each other can offer advantages in this direction. This paper presents an architecture of an evolvable agent-based system (software and software/hardware hybrids) as well as some plans for further implementation.

Mandutianu, Sanda↗

NASA NTRS2002

Lessons Learned In Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The "pieces" are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗

NASA NTRS2002

Lessons Learned in Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The pieces are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗

NASA NTRS1985

The blackboard model - A framework for integrating multiple cooperating expert systems

The use of an artificial intelligence (AI) architecture known as the blackboard model is examined as a framework for designing and building distributed systems requiring the integration of multiple cooperating expert systems (MCXS). Aerospace vehicles provide many examples of potential systems, ranging from commercial and military aircraft to spacecraft such as satellites, the Space Shuttle, and the Space Station. One such system, free-flying, spaceborne telerobots to be used in construction, servicing, inspection, and repair tasks around NASA's Space Station, is examined. The major difficulties found in designing and integrating the individual expert system components necessary to implement such a robot are outlined. The blackboard model, a general expert system architecture which seems to address many of the problems found in designing and building such a system, is discussed. A progress report on a prototype system under development called DBB (Distributed BlackBoard model) is given. The prototype will act as a testbed for investigating the feasibility, utility, and efficiency of MCXS-based designs developed under the blackboard model.

Erickson, W. K.↗

NASA NTRS1993

Lunar laser ranging data processing in a Unix/X windows environment

In cooperation with the NASA Crustal Dynamics Project initiative placing workstation computers at each of its laser ranging stations to handle data filtering and normalpointing, MLRS personnel have developed a new generation of software to provide the same services for the lunar laser ranging data type. The Unix operating system and X windows/Motif provides an environment for both batch and interactive filtering and normalpointing as well as prediction calculations. The goal is to provide a transportable and maintainable data reduction environment. This software and some sample displays are presented. that the lunar (or satellite) datacould be processed on one computer while data was taken on the other. The reduction of the data was totally interactive and in no way automated. In addition, lunar predictions were produced on-site, another first in the effort to down-size historically mainframe-based applications. Extraction of earth rotation parameters was at one time attempted on site in near-realtime. In 1988, the Crustal Dynamics Project SLR Computer Panel mandated the installation of Hewlett-Packard 9000/360 Unix workstations at each NASA-operated laser ranging station to relieve the aging controller computers of much of their data and communications handling responsibility and to provide on-site data filtering and normal pointing for a growing list of artificial satellite targets. This was seen by MLRS staff as an opportunity to provide a better lunar data processing environment as well.

Ricklefs, Randall L.↗

NASA NTRS2004

Tropospheric Airborne Meteorological Data Reporting (TAMDAR) Sensor Development

One of the recommendations of the National Aviation Weather Program Council was to expand and institutionalize the generation, dissemination, and use of automated pilot reports (PIREPS) to the full spectrum of the aviation community, including general aviation. In response to this and other similar recommendations, NASA initiated cooperative research into the development of an electronic pilot reporting capability (Daniels 2002). The ultimate goal is to develop a small low-cost sensor, collect useful meteorological observations below 25,000 ft., downlink the data in near real time, and use the data to improve weather forecasts. Primary users of the data include pilots, who are one targeted audience for the improved weather information that will result from the TAMDAR data. The weather data will be disseminated and used to improve aviation safety by providing pilots with enhanced weather situational awareness. In addition, the data will be used to improve the accuracy and timeliness of weather forecasts. Other users include air traffic controllers, flight service stations, and airline weather centers. Additionally, the meteorological data collected by TAMDAR is expected to have a significant positive impact on forecast accuracy for ground based applications.

Daniels, Taumi S.↗

NASA NTRS1995

Satellite Situation Center data system for magnetospheric science planning

Critical problems in planning coordinated observation campaigns for magnetospheric science include the need to predict time intervals when one or more observing satellites or ground stations will be connected along magnetic field lines to other observation sites, or when such sites will be located within magnetospheric regions of common interest. The Satellite Situation Center (SSC) was created at the National Space Science Data Center (NSSDC) during the International Magnetospheric Study in the 1970s to address these problems. The SSC Data System has evolved since that era to support potentially complex queries by SSC staff and has now been opened to NASA Science Internet access via the NSSDC On-line Data Information System (NODIS). The SSC software, ephemeris data base, and access modes are described for the Version 2.1 release in 1993.

Aist-Sagara, L.↗

NASA NTRS1998

Joint NASA/EPA AVIRIS Analysis in the Chesapeake Bay Region: Plans and Initial Results

NASA's Ames Research Center is performing an AVIRIS demonstration project in conjunction with the U. S. Environmental Protection Agency (Region 3). NASA and EPA scientists have jointly defined a Study Area in eastern Virginia to include portions of the Chesapeake Bay, southern Delmarva Peninsula, and the mouths of the York and James Rivers. Several environmental issues have been identified for study. These include, by priority: 1) water constituent analysis in the Chesapeake Bay, 2) mapping of submerged aquatic vegetation in the Bay, 3) detection of vegetation stress related to Superfund sites at the Yorktown Naval Weapons Station, and 4) wetland species analysis in the York River vicinity. In support of this project, three lines of AVIRIS data were collected during the Wallops Island deployment on 17 August 1997. The remote sensing payload included AVIRIS, MODIS Airborne Simulator and an RC-10 color infrared film camera. The AVIRIS data were delivered to Ames from the JPL AVIRIS Data Facility, on 29 September 1997. Quicklook images indicate nominal data acquisition, and at the current time an atmospheric correction is being applied. Water constituent analysis of the Bay is our highest priority based on EPA interest and available collateral data, both from the surface and from other remote sensing instruments. Constituents of interest include suspended sediments, chlorophyll-a and accessory pigments, Analysis steps will include: verification of data quality, location of study sites in imagery, incorporation of relevant field data from EPA and other Chesapeake Bay cooperators, processing of imagery to show phenomenon of interest, verification of results with cooperators. By 1st quarter CY98 we plan to circulate initial results to NASA and EPA management for review. In the longer term we will finalize documentation, prepare results for publication, and complete any needed technology transfer to EPA remote sensing personnel.

Johnson, Lee↗

NASA NTRS1988

Distributed cooperating processes in a mobile robot control system

A mobile inspection robot has been proposed for the NASA Space Station. It will be a free flying autonomous vehicle that will leave a berthing unit to accomplish a variety of inspection tasks around the Space Station, and then return to its berth to recharge, refuel, and transfer information. The Flying Eye robot will receive voice communication to change its attitude, move at a constant velocity, and move to a predefined location along a self generated path. This mobile robot control system requires integration of traditional command and control techniques with a number of AI technologies. Speech recognition, natural language understanding, task and path planning, sensory abstraction and pattern recognition are all required for successful implementation. The interface between the traditional numeric control techniques and the symbolic processing to the AI technologies must be developed, and a distributed computing approach will be needed to meet the real time computing requirements. To study the integration of the elements of this project, a novel mobile robot control architecture and simulation based on the blackboard architecture was developed. The control system operation and structure is discussed.

Skillman, Thomas L., Jr.↗

NASA NTRS1994

Development of the NASA/FLAGRO computer program for analysis of airframe structures

The NASA/FLAGRO (NASGRO) computer program was developed for fracture control analysis of space hardware and is currently the standard computer code in NASA, the U.S. Air Force, and the European Agency (ESA) for this purpose. The significant attributes of the NASGRO program are the numerous crack case solutions, the large materials file, the improved growth rate equation based on crack closure theory, and the user-friendly promptive input features. In support of the National Aging Aircraft Research Program (NAARP); NASGRO is being further developed to provide advanced state-of-the-art capability for damage tolerance and crack growth analysis of aircraft structural problems, including mechanical systems and engines. The project currently involves a cooperative development effort by NASA, FAA, and ESA. The primary tasks underway are the incorporation of advanced methodology for crack growth rate retardation resulting from spectrum loading and improved analysis for determining crack instability. Also, the current weight function solutions in NASGRO or nonlinear stress gradient problems are being extended to more crack cases, and the 2-d boundary integral routine for stress analysis and stress-intensity factor solutions is being extended to 3-d problems. Lastly, effort is underway to enhance the program to operate on personal computers and work stations in a Windows environment. Because of the increasing and already wide usage of NASGRO, the code offers an excellent mechanism for technology transfer for new fatigue and fracture mechanics capabilities developed within NAARP.

Forman, R. G.↗

NASA NTRS1986

The March 1985 demonstration of the fiducial network concept for GPS geodesy: A preliminary report

The first field tests in preparation for the NASA Global Positioning System (GPS) Caribbean Initiative were conducted in late March and Early April of 1985. The GPS receivers were located at the POLARIS Very Long Base Interferometry (VLBI) stations at Westford, Massachusetts; Richmond, Florida; and Ft. Davis, Texas; and at the Mojave, Owens Valley, and Hat Creek VLBI stations in California. Other mobile receivers were placed near Mammoth Lakes, California; Pt. Mugu, California; Austin, Texas; and Dahlgren, Virginia. These sites were equipped with a combination of GPS receiver types, including SERIES-X, TI-4100 and AFGL dual frequency receivers. The principal objectives of these tests were the demonstration of the fiducial network concept for precise GPS geodesy, the performance assessment of the participating GPS receiver types, and to conduct the first in a series of experiments to monitor ground deformation in the Mammoth Lakes-Long Valley caldera region in California. Other objectives included the testing of the water vapor radiometers for the calibration of GPS data, the development of efficient procedures for planning and coordinating GPS field exercise, the establishment of institutional interfaces for future cooperating ventures, the testing of the GPS Data Analysis Software (GIPSY, for GPS Inferred Positioning SYstem), and the establishment of a set of calibration baselines in California. Preliminary reports of the success of the field tests, including receiver performance and data quality, and on the status of the data analysis software are given.

Davidson, J. M.↗

NASA NTRS1980

Mark 3 correlator hardware and software

The Mark 3 correlator system is described in some detail. The correlator system is based on a modular philosophy. Each correlator module independently processes the data from one track pair. Therefore, 28 modules are necessary to complete a full one baseline processor and 84 modules for a full 3 baseline processor. Each correlator module has two interfaces: (1) data and clock from each of the two tracks to be correlated and (2) Computer Automated Measurement and Control (CAMAC) dataway interface to the computer. The processor is organized around the IEEE CAMAC standard architecture, housing 15 correlator modules in each of 6 crates. This allows one pass processing of a full 3 baseline 28 track observation or a 6 baseline (4 station) 14 track observation. The correlator architecture allows easy expansion for up to 8 stations. The computer system is an HP 1000 system utilizing a 16 bit minicomputer with disc and tape peripherals. The processing software is also organized in a modular fashion with many independent but cooperative programs controlling the operation of the Mark 3 processor. Processing time through the correlator is normally real time or faster, with graphics displays providing real time monitor and control of the processing operation.

Whitney, A. R.↗