TOC | | Gpscom | Pages | Next Section | INDEX
The current rules in Snxdif for matching site names from one Sinex file to another is that the name and the point code (the letter designation) must match. The sequence number is included in the match as a secondary condition because it is an arbitrary number under Sinex rules which is defined internally to the particular Sinex file. So Sinex files for the ITRF or any other agency would never have matches to those of NGS if the sequence number was included in the match. In the case of NGS Sinex files different sequence codes do have meaning and we could have more than one set of sequence codes in the same adjustment if the adjustment included a large time span. Thus following rules have been adopted. When the program is matching site names for two different files and it finds that the site name and point code matches it then searches to find a site where the sequence number also matches if no sequence number matches it will accept the first occurring name match.
This program was written in FORTRAN. Predominantly ANSI standard FORTRAN, a few isolated routines query the operating system for time and date, user and system identification. These "system" routines are inherently non-portable but, should be easily modified or disabled.
Program prompt -> TYPE SINEX FILE NAME _
responce -> (give 1st file name)
Program prompt -> READ ANOTHER DATA SET Y/N/A _
responce -> y
(if above answer is 'n' a TEST run is assumed
and alternate questions will follow.
Program prompt -> TYPE SINEX FILE NAME _
responce -> (give reference file name)
Program prompt -> TYPE PRINT FILE NAME _
responce -> (give print file name)
Program prompt -> TYPE (freefield) Time for matching data sets _
responce -> (carriage return, or date and time)
date/time forms = yy mm dd hh mm ss.ss
= yy doy hh mm ss.ss
= yy mm dd
= yy doy
= mjd.ddddd
If this line is commented, comments must follow
column 32.
Program prompt -> Rotate, Translate & Scale coordinates to match ?
responce -> y
(if above answer is 'n' addional prompts will be
given to query the user to individually specify
whether to solve for rotation, translation or
scale. Experiment!)
Before the next prompt a list of site names will be printed.
Program prompt -> The sites selected from this list may be either
Program prompt -> excluded or included in the adjustment.
Program prompt -> Will you specify an exclusion list?
responce -> y
(answering 'y' as shown means all site names
specified will be excluded from the adjustment
for the seven parameter transformation. The
program now requires the user to list site
names one per line and a blank line will end the
list. If only a blank line is entered then all
sites will be included in the adjustment.
A responce of 'n' will reverse the sence of the
list causing only listed sites to be included
in the adjustment.)
Program prompt -> TYPE THE NAMES OF SITES TO BE EXCLUDED(Included)
Program prompt -> FROM THE ADJUSTMENT FOR ROTATION & TRANSLATION
Program prompt -> A BLANK OR (CR) WILL END THE LIST
Program prompt ->
Program prompt -> THE FOLLOWING SITES WILL BE Excluded
Program prompt -> Exclude SITE NAMED _
responce -> ALGO A
responce -> (blanks or carriage return)
(the above 2 responces would cause the site
ALGO to be excluded from the seven parameter
adjustment.)
Program prompt -> THE CENTER OF Adjustment CAN BE ABOUT THE ORIGIN, '
Program prompt -> the CENTROID , or ABOUT A SITE SELECTED HERE. '
Program prompt -> TYPE BLANK OR (CR) FOR THE ORIGIN, ELSE SITE = _'
responce -> (blanks or carriage return)
(the above prompt and responce allow the user to
shift the origin of the coordinate system to the
centoid of the sites of to some particular site
before the seven parameter adjustment is done.
This is not generally used.)
When several comparisons of Sinex files are being made together
it gets tiresome to answer the prompts when running the program.
In this case the user can make a file containing the answers to the
prompts which will be given. Then if the input file were named
"snxdif.inp" the program could be run the as in the following example.
snxdif < snxdif.inp > junk.purge
In this case a file such as the examples below would be prepared.
The comments shown could be included without harm. However on lines
where a file name was being given trailing comments would cause
problems.
--------------------------------------------------------
gpscom.snx
y read another data set ?
/gyp5/ITRF96.SNX.short
test.output
Time for Matching
y Rotate, translate & scale?
y specify exclusion list ?
-----------------------------------------------------
--------------------------------------------------------
gpscom.snx
y read another data set ?
/gyp5/ITRF96.SNX.short
test.output
Time for Matching
y Rotate, translate & scale?
n specify exclusion list ?
KOKB A
ALGO A
MDO1 A
TROM A
KOSG A
WTZR A
MATE A
YELL A
FAIR A
GOLD B
YAR1 A
HART A
MADR A
-----------------------------------------------------
TOC | | Gpscom | Pages | Next Section | INDEX