| Home | About Us | Contact Us | Support | Search | | Facility | | PBO | Education & Outreach | |
|
|
|
|||||||
 |
||
 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: Running The Process Control Script (PCS)
Once the PCF, scripts, and option directories have been checked, the data can be processed using the BPE, and the Process Control Script (PCS). The PCS is discussed in section 21.6 and in particular 21.6.6. For this tutorial, the PCS should run through without problems. The PCS can be started through the menu system, or can be run by hand from the $U/WORK directory. It is suggested that the BPE and the PCS be run through the menu system until the user is comfortable with the mechanics of the system. For this tutorial, the menu system will be used. Start the menu program by issuing the G command. The BPE Processing Engine can be accesed through section 6.
yochi[braunj]:V41-$ G
+---------+-------------------------------------------------------------------+
| Primary | Bernese GPS Software Version 4.0 |
+---------+-------------------------------------------------------------------+
| S:Y C:0 | |
+---------+-------------------------------------------------------------------+
| | |
| 0 .. | DEFAULTS : Defaults for Processing, Program and File Names|
| 1 .. | CAMPAIGNS : Informations and Update of Campaigns |
| 2 .. | TRANSFER : Data Transfer to Bernese Format; Simulation |
| 3 .. | ORBITS : Orbit Computation, Check and Update |
| 4 .. | PROCESSING : Preprocessing and Processing of Observations |
| 5 .. | SERVICES : Service Programs |
| 6 .. | BPE : Bernese Processing Engine |
| 7 .. | DOCU : Documentation, Help Panels |
| 9 .. | USER : Individual User Programs |
| | |
| =H | HELP : Get Help Panel |
| =X | EXIT : Terminate GPS Processing |
| | |
+---------+-------------------------------------------------------------------+
Enter Selection : 6
A BPE Processing session needs to be started. Select option 4 from the panel.
+---------+-------------------------------------------------------------------+
| 6 | BPE: OPTION MENU |
+---------+-------------------------------------------------------------------+
| S:Y C:0 | |
+---------+-------------------------------------------------------------------+
| | |
| 0 | PANEL UPDATE : Update Panels for New Release |
| 1 | PANEL EDITING : Prepare Option Panels for BPE |
| 2 | PREPARE RINEX : Prepare RINEX Files for BPE |
| 3 .. | SPECIAL FILES : Prepare Special Files for BPE |
| 4 .. | BPE PROCESSING : BPE Processing (Session or Campaign) |
| 5 .. | BPE SERVICES : BPE Service Programs |
| | |
+---------+-------------------------------------------------------------------+
Enter Selection : 4
For this tutorial, each session will be run individually. Therefore, select option 1.
+---------+-------------------------------------------------------------------+
| 6.4 | BPE: PROCESSING |
+---------+-------------------------------------------------------------------+
| S:Y C:0 | |
+---------+-------------------------------------------------------------------+
| | |
| 1 | SESSION PROCESSING: Process one or more Sessions of a Campaign |
| 2 | CAMPAIGN PROCESSING: Process an Entire Campaign |
| | |
+---------+-------------------------------------------------------------------+
Enter Selection : 1
The next panel (6.4.1) defines which CAMPAIGN area to use for processing, what JOB CHARACTER should be used, and what PCF should be used. Here, both the campaign and the process control file to use are named DOCU40_1. Fill in the appropriate fields with these selections. Leave the JOB CHARACTER field blank. +---------+--------------------------------------------------------------------+ | 6.4.1 | BPE: SESSION PROCESSING | +---------+--------------------------------------------------------------------+ | | | CAMPAIGN > DOCU40_1 < (blank for selection list) | | | | Job Identification: | | JOB CHARACTER > < (blank, or A..Z, 0..9) | | | | Input Files: | | PROCESS CONTROL FILE > DOCU40_1 < (blank for selection list) | | | +------------------------------------------------------------------------------+ Panel 6.4.1-1 defines the sessions and processing options that are to be used. The first session to be processed is 1650. The year is 1996. For now, process only a single session at a time. It is possible to enter multiple sessions and sequentially process the sessions. For example, if the NUMBER OF SESSIONS field was set to 2, then sessions 1650 and 1660 would be processed. The TASK IDENTIFICATION should be blank, and the rest of the options should be set as shown in the panel below. +---------+--------------------------------------------------------------------+ | 6.4.1-1 | BPE SESSION PROCESSING: INPUT OPTIONS | +---------+--------------------------------------------------------------------+ | | | Sessions Information: | | SESSION (START) > 1650 < | | YEAR (START) > 1996 < | | NUMBER OF SESSIONS > 1 < (if negative: processing backwards) | | | | Task Identification: | | TASK IDENTIFICATION > < (blank: 00) | | | | CPU/QUEUE Specification: | | CPU / BATCH QUEUE > NO < (NO, or blank for selection list) | | | | Special Options: | | SPECIAL PARAMETERS > NEW < (OLD.. NEW.. or ASIS) | | SKIP PROCESSES > NO < (YES.. NO, or ASIS) | | REMOTE SUBMIT > NO < (YES.. NO, or ASIS) | | DEBUGGING OPTIONS > NO < (YES.. NO, or ASIS) | | | +------------------------------------------------------------------------------+ This final menu (panel 6.4.1-1.3) appears because the SPECIAL PARAMETERS field was set to NEW in the previous panel. This panel shows some of the variables that will be used in the processing. These variables will be used to mostly to define names of orbit, coordinate, and solution files. These variables are substituted into the program panels before execution of the menu program. For example, look at panel $U/OPT/EUROCLUS/DAT33___.PAN. In this panel the $O place holder will be substitued for R3 before the menu program is run. In this panel the R3 variable will be substitued for the $O place holder before the menu program is run. In addition to the variables defined in panel 6.4.1-1.3, there are other variables defining session numbers; year numbers; and day numbers which are automatically set when running a PCS. In the name field for the tabluar orbit name above, the $Y field will be substituted with 96 and the $D1 field will be changed to 165 before the menu program is executed.| Input File | | TABULAR ORBITS > $O_$Y$D1 < (NO in case of orbit update, | +---------+--------------------------------------------------------------------+ |6.4.1-1.3| BPE SESSION PROCESSING: SPECIAL PARAMETERS | +---------+--------------------------------------------------------------------+ | | | Special Parameter Setting: | | EUROCLUS ORBIT FILE NAME "O" > R3 < | | AMBIGUITY FREE RESULTS "X" > EG < | | AMBIGUITY FIXED RESULTS "Z" > EQ < | | U .... "U" > UU < | | V .... "V" > VV < | | W .... "W" > WW < | | PLUS DAYS "PLUS" > +0 < | | MINUS DAYS "MINUS" > -0 < | | | | Control Process: | | SLEEP TIME > 0 < (in seconds, 0: default value used) | | | +------------------------------------------------------------------------------+ At this point, the PCS should be started. The PCS then scrolls to the screen a progress status report. This report shows the list of scripts that are to be run. The PCS executes the first script, in this example EURO_COP. Once that script is finished the PCS moves on and executes the next script (PRETAB). Below, the PCS has moved through the first seven scripts, and is working on the eighth script MAUPRP. WILL RUN PID 8 PID STATUS IN PRCNXT PID 001 EURO_COP EUROCLUS STARTED = T ENDED = T PID 002 PRETAB EUROCLUS STARTED = T ENDED = T PID 003 ORBGEN EUROCLUS STARTED = T ENDED = T PID 004 RXOBV3 EUROCLUS STARTED = T ENDED = T PID 005 CODCHK EUROCLUS STARTED = T ENDED = T PID 006 CODSPP EUROCLUS STARTED = T ENDED = T PID 007 SNGDIF EUROCLUS STARTED = T ENDED = T PID 008 MAUPRP EUROCLUS STARTED = T ENDED = F < PID 009 GPSEDT EUROCLUS STARTED = F ENDED = F PID 010 ADDNEQ EUROCLUS STARTED = F ENDED = F PID 011 COMPAR EUROCLUS STARTED = F ENDED = F PID 012 GPSBAS EURO_BAS STARTED = F ENDED = F PID 013 ADDNEQ EURO_BAS STARTED = F ENDED = F PID 014 COMPAR EURO_BAS STARTED = F ENDED = F PID 015 GPSEST EURO_IOF STARTED = F ENDED = F PID 016 GPSEST EUROFREE STARTED = F ENDED = F PID 017 COMPAR EUROFREE STARTED = F ENDED = F PID 018 GPSQIFAP EURO_QIF STARTED = F ENDED = F PID 019 GPSQIF_P EURO_QIF STARTED = F ENDED = F PID 020 QIFXTR EURO_QIF STARTED = F ENDED = F PID 021 GPSEST EURO_IOX STARTED = F ENDED = F PID 022 GPSEST EURO_FIX STARTED = F ENDED = F PID 023 COMPAR EURO_FIX STARTED = F ENDED = F PID 024 GPSEST EURO_FXB STARTED = F ENDED = F PID 025 COMPAR EURO_FXB STARTED = F ENDED = F PID 026 EURO_DEL EUROCLUS STARTED = F ENDED = F WILL SLEEP The PCS should continue on through all the scripts in the PCF. Once finished, the output files can be viewed in the campaign output directory. For this example that would be $P/DOCU40_1/OUT. The output files are discussed in a different section. Return to the tutorial index page. Last modified Thursday, 17-Nov-2005 03:58:00 UTC |
| ||
 |
Home | About Us | Contact Us | Support | Search | Facility | PBO | Education & Outreach Comments: webmaster |
|
unavco.org