UNAVCO Home UNAVCO Home
   |    |   |  
UNAVCO Home UNAVCO Facility

Software Remote PC Software RedHat Linux Auxiliary utilities Downloading & Data Transfer AOA Ashtech Trimble Other Pre-Processing TEQC Other Processing GAMIT/GLOBK Bernese GIPSY-OASIS II Trimble Geomatics (TGO) 		Bernese - Tutorial: Checking Output from PCS

Once the PCS has been started, output files will begin to be generated in the $P/DOCU40_1/OUT directory. There are three types of output files. One type of output file generates documents that report on the status of the PCS. These output files are known as protocol files. The second type of file shows the output from the Bernese programs. These files contain reports on the processing parameters used, the input and output files that are used or created, and statistics on the results of the program run. The third type of output file are the output result files. These can include normal equation output files, residual files, etc.

Protocol Files

The protocol output files generated from the PCS will be named according to the task id, year, session, and process id (PID). These file names have the following format: 



     Format : TDYRSESS.PID
     Example: 00971650.002

     Where:
     TD: 2-Characters : Task ID. Defined in panel 6.4.1. 
                        This is normally "00".
     YR: 2-Characters : The last two characters of the year. 
                        For this example "97".
     SESS: 4-Characters :The four character id of the session. 
                         Example "1650".
     PID: 3 to 7-Characters: The PID of the process. Example "002".

Program Output Files

The program output files normally have the program name as the base of the output file, and a unique integer suffix for each output file. 


	
     Format : PGMNAM.EXT
     Example: CODSPP.L01

     Where:
     PGMNAM: 6-Characters : The six character name of the program that 
                              was executed. Example CODSPP.
     EXT   : 3-Characters : A unique id automatically determined by the
                            Bernese program. Example L01.

An example output file for the program CODSPP (Panel program 4.2) is given as a linked file.

It is also possible to have program output files that have more descriptive names. These names are defined in the input data panels and will not be discussed here.

Analyzing Output From PCS Processing

To analyze the output files for the first day in the tutorial, move to the campaign directory structure. There should be a protocol file for every script in the PCF. For this example, the highest PID number will be 026. There will also be program output files for each of the Bernese processing programs that are executed during the PCF. 


[braunjizu WORK]$ cd $P/DOCU40_1/OUT
[braunjizu OUT]$ ls
00961650.001      00961650.019_004  COMPAR.L03        EU_96165.SME      MAUPRP.J
00961650.002      00961650.019_005  COMPAR.L04        GPSCMP.SUM        MAUPRP.L01
00961650.003      00961650.020      COMPAR.L05        GPSEST.J          MPRXTR.J
00961650.004      00961650.021      COOXTR.SUM        GPSEST.L01        MPRXTR.L01
00961650.005      00961650.022      DEFWKS.SUM        GPSEST.L02        MPRXTR.SUM
00961650.006      00961650.023      DEFXTP.J          GPSEST.L03        ORBGEN.J
00961650.007      00961650.024      DEFXTP.L01        GPSEST.L04        ORBGEN.L01
00961650.008      00961650.025      DEFXTR.SUM        GPSEST.L05        PRETAB.J
00961650.009      00961650.026      EG008574.SUM      GPSPOL.SUM        PRETAB.L01
00961650.010      ADDNEQ.J          EG096165.NEQ      GPSWKS.SUM        QIFXTR.SUM
00961650.011      ADDNEQ.L01        EG096165.SNX      GPSXTR.J          RESRMS.EDT
00961650.012      ADDNEQ.L02        EGB08574.SUM      GPSXTR.L01        RESRMS.J
00961650.013      AMBXTR.SUM        EGB96165.NEQ      GPSXTR.L02        RESRMS.L01
00961650.014      CODCHK.J          EGB96165.SNX      GPSXTR.L03        RESRMS.SUM
00961650.015      CODCHK.L01        EG_08574.SUM      GPSXTR.L04        RXOBV3.J
00961650.016      CODSPP.J          EG_96165.NEQ      GPSXTR.L05        RXOBV3.L01
00961650.017      CODSPP.L01        EQB08574.SUM      GPSXTR.L06        SNGDIF.J
00961650.018      CODXTR.J          EQB96165.NEQ      GPSXTR.L07        SNGDIF.L01
00961650.019      CODXTR.L01        EQ_08574.SUM      GPSXTR.L08
00961650.019_001  COMPAR.J          EQ_96165.NEQ      GPSXTR.L09
00961650.019_002  COMPAR.L01        EUROCLUS.96_165   GPSXTR.L10
00961650.019_003  COMPAR.L02        EU_96165.SMC      GPSXTR.SUM
The PCS protocol files can be viewed to show the the status of the script that is to be executed. For this tutorial, the second PID is the PRETAB script. It runs the program BRDTAB. This program translates the precise ephemeris from their SP3 file format into the internal bernese tabular format. This translation converts the orbits from their ITRF94 reference frame, into the J2000. inertial reference frame. See section 21.4.2 for a complete description of the protocol file. 

[braunjizu OUT]$ cat 00961650.002




	PROTOCOL FILE FOR BPE SCRIPT
	----------------------------
	 
	SCRIPT NAME         : PRETAB
	YEAR                : 96
	SESSION             : 1650
	CAMPAIGN            : DOCU40_1
	CAMPAIGN PATH       : P:/
	OPTION DIRECTORY    : EUROCLUS
	PROCESS ID          : 002
	SUB PROCESS ID      : 002
	CPU                 : CPU1
	PATH TO WORK AREA   : /home/braunj/GPSTEMP/AUTO0001
 
	 DATE      TIME     STA PROGRAM  MESSAGE
	----------------------------------------
	 30-OCT-97 11:16:06 MSG PRETAB   PROCESS STARTED
	 30-OCT-97 11:16:13 MSG BRDTAB   PROGRAM STARTED
	 30-OCT-97 11:16:20 MSG BRDTAB   PROGRAM ENDED
	 30-OCT-97 11:16:24 MSG PRETAB   PROCESS ENDED
	----------------------------------------

Return to the tutorial index page.

Last modified Wednesday, 16-Nov-2005 20:58:00 MST
 

Home | About Us | Contact Us | Support | Search | Facility | PBO | Education & Outreach

Comments: webmasterATunavco.org
© 2008 UNAVCO, Inc.