New processing examples - Bernese GNSS Software

More documents

Recommendations

Info

Example BPE: General Aspects R. Dach et al.: Bernese GNSS Software: Processing Examples in Version 5.2 Document compiled: Bern, July 2, 2013 Example BPE: General Aspects README–Files on the Example BPEs Standard–Variables for the Dataflow Defining Standard Processing Files Defining the Reference Frame Set of Project–Specific Files Selecting Orbit/Clock Products Define Basic Modeling Aspects Hourly Processing Limitation of the BPE Variables Slide 39 of 86 Astronomical Institute, University of Bern AIUB README–Files on the Example BPEs Each example BPEs is accomplished by an extensive README file: • explaining the main purpose R. Dach et al.: Bernese GNSS Software: Processing Examples in Version 5.2 Document compiled: Bern, July 2, 2013 • providing a detailed description on the realization of the purpose, • showing where to find the key quality indicators for the results and giving some ideas about potential sources of problems • listing of the BPE server variables in the BPE example PCF with a short explanation on their usage • listing of the necessary input files for the processing and where they are expected in the DATAPOOL area • listing of the result files and where they are located in the SAVEDISK area with the current configuration Slide 40 of 86 Astronomical Institute, University of Bern AIUB
Standard–Variables for the Dataflow R. Dach et al.: Bernese GNSS Software: Processing Examples in Version 5.2 Document compiled: Bern, July 2, 2013 BPE–variables for the dataflow (DATAPOOL→CAMPAIGN52): (all BPEs) • V_RNXDIR (default: “RINEX” or “HOURLY”) Directory in the ${D} (DATAPOOL) area where the RINEX files are expected. • V_OBSSEL (select according to your needs) This variable may contain a filename for a cluster file or a file with the RINEX station abbreviations. Slide 41 of 86 Astronomical Institute, University of Bern AIUB Standard–Variables for the Dataflow R. Dach et al.: Bernese GNSS Software: Processing Examples in Version 5.2 Document compiled: Bern, July 2, 2013 BPE–variables for the dataflow (DATAPOOL→CAMPAIGN52): (all BPEs) • V_REFDIR (default: “REF52”) Directory in the ${D} (DATAPOOL) area where the basic Bernese files for the processing are located. • V_REFINF (default: “IGB08”) Reference frame files (CRD and VEL), used as master files when updating coordinate and velocity files. • V_CRDINF (any project name, e.g., “EXAMPLE”) The basename of the files used as basic Bernese input files for this example BPE. Slide 42 of 86 Astronomical Institute, University of Bern AIUB
Page 1 and 2: Bernese GNSS Software: Processing E
Page 3 and 4: Directory Structure Main Directorie
Page 5 and 6: Populating the DATAPOOL area Let us
Page 7 and 8: Populating the DATAPOOL area Let us
Page 9 and 10: Realization of the Example Dataflow
Page 11 and 12: Example for a XXX_SAV-script: R2S_S
Page 13 and 14: Consequences from the Example Dataf
Page 15 and 16: What Applications Shall be Covered
Page 17 and 18: Processing Example: CLKDET.PCF R. D
Page 19: Example Dataset R. Dach et al.: Ber
Page 23 and 24: Defining Standard Processing Files
Page 25 and 26: Defining the Reference Frame BPE-va
Page 27 and 28: Selecting Orbit/Clock Products R. D
Page 29 and 30: Example BPE: Specific Aspects R. Da
Page 31 and 32: BPE-specific Variables (PPP) R. Dac
Page 33 and 34: BPE-specific Variables (RNX2SNX) R.
Page 35 and 36: BASTST-Example PCFile name: ${U}/PC
Page 37 and 38: BPE-specific Variables (CLKDET) Int
Page 39 and 40: Preparing the Campaign You have to
Page 41 and 42: Filling the DATAPOOL Put the needed
Page 43: Generate Project Related Files A se

New processing examples - Bernese GNSS Software

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

Delete template?

Save as template?