08.06.2013 Views

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

20. Processing Examples<br />

#<br />

# Create summary file, save results, and delete files<br />

# ---------------------------------------------------<br />

901 R2S_SUM R2S_GEN ANY 1 522<br />

902 R2S_SAV R2S_GEN ANY 1 901<br />

903 R2S_DEL R2S_GEN ANY 1 902<br />

904 BPE_CLN R2S_GEN ANY 1 903<br />

#<br />

# End of BPE<br />

# ----------<br />

999 DUMMY NO_OPT ANY 1 904<br />

PID 901 R2S SUM: This script creates a processing summary giving a comprehensive<br />

overview of the most important results. The included information is:<br />

• Error messages, warnings, and pseudo-graphics concerning RINEX conversions<br />

• Orbit generation, single-point-positioning, preprocessing, and screening summaries<br />

• Lists of files rejected during preprocessing<br />

• QIF ambiguity resolution summary<br />

• Preliminary and final results (coordinates and troposphere)<br />

• Verification of the datum definition<br />

• Sliding multi-session comparison of station coordinates<br />

PID 902 R2S SAV: Used to save session result files in directories of your choice.<br />

PID 903 R2S DEL: Files from previous RNX2SNX runs are deleted from the campaign directory.<br />

This is done with a sliding window deleting all old files except of the last<br />

7 sessions.<br />

PID 904 BPE CLN: This step is responsible for cleaning up BPE-specific files (LOG and PRT<br />

files in the campaign’s BPE directory) with a delay of 30 sessions.<br />

PID 999 DUMMY: Does nothing.<br />

The result saving step (PID 902) is skipped in this example. This can easily be changed by<br />

removing the SKIP keyword in the PCF for this PID.<br />

The deletion script (PID 903) can be forced to delete all files not only from previous but<br />

also from the current session (except of some important result and summary files) by setting<br />

PARAM1 to ALL.<br />

The DUMMY-script may seem useless at a first glance. But if you have such a script running<br />

at a well defined PID in all your PCFs the successful execution of a BPE can be tested in<br />

a generic way by checking the presence of the script’s LOG- or PRT-file. In this way a script<br />

starting a BPE can react in case of errors (e.g., send an error mail).<br />

Further Reading: Section 19.10: BPE Output and Protocol Files (page 415), Section 19.11:<br />

Error Handling (page 417).<br />

Page 446 AIUB

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!