TOC  |      |      | Last Section | Next Section | INDEX 

pages.sum

The summary of pages input files and output information.

pages.sum does not contain diagnostic information.

The pages.sum file is divided into major and minor sections. Each section, except the first, has a title which provides quick access to that section via the search capability of most editors. Each major section is separated by a row of equal signs; each minor section by a row of dashes. The following outline shows the general structure of the pages.sum file. In the outline, each level contains the section title, upper case as it appears in the file, followed by discriptive comments.

1. Quick solution summary
   containing a brief setup summary, the post-fit RMS, singularity messages and the following
   • NUMBER OF SATELLITES
   • NUMBER OF STATIONS
   • NUMBER OF CONSTRAINED STATIONS
   • UNKNOWN PARAMETER SUMMARY
2. CONSTRAINTS/OPTIONS
   input through the pages.skl file
3. SKELETON FILE
   the pages.skl file
4. INPUT FILE
   the pages.inp file
5. OVERALL STATISTICS
   • RMS BY SATELLITE VS. BASELINE
   • OBS BY SATELLITE VS. BASELINE
   • % OMITTED BY SATELLITE VS. BASELINE
6. LIST OF PARAMETERS SOLVED FOR:
   • PHASE AMB
   • SATELLITE ADJUSTMENTS (does not appear in example)
   • STATION ADJUSTMENTS
   • EARTH ORIENTATION (does not appear in example)
7. STATION INFORMATION (INPUT AND OUTPUT VALUES)
   The example contains two sites:
   • brmu
   • gode
8. ADJUSTED BASELINE COMPONENTS
9. NORMAL TERMINATION message

• Quickly scan through the first section of the "quick solution summary". Verify that the start/stop times, observable frequency, interval, etc. are as expected. Check the OVERALL RMS. A good rule-of-thumb is the OVERALL RMS should be less than or equal to 0.015 meters for long lines and 0.012 meters for short lines. Any singularities should be listed just below the OVERALL RMS. Singularities should be rare considered carefully. Generally:
  • singularities in tropo parameters mean missing data from the indicated site and are of minimal concern,
  • one or two singularities in phase ambiguities, particularly when auto-editing the data, mean missing data from a satellite and are also of minimal concern,
  • any singularities in satellite or station parameters requires careful consideration. In the best circumstance, few observations are available from the satellite or station and the offending source could be eliminated from the solution. In the worst circumstance, data may be corrupt, or inappropriate to estimate the desired parameters. In this case, the data would have to be carefully evalutated or the experiment redesigned.
• Skip down to the OVERALL STATISTICS. The number of OBSERVATIONS should be greater than 10,000 observations per baseline per 24 hours of data for most baselines, the OMITTED observations should be small, and the WEIGHTED MEAN TIME should be roughly the mid-point of the data span. Scan the SATELLITE BY BASELINE statistics searching for high-RMS outliers and missing satellites.
• Finally, skip to the STATION INFORMATION section. Double check the source files for the station information and the antenna types. Finally check the both the XYZ and NEU ADJ and SIGMAS.

• the first column contains the totals for the indicated baseline,
• the last row contains the totals for the indicated satellite,
• if a "0 = FULL" run is specified, as in this example, the data are read twice, once to generate the normal matrix and solution, once to calculate the post-fit residuals. In this case, the "POST-FIT RMS" would be the true calculated RMS; the "RMS BY SATELLITE" would be the post-fit RMS's.
• if a "2 = THRU MATRIX INVERSION" run is specified, the "POST-FIT RMS" would be estimated from the standard error of unit weight; the "RMS BY SATELLITE" would be the a priori RMS's.

The "STATION INFORMATION" section differs from the "LIST OF PARAMETERS" because the former includes all pertinent a priori information and final, adjusted coordinates as well as the estimated adjustments; the latter is simply a listing of the estimated adjustments. Each station in the solution is included. Each station is listed separately starting with the keywords "STATION NAME:" and ending with a line of pluses except for the last which is separated from the next major section by a standard line of equal signs. The intent is to create a complete and readable block of information which could be printed separately as part of a report. The discriptive components of a station block are:

• the station name and alternative names. These alternatives are intended to be political, geographic or institutional names; all more easily recognizable as a physical location than the four character site ID.
• the source of the input information. If this is a binary site information file, the station information should be substantial. If the site could not be found in a site information file, the minimal information contained in the database will be used.
• the receiver with the receiver type ID numbers in parentheses, the firmware (F/W) designation, and receiver serial number (S/N).
• the antenna with the antenna type ID numbers in parentheses, and antenna serial number (S/N). At this time, the antenna information should be noted in particular. Immediately following the keyword "ANTENNA" is a number in parenthesis. This number is the identifier used in the antenna pattern file and must match the users expectations.
• the monument ID. Typically the DOMES number.
• the tectonic plate four character ID.
• meteorological info. If a RINEX met file is used, it will be named. If no met file is provided by the user, a reminder that a met model will be used instead is given. This model is dependent upon the station's ellipsoid height and latitude, and the date. The model includes a seasonal but not diurnal variation.
• the input information which includes
  • coordinates of the monument designated above with reference epoch,
  • coordinate sigmas,
  • velocity,
  • velocity sigmas,
  • any offsets between the designated monument and local, GPS monument,
  • any offsets to the antenna reference point (ARP),
  • eccentricity to the antenna phase centers.
  These input values are tagged with a descriptive label. The group as a whole is given date to identify the epoch in a site's history from which they were taken. Generally, if no monument-to-monument offsets or offsets to the ARP, the offsets will not be given.
• the "construction" of the monument, ARP and L1 phase center a priori coordinates at the weighted mean epoch of the solution. Each step is shown as a simple mathematical sum, with the components labeled.
• the adjusted L1 phase center, ARP and monument coordinates. Again, each step is shown a s mathematical sum and the epoch is the weighted mean epoch of the solution.
• the adjusted monument coordinates at a user specified epoch. The default epoch is the start of the year in which the data were collected.
• a summary block giving the XYZ coordinates of the L1 phase center, ARP, monument, and the estimated adjustment and formal adjustment sigmas.
• a summary block giving the geodetic coordinates of the L1 phase center, ARP, monument, and the north/east/up components of the estimated adjustment and sigmas. Note that geodetic coordinates are given in two line pairs. The first contains the latitude, east longitude and ellipsoidal height; the second gives the west longitude.

Sample Two-Site, One-Baseline pages.sum File

 TOC  |      |      | Last Section | Next Section | INDEX