TOC  |      |      | Last Section | Next Section | INDEX BY TYPE | INDEX ALPHABETICALLY

pages.skl

pages input file controlling the models and constaints used in the solution

Overview

The pages.skl file contains those model and constraint controls which rarely change. pages.skl is a required control file for pages. pages.skl is an ASCII file and, therefore, easily modifiable with an editor.

A basic pages.skl file contains two sections:

  1. model control,
  2. constraint control.
Each section will be described in detail below but some general rules are:
  1. Only one model control section is permitted,
  2. The model control entries must appear in the order shown,
  3. The model control entries should be included,
  4. The constraint controls are entered using a descriptive line or identifier, or an identifier and value,
  5. Any file name may include the path,
  6. The default path is always the current directory,
  7. The maximum length of a file name plus path is 64 characters,
  8. All characters to the right of a dollar sign, "$", are ignored,
  9. Lines starting with a dollar sign are skipped,
  10. Blanks are not significant except in names including constraint identifier names,
  11. Control flags are not case sensitive. However, file and site names, and constraint identifiers are case sensitive.

The growth in flexibility of the pages program has resulted in a large number of option controls.
To facilitate finding an control:

Model Control Section 

Example:                                                       Example
                                                             Line number
    0                    $ Diagnostics                           ( 1)
    900                  $ Screen Output Interval [sec]          ( 2)
    30                   $ Observation Interval [sec]            ( 3)
    15                   $ Elevation Cutoff [deg]                ( 4)
    540                  $ Data Gap [sec]                        ( 5)
    1.0E-01              $ Edit Limit [m]                        ( 6)
    0 0 3                $ Model Flags                           ( 7)
    1 1                  $ TSF Flags                             ( 8)
    7200   7200          $ TSF Max & Min Times [sec]             ( 9)
    1 90                 $ TSF Elv Bin Number & Limits [deg]     (10)
    0                    $ TSF Min Obs Number                    (11)
    0 0 0 0              $ PM & LOD Flags                        (12)
    86400                $ PM & LOD Time [sec]                   (13)
    ../files/site_info   $ Station Info File                     (14)
     $ Satellite Info File                                       (15)
     $ Descriptive Text File                                     (16)
     $ Pole File                                                 (17)
     $ UT1 File                                                  (18)
     $ Broadcast Orbit File                                      (19)
    ant_info.003         $ Antenna phase corrections             (20)
    END                                                          (21)

Following is a detailed explanation of each line of the Model Control Section of the pages.skl file:

Line 1. 


       0                    $ Diagnostics

The diagnostic flag controls the amount of information pages tells the user about its actions. The larger the number, the more information is output. The most common settings are: 

    0   = minimum info
    1   = post-fit residual plots
    2   = a priori and post-fit residual plots
This flag is potentially dangerous because of the large quantities of printed output which could be generated.

Line 2. 


       900                  $ Screen Output Interval [sec]

The screen output interval flag controls how frequently pages confirms its operation by writing the current data time to the screen. Units are in seconds. In the example, messages appear on the screen after each fifteen minutes of data are processed.

Line 3. 


       30                   $ Observation Interval [sec]

The observation interval flag controls how much data are used. Units are in seconds. For example, data may be recorded and edited using a 30-second interval, but processed by pages using a 120-second interval. The shorter interval would have advantages for data editing, but might be unnecessary for a satisfactory final solution.

Line 4. 


       15                   $ Elevation Cutoff [deg]

The elevation cutoff flag governs the minimum elevation an observation must be to be processed in pages.

Line 5. 


       540                  $ Data Gap [sec]

A gap in the data implies a discontinuity or cycle slip. The data gap flag specifies the minimum significant gap size in seconds. A new phase ambiguity for a baseline-satellite combination will be estimated automatically if a gap in the satellite's tracking is longer than this interval (and no integer bias has been given).

Line 6. 


       1.0E-01              $ Edit Limit [m]

Because pages has the capability to identify outliers and issue edit instructions to delete such data points, this parameter will set the limit, in meters, beyond which a point is designated as an outlier.

Lines 7 - 11 

    0 0 3                $ Model Flags
    1 1                  $ TSF Flags     
    7200    7200         $ TSF Max & Min Times [sec]
    1 90                 $ TSF Elv Bin Number & Limits [deg]
    0                    $ TSF Min Obs Number

The above five lines control the tropospheric model, the estimation type, and the interval. The first line of the five identifies the tropospheric, solid earth tide, and solar radiation pressure models to use. For the tropospheric model, three options are available: 


       0 = the Neill mapping functions, NMF, with Saastemoinen dry and wet tropo
            models (default);
       1  = the CfA 2.2 mapping functions with Saastemoinen dry and wet
            tropo models (vlbi);
       2  = tropo model included in the database. Currently this is the
            Marini model.
      

       For the solid earth tide model, there are three options:

       1 = The original model (subroutine etide)
       2 = The improved model (subroutine stide)
       other = The Dehant IERS model (subroutine ierstide)


       For the solar radiation pressure model, there are three options:

       1 = Use 1 solar radiation pressure parameter
       2 = Use 2 solar radiation pressure parameters
       3 = Use 3 solar radiation pressure parameters (3 axes)
		  with two sine/cosine terms for each axis -- for a
		  total of 9 parameters for each satellite

Line 8 contains two flags controlling the manner in which the tropo corrections are to be estimated. A "0" for both flags instructs pages not to estimate tropo corrections. This overrides any instructions in the pages.inp file. A "1" in the first position causes pages to estimate constant, additive, wet tropo corrections for the stations designated in the pages.inp file. A "1" in the second position causes a piecewise-linear, continuous wet tropo correction to be estimated regardless of the value of the first parameter.

Line 9 sets the duration of the estimated tropo correction. Two numbers appear on this line. Both values are used in current research. In normal operation both values must be identical. The units are in seconds.

Lines 10 and 11 are reserved for research and should be left at: 


         1 90
         0
respectively.

Lines 12 - 13 

    0 0 0 0            $ PM & LOD Flags
    86400              $ PM & LOD Time [sec]

The two lines above control the estimation of Earth orientation parameters (EOP). Line 12 controls which EOP are estimated and how. The four values actually are two pairs of values. The first pair controls the X and Y pole estimate, while the second pair controls the UT1 estimate. As with the tropospheric parameters, a "0" means no estimation should occur. A "1" in the first position of each pair instructs the program to estimate additive, constant corrections. A "1" in the second position of each pair causes a piecewise-linear continuous estimation.

Line 13 sets the frequency at which these EOP corrections are estimated. Units are in seconds. This limit applies to all EOP parameter estimates.

Line 14. 

       ../files/site_info $ Station Info File

Defines an input file name for A-priori station information.

Line 15. 

        $ Satellite Info File

In the current pages configuration, this line 15 is defunct.

Line 16. 

        $ Descriptive Text File

In the current pages configuration, this line 16 is defunct.

Line 17. 

        $ Pole File

This file contains A-priori information defining the X,Y pole values. The X and Y pole file must be named "pole." with no path and therefore must reside in the current directory, if named.

Line 18. 

        $ UT1 File

The UT1 file must be named "ut1." with no path and therefore must reside in the current directory, if named.

Line 19. 

        $ Broadcast Orbit File

Self-explanatory.

Line 20. 

       ant_info.003      $ Antenna Phase Corrections

Line 21. 

       END
This line marks the end of the Model Control Section

Constraint Control Section

Because the constraint control identifiers can appear in any order, the various possible identifiers will be listed alphabetically with their descriptions and examples, where necessary. The spelling and spacing of these identifiers is significant, all currently sanctioned identifiers are independent of case. This section name is somewhat misleading because many types of parameters can be entered or flags set in this section. Ultimately, all parameterization, including that described in the Model Control Section above, will be included in this section.

In the older versions of the program the keyword control identifiers were required to be in capital letters. For all currently santioned options they can now be in either upper or lower case. The form of some of these identifiers has also been changed to make them more consistant with each other. Many of the most used options have been retained in their older form as well and these, as previously, must be in upper case. For the following presentation all keywords are shown in bold upper case for emphasis. Each of the identifiers must be spelled exactly as shown below, however, additional letters at the end which might complete the spelling of a word would be ignored and thus acceptable. In addition any explanatory comments beyond the required fields will be ignored.

In versions of the program prior to June 98 units on the constraints were mostly defined as variances. The scaleing of all constraints are now defined by standard errors, except in a couple of cases where a multiplier of the apriori weight is used for increasing the weight of an individual constraint(this option is old and is in fact not really used but is still available).

The Constraint Control Section requires two identifiers regardless of the inclusion of any other identifiers:

OPTIONS
This identifies the start of the Constraint Control Section.
END_OPTS
This identifies the end of the Constraint Control Section.
All other constraint identifiers are optional. Some require additional information. These cases will be noted and described in detail including FORTRAN format specifications.

Following is a list, in alphabetical order, of all current options available for the Constraint Control Section of the pages.skl file:

AGENCY ID
The SP3 format requires a four-character ID for the agency which created the file. The default, "NOAA", can be overridden with this identifier. For this option the new four-character ID must be on the same line as the option keywords and must begin in column 16.

CONSTRAIN A PRIORI SCALE
Constrains the apriori scale of the reference frame. This constrains the adjustment such that individual sites move inwards or outwards from the center of the frame in a manner so the average distance of the sites from the center is unchanged, the result is that the original scale is unchanged. The sites used to define this constraint are the same used in the list for either identifier "CONSTRAIN AVERAGE COORD" or "CONSTRAIN SITE COORD" thus one or the other of these options (see below) must also be invoked to use the average scale constraint.
NOTE: requires additional input on next line.
The identifier is followed by the standard error to be applied.
UNITS: ppb (parts per billion)
FORMAT: Free format

CONSTRAIN A PRIORI VEL
Constrains all sites to their apriori velocities. The older keywords for implementing this constraint will still work see "HOLD APRIORI VELOCITIES" in pages.skl.oldstuff .
NOTE: requires additional input on next line.
The identifier is followed by the standard error to be applied.
UNITS: meters/year
FORMAT: Free format

CONSTRAIN A PRIORI UT1
Constrain the UT1 estimates to their a priori values. The standard error, in units of seconds, to be used in the constraint is also read in this block.
The identifier is followed by the standard error to be applied.
UNITS: seconds
FORMAT: free format

CONSTRAIN A PRIORI POLE
Constrain all pole X and Y values to their a priori values. The standard error, in units of milli-arc-seconds, to be used in the constraint is also read in this block.
The identifier is followed by the standard error to be applied.
UNITS: milli-arc-seconds
FORMAT: free format

CONSTRAIN APRIORI SAT. POSITION
Constrain the satellite coordinates to their a priori values. The standard error, in meters, is also entered in this block.
The identifier is followed by the standard error to be applied.
UNITS: meters
FORMAT: free format

CONSTRAIN APRIORI SAT. VELOCITY
Constrain the satellite velocities to their a priori values. The standard error, in m/sec, is also entered in this block.
The identifier is followed by the standard error to be applied.
UNITS: meters/seconds
FORMAT: free format

CONSTRAIN AVERAGE COORD
End is identified by END-AVSI
Constrains the centroid of a group of sites. Each site could shift but the average of the coordinates must not. The older keywords for implementing this constraint will still work see "AVG. SITE CONST" in pages.skl.oldstuff .
NOTE: requires additional input on subsequent lines.
There are two possible options to apply with this constraint:
1. USE A PRIORI
This option causes pages to use the centroid of the apriori station coordinates in defining the constraint equations. The next line must give a standard error to be applied to the constraint equation.
UNITS: meters
FORMAT: (13X, F16.6)
Immediately following the standard error line are the sites to be constrained, one line per site. The site identifiers follow the Sinex standards and have 3 parts, a 4 character site name, a 1 character "point code", and a sequence number. In the process of matching the list of constrained sites against the list of sites in the solution the match will be made based upon the site identifier specified in the following list. That is, if the sequence number is not given it will be ignored in the matching process and the same for the "point code". Thus one needs to specify only enough information to adequately identify the site that is to be included in the constaint. If a site is in the constraint list but is not in the data set being adjusted a warning message will be written out and that site identifier will not be used.
Example: 
           CONSTRAIN AVERAGE COORD

           USE A PRIORI

                                  1.0e-06

           sant

           algo a

           mcmu a 12

           END-AVSI
2. If USE A PRIORI is not specified, then the standard error line is followed by the lines designating the sites to be constrained and the coordinates to use for defining the centroid of those sites, one site per line. (Note:This option is best avoided, it is old and infrequently used. Care must be exercised in its use as the coordinates specified must be phase center coordinates.)
UNITS: meters
FORMAT: (A12, 1X, 3F16.6)
Example: 
           CONSTRAIN AVERAGE COORD

                                  1.0e-06

           sant           1769693.285393  -5044574.219096  -3468321.218509

           mcmu          -1310696.280131    310469.128906  -6213368.431436

           END-AVSI

CONSTRAIN AVERAGE VEL
End is identified by END-SITE
Constrains the average velocity of a group of sites. Each site's velocity could shift, but the average must not. The older keywords for implementing this constraint will still work see "AVG. SITE VEL. CONST." in pages.skl.oldstuff .
NOTE: requires additional input on subsequent lines.
The next line must define a constraint on either rotation or translation, and both may be included, one immediately following the other. These options are defined as follows:
ROTATION
Indicates a constraint on the rotation of the network, as defined by the velocities of the constrained sites. To specify this constrain the keyword "ROTATION" is followed by three rotational velocity components to be enforced and a standard error for the constraint.
UNITS: radians/year
FORMAT: (A12, 1X, 4F16.8)
TRANSLATION
Indicates a constraint on the translation of the network, as defined by the average velocity of the constrained sites. To specify this constraint the keyword "TRANSLATION" is followed by three velocity components to be enforced and a standard error for the constraint.
UNITS: meters/year
FORMAT: (A12, 1X, 4F16.8)
Following these entries, the identifiers of the sites to be used in the constraint are given, one entry per line.
Note that the velocity components defined in these constraints may be zero, or can be computed from an a-priori velocity model for the sites selected. To do so one must get the sum of the cross products of the (A-priori velocity - Model velocity) times the coordinate vector for the sites to be included.
Example: 
    CONSTRAIN AVERAGE VEL

    TRANSLATION             0.000      0.000     0.000     1.000e-05

    ROTATION                0.000      0.000     0.000     1.000e-05

    sant

    mcmu

    END-SITE

CONSTRAIN AVERAGE UT1
Constrains the average UT1 estimates.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: seconds
FORMAT: free format

CONSTRAIN FIRST UT1
Constrains the first UT1 estimate.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: seconds
FORMAT: free format

CONSTRAIN OPR PR1
Constrain the scale factors for the once-per-revolution radiation pressure 1 terms. The sigma, in dimensionless units, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: dimensionless
FORMAT: free format

CONSTRAIN OPR PR2
Constrain the scale factors for the once-per-revolution radiation pressure 2 terms. The sigma, in dimensionless units, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: dimensionless
FORMAT: free format

CONSTRAIN OPR PR3
Constrain the scale factors for the once-per-revolution radiation pressure 3 terms. The sigma, in dimensionless units, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: dimensionless
FORMAT: free format

CONSTRAIN RAD PR1
Constrain the radiation pressure 1 scale factors. The sigma, in dimensionless units, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: dimensionless
FORMAT: free format

CONSTRAIN RAD PR2
Constrain the radiation pressure 2 scale factors. The sigma, in dimensionless units, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: dimensionless
FORMAT: free format

CONSTRAIN RAD PR3
Constrain the radiation pressure 3 scale factors. The sigma, in dimensionless units, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: dimensionless
FORMAT: free format

CONSTRAIN SAT POS
Constrain the adjustments to piece-wise linear satellite coordinates to require, within limits of the sigma, that the successive values are equal. With this method using different values for sigma allows one to dampen the rate of change of the adjusted parameters, allowing flexibility, but not too much. The sigma, in meters, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: meters
FORMAT: free format

CONSTRAIN SAT VEL
Constrain the adjustments to piece-wise linear satellite velocities to require, within limits of the sigma, that the successive values are equal. With this method using different values for sigma allows one to dampen the rate of change of the adjusted parameters, allowing flexibility, but not too much. The sigma, in meters, is also entered in this block.
The identifier is followed by the standard deviation to be applied.
UNITS: meters
FORMAT: free format

CONSTRAIN SITE COORD
End is identified by END-INDV-SITES
Constrains the coordinates of the indicated sites. The older keywords for implementing this constraint will still work see "CONST. INDIVIDUAL SITE"
in pages.skl.oldstuff .
NOTE: requires additional input on subsequent lines.
There are two possible options to apply with this constraint:
1. USE A PRIORI
This option causes pages to use the a-priori station coordinates and sigmas to define the constraints. The site ID's and an additional factor which is multiplied times the weight to be applied to the constraints follow, one entry per line. (For site name matching criteria see above
CONSTRAIN AVERAGE COORD)
UNITS: meters
FORMAT: Free format
Example: 
         CONSTRAIN SITE COORD

         USE A PRIORI 

         kokb              1.000e+00

         algo b            1.000e+00

         madr a  9         1.000e+00

         END-INDV-SITES

2. Specify the site ID's, coordinates, and standard errors to be applied.
UNITS: meters
FORMAT: (A12, 1X, 3F16.8, E16.8)
Example: 
         CONSTRAIN SITE COORD

         sant          1769693.285393 -5044574.219096 -3468321.218509  1.000e-05

         mcmu         -1310696.280131   310469.128906 -6213368.431436  1.000e-05

         END-INDV SITES

CONSTRAIN SITE VELOCITY
End is identified by END-INDV-VEL.
Constrains the indivdual sites' velocities. The older keywords for implementing this constraint will still work see "CONST. INDIVIDUAL VEL." in pages.skl.oldstuff .
NOTE: requires additional input on subsequent lines.
There are two possible options to apply with this constraint.
1. USE A PRIORI
This option causes pages to use the input station velocities and sigmas as constraints. The site ID's and an additional factor which is multiplied times the weight to be applied to the constraints follow, one entry per line.
UNITS: (meters/year)squared
FORMAT: Free format
Example: 
         CONSTRAIN SITE VELOCITY

         USE A PRIORI

         kokb              1.000e+00

         algo              1.000e+00

         madr              1.000e+00

         END-INDV-VEL.

2. Specify the site ID's, velocities, and standard error to be applied.
UNITS: meters/year
FORMAT: (A12, 1X, 3F16.8, E16.8)
Example: 
         CONSTRAIN SITE VELOCITY

         sant                0.005          -0.007           0.002     1.000e-05

         mcmu                0.110          -0.110          -0.103     1.000e-05

         END-INDV-VEL.

CONSTRAIN TROPO
Constrain the troposphere zenith wet delays to their a priori values.
The standard error, in meters, is also entered in this block.
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: meters
FORMAT: free format

CONSTRAIN VELOCITY PAIRS
End is identified by END-PAIR
This identifier forces pairs of sites to have the same velocity.
The older keywords
for implementing this constraint will still work see "EQUAL VELOCITY PAIRS"
in pages.skl.oldstuff .
NOTE: requires additional input on subsequent lines.
The next line must give the standard error to be applied as the constraint.
UNITS: meters/year
FORMAT: Free format
Subsequent lines contain two site ID's per line, designating the
site pairs to constrain.
FORMAT: Free format
Example: 
         CONSTRAIN VELOCITY PAIRS

                               1.0e-07

         gait          gode

         kosg          brus

         END-PAIR

COMMENTS
End is identified by END_COMM
Any remarks desired may be placed between these identifiers.

BRK SAT POS ON
Enable and specify the interval, in seconds, for re-estimation of satellite coordinates. For this option the interval to be used follows the keywords on the same line.

BRK SAT VEL ON
Enable and specify the interval, in seconds, for re-estimation of satellite velocities. For this option the interval to be used follows the keywords on the same line.

BRK RAD PR ON
Enable and specify the interval, in seconds, for re-estimation of radiation pressure scale factors. For this option the interval to be used follows the keywords on the same line.

DO NOT USE PHASE PATTERN HORIZ
This identifier forces pages to ignore the horizontal information in the IGS format antenna phase correction file (ant_info) regarding the offsets from the antenna reference point to the L1 and L2 phase centers. When this option is invoked the program uses the information about the horizontal offsets that is contained in the header (*hd.dat) file which, in turn, is taken from the POM files.

DO NOT USE PHASE PATTERN OFFSETS
This identifier forces pages to ignore the information in the IGS format antenna phase correction file regarding the offsets (ant_info) from the antenna reference point to the L1 and L2 phase centers. This option turns off both horizontal and vertical offsets. When this option is invoked the program uses the information about offsets that is contained in the header (*hd.dat) file which, in turn, is taken from the POM files.

DO NOT USE PHASE PATTERN VERTI
This identifier forces pages to ignore the vertical information in the IGS format antenna phase correction file (ant_info) regarding the offsets from the antenna reference point to the L1 and L2 phase centers. When this option is invoked the program uses the information about the vertical offsets that is contained in the header (*hd.dat) file which, in turn, is taken from the POM files.

EPOCH FOR OUTPUT
The coordinates of all sites are rotated to a common epoch on output. The default is the start of the year in which the adjustment is being computed. This default can be changed with this identifier.
NOTE: requires additional input on next line.
The identifier is followed on the next line by a date.
FORMAT: one of the following:

FIRST VALID TIME
Occasionally, the coordinates for a site change, when the reference frame is updated, for example. pages searches the site information for the appropriate coordinates for the date the data were taken. This identifier limits the search effectively forcing sites to have consistent coordinates through all processing. This is essential for long term projects. The older keywords for implementing this option will still work see "TIME FOR APRIORI VALUES" in pages.skl.oldstuff .
NOTE: requires additional input on next line.
The identifier is followed by a date.
FORMAT: one of the following:

FRAME ID
The SP3 format requires a five-character ID for the agency which created the file. The default, "ITR96", can be overridden with this identifier.
NOTE: requires additional input on next line.
The identifier is followed by a string on the same line.
FORMAT: (15x,A)

IGNORE INPUT OCE
Instruct the program to ignore the user input ocean loading parameters.

LAST SITE_INFO MODIFICATION
Option for last acceptable modification to site info file. This option is distinct from "FIRST VALID TIME" in that this option will reject all changes to the site_info file after the specified date given.
NOTE: requires additional input on next line.
The identifier is followed by a date.
FORMAT: one of the following:

MAKE EOP GLOBAL
Indicates that EOP parameters are to appear in the global part of the matrix.

MAKE SATELLITES GLOBAL
Indicates that satellite parameters are to appear in the global part of the matrix.

MAKE SITE TROPO GLOBAL
End is identified by END-TROPO
Designates sites whose tropospheric corrections should be carried in the global part of the matrix. This is necessary for sites common in normal matrices to be joined into a combined adjustment using the program gpscom. The older keywords for implementing this constraint will still work see "DEFINE JUNCTION SITES" in pages.skl.oldstuff .
NOTE: requires additional input on subsequent lines.
The site ID's are listed, one per line or the phase "use all sites" is recognize and accepted.
Examples: 
         MAKE SITE TROPO GLOBAL

         sant     

         mcmu    

         END-TROPO
or 
         MAKE SITE TROPO GLOBAL

         use all sites

         END-TROPO

MAX MOD
Each site info record is tagged with the date that record was created or last modified. For example, if an antenna change were made on June 12, 1999 and the appropriate antenna record delineating that change were inserted into a site info file on June 15, 1999; the date that the info would become valid, the "val" date would be 99/06/12, but the modification, or "mod" date would be 99/06/15.

This option forces the program to ignore records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX A MOD
This option forces the program to ignore antenna records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX C MOD
This option forces the program to ignore coordinate/velocity records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX G MOD
This option forces the program to ignore geodetic offset records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX M MOD
This option forces the program to ignore met sensor records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX O MOD
This option forces the program to ignore ocean loading records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX R MOD
This option forces the program to ignore receiver records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX T MOD
This option forces the program to ignore topocentric offset records with a "mod" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX VAL
Each site info record has a date on which the information in that record becomes valid. For example, if an antenna change were made on June 12, 1999, the "val" date for the site info record containing delineating that change would be 99/06/12.

This option forces the program to ignore records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX A VAL
This option forces the program to ignore antenna records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX C VAL
This option forces the program to ignore coordinate/velocity records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX G VAL
This option forces the program to ignore geodetic offset records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX M VAL
This option forces the program to ignore met sensor records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX O VAL
This option forces the program to ignore ocean loading records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX R VAL
This option forces the program to ignore receiver records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MAX T VAL
This option forces the program to ignore topocentric offset records with a "val" date later than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN MOD
Each site info record is tagged with the date that record was created or last modified. For example, if an antenna change were made on June 12, 1999 and the appropriate antenna record delineating that change were inserted into a site info file on June 15, 1999; the date that the info would become valid, the "val" date would be 99/06/12, but the modification, or "mod" date would be 99/06/15.

This option forces the program to ignore records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN A MOD
This option forces the program to ignore antenna records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN C MOD
This option forces the program to ignore coordinate/velocity records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN G MOD
This option forces the program to ignore geodetic offset records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN M MOD
This option forces the program to ignore met sensor records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN O MOD
This option forces the program to ignore ocean loading records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN R MOD
This option forces the program to ignore receiver records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN T MOD
This option forces the program to ignore topocentric offset records with a "mod" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN VAL
Each site info record has a date on which the information in that record becomes valid. For example, if an antenna change were made on June 12, 1999, the "val" date for the site info record containing delineating that change would be 99/06/12.

This option forces the program to ignore records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN A VAL
This option forces the program to ignore antenna records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN C VAL
This option forces the program to ignore coordinate/velocity records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN G VAL
This option forces the program to ignore geodetic offset records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN M VAL
This option forces the program to ignore met sensor records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN O VAL
This option forces the program to ignore ocean loading records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN R VAL
This option forces the program to ignore receiver records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

MIN T VAL
This option forces the program to ignore topocentric offset records with a "val" date earlier than that supplied by the user as part of this command.

The date is entered on this same line in one of the following formats:

NO APRIORI INFO MATRIX
This option instructs pages not to include the aprioir information matrix in the Sinex file.

NO OCEAN-LOADING
Instruct the program to turn off all ocean loading models.

NO SOLUTION
Forces pages to exit immediately after creating and writing the normal matrix file.

NO XYZ ROTATION ABOUT X
Constrains the average rotation of the network as defined by the computed coordinate shifts, about the X-axis. The sites used to define this constraint are the same used in the list for either identifier CONSTRAIN AVERAGE COORD or CONSTRAIN SITE COORD thus one or the other of these options (see above) must also be invoked to use the average scale constraint.
NOTE: requires additional input on next line.
The identifier is followed by the standard error to be applied.
UNITS: mas (milli-arc seconds)
FORMAT: Free format

NO XYZ ROTATION ABOUT Y
Constrains the average rotation of the network as defined by the computed coordinate shifts, about the Y-axis. The sites used to define this constraint are the same used in the list for either identifier CONSTRAIN AVERAGE COORD or CONSTRAIN SITE COORD thus one or the other of these options (see above) must also be invoked to use the average scale constraint.
NOTE: requires additional input on next line.
The identifier is followed by the standard error to be applied.
UNITS: mas (milli-arc seconds)
FORMAT: Free format

NO XYZ ROTATION ABOUT Z
Constrains the average rotation of the network as defined by the computed coordinate shifts, about the Z-axis. The sites used to define this constraint are the same used in the list for either identifier CONSTRAIN AVERAGE COORD or CONSTRAIN SITE COORD thus one or the other of these options (see above) must also be invoked to use the average scale constraint.
NOTE: requires additional input on next line.
The identifier is followed by the standard error to be applied.
UNITS: mas (milli-arc seconds)
FORMAT: Free format

OBSERVATION STANDARD ERR
Enter the a priori standard error of the observable. When this information is not provided a default standard error of 10cm. is assigned to the observations. The older keywords for implementing this constraint will still work see "OBSERVATIONS STANDARD ERROR" in pages.skl.oldstuff .
NOTE: requires additional input on next line.
The identifier is followed by the standard deviation to be applied.
UNITS: meters
FORMAT: free format

PLOT POST-FIT
Create post-fit plots.

PLOT A PRIORI
Create a priori plots.

PLOT AZ-EL
Create azimuth-elevation plots.

PLOT ION
Create ion residual plots.

PROJECT NAME
The project name.
NOTE: requires additional input on next line.
FORMAT: (A72)

PWL RAD PR ON
Enable and specify the interval, in seconds, for piece-wise, linear estimation of radiation pressure scale factors. When this option is used the interval time follows the kewords on the save line. Alternatively the additional keyword AUTO can be given rather than the time interval, in which case the program will determine when to provide a break in the parameter. If the program determines the time of the break and the satellite enters eclipse the time of eclipse will be used in determining the time of the break in the parameter.

PWL SAT POS ON
Enable and specify the interval, in seconds, for piece-wise, linear estimation of satellite coordinates. When this option is used the interval time follows the kewords on the save line. Alternatively the additional keyword AUTO can be given rather than the time interval, in which case the program will determine when to provide a break in the parameter. If the program determines the time of the break and the satellite enters eclipse the time of eclipse will be used in determining the time of the break in the parameter.

PWL SAT VEL ON
Enable and specify the interval, in seconds, for piece-wise, linear estimation of satellite velocities. When this option is used the interval time follows the kewords on the save line. Alternatively the additional keyword AUTO can be given rather than the time interval, in which case the program will determine when to provide a break in the parameter. If the program determines the time of the break and the satellite enters eclipse the time of eclipse will be used in determining the time of the break in the parameter.

SAVE SATELLITES
Instruct the program the satellite parameters are to be saved as reduced local parameters in the global normal matrix file for subsequent back substitution using the global solution and inverse from a combined adjustment.

SAVE TROPOSPHERES
Instruct the program the troposphere parameters are to be saved as reduced local parameters in the global normal matrix file for subsequent back substitution using the global solution and inverse from a combined adjustment.

SITE INFO
Additional station information file names. The older keywords for implementing this option will still work see "STATION INFO" in pages.skl.oldstuff .
NOTE: requires additional input on next line.
The identifier is followed by a file name.
FORMAT: Free format

TOLERANCE
The tolerance to singularities. LS matrix rows with Googe numbers smaller than this value will be designated singular and set to zero. When the tolerance is not specified in this manner the value 1.0d-5 will be used as a default.
NOTE: requires a value on next line.
UNITS: dimensionless
FORMAT: Free format

TURN OFF DECORR
Double-differencing introduces mathematical correlations between observations. The current default is to apply a de-correlation technique which corrects for this effect. This identifier forces pages to turn off the de-correlation technique which corrects for this effect. If used the correlations will not be accounted for in the processing. In older versions of the program (before Jan. 1999) the default was the opposite, that is to not apply the de-correlation technique. At that time there was an option "APPLY DD CORRELATIONS". This option will no longer be recognized.

UNCONSTRAIN AVERAGE X C
Turns off the constraint on the average X coordinate for the sites selected in identifier "CONSTRAIN AVERAGE COORD" which frees this parameter for adjustment when the average site coordinate constraint is in place. The older keywords for implementing this option will still work see "TURN OFF AVG. SITE X" in pages.skl.oldstuff .

UNCONSTRAIN AVERAGE Y C
Turns off the constraint on the average Y coordinate for the sites selected in identifier "CONSTRAIN AVERAGE COORD" which frees this parameter for adjustment when the average site coordinate constraint is in place. The older keywords for implementing this option will still work see "TURN OFF AVG. SITE Y" in pages.skl.oldstuff .

UNCONSTRAIN AVERAGE Z C
Turns off the constraint on the average Z coordinate for the sites selected in identifier "CONSTRAIN AVERAGE COORD" which frees this parameter for adjustment when the average site coordinate constraint is in place. The older keywords for implementing this option will still work see "TURN OFF AVG. SITE Z" in pages.skl.oldstuff .

USE FRAME
This identifier limits the search for site coordinates to a specific frame designation like "ITRF97". This effectively forces sites to have consistent coordinates through all processing, which is essential for projects whose data spans a considerable time period. The last coordinate record with the user requested frame designation will be used. Sites which do not contain a site info record with this frame will be searched normally. This option also set the "FRAME ID" option to the same value.

NOTE: requires additional input on the same line, e.g.
use frame ITRF97

USE PHASE PATTERN HORIZ
This identifier forces pages to use the horizontal information in the IGS format antenna phase correction file (ant_info) regarding the offsets from the antenna reference point to the L1 and L2 phase centers.

WRITE INTEGER FILES
Instructs pages to create phase ambiguity (integer) files in the standard format. The older keywords for implementing this constraint will still work see "OUTPUT INTEGER FILES" in pages.skl.oldstuff .

WRITE NORMAL
Causes pages to create the normal matrix output file named pages.nrm. Several of these files for different data sets can then be joined into a combined adjustment of the global parameters using the program gpscom.

WRITE SINEX
Causes pages to create the SINEX output file named pages.snx.
NOTE: requires additional input on subsequent lines.
This identifier requires the following information, one entry per line, in this exact order:
DESCRIPTION
description of the processing which produced this SINEX file;
OUTPUT
organization creating this file;
CONTACT
email address of person to contact with questions regarding this processing;
SOFTWARE
program name;
HARDWARE
system/hardware description;
INPUT
data source.

FORMAT: Free format

WRITE TROPO FILE
Write the file containing the tropo delays.

Sample pages.skl File

 TOC  |      |      | Last Section | Next Section | INDEX BY TYPE | INDEX ALPHABETICALLY
skl.html
March 11, 2005
Steve Hilla