文档库

最新最全的文档下载
当前位置:文档库 > gamit track命令官方解释

gamit track命令官方解释

# Run with -d 356_19 -w 12501 * * Example track command file for processing San Simeon 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 recommended to have * only one fixed site. The other sites are denoted K for kinematic. * The site_stats command determines if a site position will be able * to change during the processing. * 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 used in the * runstring: * track -f track.cmd -d 356_19 -w 12501 * The string after the -d and -w replace the and strings * below
obs_file trak trak.03o F pin1 pin1.03o K pomm pomm.03o K lows lows.03o K crbt crbt.03o K
*----------------------------------------------------------------- * NAV_FILE * An orbit file must be given. In this case we are using the * mit GPS week 1250 day 1 SP3 orbit file. * 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 mit.sp3 sp3
*----------------------------------------------------------------- * MODE * A quick method for setting up track is select a mode. In this case * since the baselines are up to 300 km long we used mode long. * Defaults set in this mode can be changes with commands after * setting the mode. mode long
*----------- --------------------------- * The commands below are optional and are used to specific output * files and change some defaults
* Specific day specific output files
pos_root TRAK
res_root TRAK
sum_file TRAK.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
* Running the smoothing filter is reccommended on long baselines * because this uses all the data for atmospheric delay estimation * and any non-integer biases (non-resolved biases) are constant back smooth
* If the sampling interval is in the rinex files this is not needed * unless a longer sampling interval is desired interval 1
* Small changes to the default parameters to resolve more bias * parameters for this data. x float_type 1 1 LC 0.5 1
* By default and gap in the data introduces a new bias flag in track * For high rate, telemetered data there are often gaps due to missed * telemeter. F

免费下载Word文档免费下载: gamit track命令官方解释

(共2页)