Example command file

1. Run with -d 299 -w 16072

• Example track command file for processing Soton data

• -----------------------------------------------------------------
• OBS_FILE
• Give the rinex file names to be processed. The obs_file command
• must be given first. At least one site must be named as F which
• means the position of the site is fixed. It is recommended to have
• only one fixed site. The other sites are denoted K for kinematic.
• NOTE: At least one blank line must follow the last station in
• the list and there can be no blank lines between the station
• list.

• To use this command file the -d and -w options must be used in the
• runstring (called in the track_std_manual.sh script):
• track -f track_test.cmd -d 299 -w 16072
• The string after the -d and -w replace the <day> and <week> strings
• below

obs_file 
  ref2 ref2<day>a.10o F
  base base<day>b.10o K

• -----------------------------------------------------------------
• NAV_FILE
• An orbit file must be given.
• NOTE: when 24-hours of data are processed the sp3 files from
• day before and after need to be concatinated withe sp3 file
• from the day being processed to ensure that that are ephemeris
• entries before and after the last data points. A simple unix
• cat command can be used to generate the merged files.

nav_file igu<week>_00.sp3 sp3

• -----------------------------------------------------------------
• MODE
• A quick method for setting up track is select a mode.
• "short" for baselines to ref station up to 1 km
• "long" for baselines to ref station greater than 1 km
• glacsweb ref station approximately 1 km away so use "short"

mode short

• ----------- <END of required inputs> ---------------------------
• The commands below are optional and are used to specify output
• files and change some defaults

• Specify day specific output files

pos_root TRAK<day>a.10

• res_root TRAK<day>

sum_file TRAK<day>a.10.sum

• Select the output coordinate type. For quick assessment and
• looking at relative motions North, East and Up (all in meters)
• are convenient
• Use NEU+GEOD to get both NEU output and geodetic lat, long and height.
• Use GEOD to get just geodetic coordinates.

out_type NEU+GEOD

• Running the smoothing filter is recommended on long baselines
• because this uses all the data for atmospheric delay estimation
• and any non-integer biases (non-resolved biases) are constant
• also can be useful on short baselines

back smooth

• If the sampling interval is in the rinex files this is not needed
• unless a longer sampling interval is desired

interval 1

• Size of jump in ionospheric delay that will be flagged as cycle slip.
• Can be increased for noisy data

ion_stats 0.5 

• By default a gap in the data introduces a new bias flag in track.
• bf set controls the size of the gap that causes this flagging

bf_set  1  20

• The site_stats command determines if a site position will be able
• to change during the processing.

site_stats
  all 4.472 4.472 4.472  4.472 4.472 4.472 

• float_type - Parameters of the sigmas limits and weights to different
• data types often can be changed for specific data sets to resolve
• more biases to integers. Caution should be used to avoid fixing
• biases to the wrong integer values. Small changes to the default
• parameters to resolve more bias parameters for this data.

• float_type 1 1 LC 0.5 1