Changeset 4728 in ntrip


Ignore:
Timestamp:
Sep 11, 2012, 12:16:51 PM (12 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r4726 r4728  
    4848<ul>
    4949<li> RTCM 2 decoder, written by Oliver Montenbruck, German Space Operations Center, DLR, Oberpfaffenhofen, Germany</li>
    50 <li> RTCM 3 decoder for standard messages and a RTCM 3 encoder & decoder for SSR messages, both written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld, Germany</li>
    51 </ul>
    52 </p>
     50<li> RTCM 3 decoder for conventional ans MSM observation messages and a RTCM 3 encoder & decoder for SSR messages, both written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld, Germany</li>
     51</ul>
     52</p>
     53<p>
     54Note that some figures presented in this documentation show screenshots from earlier version of BNC. If so then there was no relevant change in the contents or no change at all.
    5355</p>
    5456
    5557<p>
    5658<b>Acknowledgements</b><br>
    57 Earlier versions of BNC's Help Contents have been proofread by Thomas Yan, University of New South Wales, Australia. He also provided pre-compiled builds of BNC for Mac systems.<br>
     59Earlier versions of BNC's Help Contents have been proofread by Thomas Yan, University of New South Wales, Australia. He also provides builds of BNC for Mac systems.<br>
    5860Scott Glazier, OmniSTAR Australia has been helpful in finding BNC's bugs.<br>
    5961James Perlt, BKG, helped fixing bugs and redesigned BNC's main window.<br>
    … …  
    99101<ul>
    100102<li>RTCM Version 2 message types for GPS and GLONASS observations, </li>
    101 <li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS, GLONASS, SBAS, Galileo, COMPASS and QZSS,</li>
    102 <li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS, GLONASS and Galileo,</li>
     103<li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS, GLONASS and Galileo (RTCM draft),</li>
     104<li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS and GLONASS,</li>
    103105<li>RTNET, a plain ASCII format defined within BNC to receive orbits and clock from a serving GNSS engine.
    104106</ul>
    … …  
    117119
    118120<p>
    119 Note further that BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files.
     121Note also that BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files.
    120122</p>
    121123
    … …  
    669671and hence follows UNAVCO's famous 'TEQC' program. The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License.
    670672</p>
    671 <p><img src="IMG/screenshot30.png"/></p>
    672 <p><u>Figure 7:</u>Example for satellite availability, elevation and PDOP plots.</p>
    673673
    674674<p><a name="reqcact"><h4>3.6.1 Action - optional</h4></p>
    … …  
    698698
    699699<p><img src="IMG/screenshot27.png"/></p>
    700 <p><u>Figure 8:</u> Example for 'RINEX Editing Options' window.</p>
     700<p><u>Figure 7:</u> Example for 'RINEX Editing Options' window.</p>
    701701
    702702<p><a name="reqcinput"><h4>3.6.3 Input Files - mandatory if 'Action' is set</h4></p>
    … …  
    712712
    713713<p><img src="IMG/screenshot25.png"/></p>
    714 <p><u>Figure 9:</u> Example for RINEX file editing with BNC in Post Processing mode.</p>
    715 
    716 <p>
    717 If 'Analyze' is selected, specifying a 'Log' file to output analysis results is mandatory.<br>
    718 </p>
     714<p><u>Figure 8:</u> Example for RINEX file editing with BNC in Post Processing mode.</p>
     715
     716<p>
     717If 'Analyze' is selected, specifying a 'Log' file to output analysis results is mandatory. The following is a RINEX quality check analysis logfile example:
     718<pre>
     719Analyze File
     720------------
     721File:            cut02530.12o
     722Marker name:     CUT0
     723Receiver:        TRIMBLE NETR9
     724Antenna:         TRM59800.00     SCIS
     725Start time:      2012-09-09 00:00:00.000
     726End time:        2012-09-09 23:59:30.000
     727Interval:        30
     728# Sat.:          56
     729# Obs.:          54159
     730# Slips (file):  295
     731# Slips (found): 52
     732Mean MP1:        0.25382
     733Mean MP2:        0.163092
     734Mean SNR1:       4.83739
     735Mean SNR2:       5.09455
     736</pre>
     737<p>
     738
     739<p><a name="reqcplots"><h4>3.6.5 Directory for Plots - optional if 'Action' is set</h4></p>
     740<p>
     741If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. File names will be composed from the RINEX input file name(s) plus suffix 'PNG' to indicate the plot file format in use. </p>
    719742
    720743<p><img src="IMG/screenshot29.png"/></p>
    721 <p><u>Figure 10:</u> Example for RINEX quality check output with BNC in Post Processing mode. A multipath and a signal-to-noise ratio analysis are presented in terms of a sky plot.</p>
    722 
    723 <p><a name="reqcplots"><h4>3.6.5 Directory for Plots - optional if 'Action' is set</h4></p>
    724 <p>
    725 If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. File names will be composed from the RINEX input file name(s) plus suffix 'PNG' to indicate the plot file format in use. </p>
     744<p><u>Figure 9:</u> Example for RINEX quality check graphics output with BNC. A multipath and a signal-to-noise ratio analysis are presented in terms of a sky plot.</p>
     745
     746<p><img src="IMG/screenshot30.png"/></p>
     747<p><u>Figure 10:</u> Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check with BNC.</p>
    726748
    727749<p><a name="reqccommand"><h4>3.6.6 Command Line, No Window - optional</h4></p>
    … …  
    773795<tr><td>reqcOutNavFile</td><td>RINEX Navigation output file</td></tr>
    774796<tr><td>reqcOutLogFile</td><td>Logfile</td></tr>
     797<tr><td>reqcPlotDir</td><td>Plot file directory</td></tr>
    775798<tr><td>reqcRnxVersion</td><td>RINEX version of emerging new file</td></tr>
    776799<tr><td>reqcSampling</td><td>Sampling interval of emerging new RINEX file</td></tr>
    … …  
    28232846<li>Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    28242847<li>Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
    2825 <li>Type 4021, Compact SBAS pseudo-ranges</li>
    2826 <li>Type 4022, Compact SBAS carrier phases</li>
    2827 <li>Type 4023, Compact SBAS pseudo-ranges and carrier phases</li>
    2828 <li>Type 4024, Full SBAS pseudo-ranges and carrier phases plus signal strength</li>
    2829 <li>Type 4025, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength</li>
    2830 <li>Type 4026, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    2831 <li>Type 4027, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
    2832 <li>Type 4031, Compact QZSS pseudo-ranges</li>
    2833 <li>Type 4032, Compact QZSS carrier phases</li>
    2834 <li>Type 4033, Compact QZSS pseudo-ranges and carrier phases</li>
    2835 <li>Type 4034, Full QZSS pseudo-ranges and carrier phases plus signal strength</li>
    2836 <li>Type 4035, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength</li>
    2837 <li>Type 4036, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    2838 <li>Type 4037, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)</li>
     2848<li>Type 1101, Compact SBAS pseudo-ranges</li>
     2849<li>Type 1102, Compact SBAS carrier phases</li>
     2850<li>Type 1103, Compact SBAS pseudo-ranges and carrier phases</li>
     2851<li>Type 1104, Full SBAS pseudo-ranges and carrier phases plus signal strength</li>
     2852<li>Type 1105, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength</li>
     2853<li>Type 1106, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
     2854<li>Type 1107, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
     2855<li>Type 1111, Compact QZSS pseudo-ranges</li>
     2856<li>Type 1112, Compact QZSS carrier phases</li>
     2857<li>Type 1113, Compact QZSS pseudo-ranges and carrier phases</li>
     2858<li>Type 1114, Full QZSS pseudo-ranges and carrier phases plus signal strength</li>
     2859<li>Type 1115, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength</li>
     2860<li>Type 1116, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
     2861<li>Type 1117, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br><br></li>
     2862<li>Type 1121, Compact COMPASS pseudo-ranges</li>
     2863<li>Type 1122, Compact COMPASS carrier phases</li>
     2864<li>Type 1123, Compact COMPASS pseudo-ranges and carrier phases</li>
     2865<li>Type 1124, Full COMPASS pseudo-ranges and carrier phases plus signal strength</li>
     2866<li>Type 1125, Full COMPASS pseudo-ranges, carrier phases, Doppler and signal strength</li>
     2867<li>Type 1126, Full COMPASS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
     2868<li>Type 1127, Full COMPASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)</li>
    28392869</ul>
    28402870</p>
    … …  
    28652895
    28662896<ol type=b>
     2897
    28672898<li>File 'RinexObs.bnc'<br>
    2868 The purpose of this configuration is to convert RTCM streams to RINEX Observation files. The configuration pulls streams from several NTRIP Broadcasters using different Ntrip versions and generate 15min 1Hz RINEX Version 3 Observation files. See <u>http://igs.bkg.bund.de/ntrip/observations</u> for observation stream resources.
     2899The purpose of this configuration is to convert RTCM streams to RINEX Observation files. The configuration pulls streams from several Ntrip Broadcasters using different Ntrip versions and generate 15min 1Hz RINEX Version 3 Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources.
     2900</li><br>
     2901
     2902<li>File 'RinexEph.bnc'<br>
     2903The purpose of this configuration is to convert RTCM streams to RINEX Navigation files. The configuration pulls an RTCM Version 3 stream carrying Broadcast Ephemeris coming from the real-time EUREF and IGS network. It saves hourly RINEX Version 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast Ephemeris resources.
     2904</li><br>
     2905
     2906<li>File 'SSR.bnc'<br>
     2907The purpose of this configuration is to save Broadcast Corrections from RTCM SSR messages in a plain ASCII format as hourly files. See http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF orbit/clock products. 
     2908
     2909</li><br>
     2910<li>File 'RinexConcat.bnc'<br>
     2911The purpose of this configuration is to concatenate RINEX Version 3 files to produce a concatenated file and edit the marker name in the file header. The sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks.
     2912</li><br>
     2913
     2914<li>File 'RinexQC.bnc'<br>
     2915The purpose of this configuration is to check the quality of a RINEX Version 3 file through a multipath analysis. The results is saved in disk in terms of a plot in PNG format. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks.
     2916</li><br>
     2917
     2918<li>File 'RTK.bnc'<br>
     2919The purpose of this configuration is to feed a serial connected receiver with observations from a reference station for conventional RTK. The stream is scanned for RTCM messages. Message type numbers and latencies of incoming observation are reported in BNC's logfile. 
     2920</li><br>
     2921
     2922<li>File 'FeedEngine.bnc'<br>
     2923The purpose of this configuration is to feed a real-time GNSS engine with observations from a number of remote reference stations. The configuration pulls streams provided in various formats from different Ntrip Broadcasters.  Incoming observations are decoded, synchronized and output through a local IP port and saved into a file. Failure and recovery thresholds are specified to inform about outages.
     2924</li><br>
     2925
     2926<li>File 'PPP.bnc'<br>
     2927The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a stream of Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in the logfile.
     2928</li><br>
     2929
     2930<li>File 'PPPQuickStart.bnc'<br>
     2931The purpose of this configuration is Precise Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration reads RTCM Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in NMEA format on disc.  Positions are also output through IP port for real-time visualization with tools like RTKPLOT.
     2932</li><br>
     2933
     2934<li>File 'PPPPostProc.bnc'<br>
     2935The purpose of this configuration is Precise Point Positioning in Post
     2936</li><br>
     2937Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing otions are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm.
     2938
     2939<li>File 'SPPQuickStartGal.bnc'<br>
     2940The purpose of this configuration is Single Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration uses GPS, GLONASS and Galileo observertions and a Broadcast Ephemeris stream. 
     2941</li><br>
     2942
     2943<li>File 'Sp3.bnc'<br>
     2944The purpose of this configuraiton is to produce SP3 files from a Broadcast Ephemeris stream and a Broadcast Corrections stream. Note that this requires an ANTEX file because SP3 file contents should be referred to CoM.
     2945</li><br>
     2946 
     2947<li>File 'Sp3ETRF2000PPP.bnc'<br>
     2948The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an SP3 file containing orbits referred also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows to compare an 'INTERNAL' PPP solution with ETRF2000 reference coordinates.
     2949</li><br>
     2950
     2951<li>File 'Upload.bnc'<br>
     2952The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to uploads them to an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format.
     2953</li><br>
     2954
     2955<li>File 'UploadPPP.bnc'<br>
     2956This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP soltution based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the Broadcast Corrections through observing coordinate displacements.
     2957</li><br>
     2958 
     2959<li>File 'Combi.bnc'<br>
     2960The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format.
     2961</li><br>
     2962
     2963<li>File 'CombiPPP.bnc'<br>
     2964This configuration equals the 'Combi.bnc' configuration. However, the combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements.
     2965</li><br>
     2966
     2967<li>File 'UploadEph.bnc'<br>
     2968The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds.
    28692969</li>
    2870 <br>
    2871 <li>File 'RinexEph.bnc'<br>
    2872 The purpose of this configuration is to convert RTCM streams to RINEX Navigation files. The configuration pulls an RTCM Version 3 stream carrying Broadcast Ephemeris coming from the real-time EUREF and IGS network. It saves hourly RINEX Version 3 Navigation files. See <u>http://igs.bkg.bund.de/ntrip/ephemeris</u> for further real-time Broadcast Ephemeris resources.
    2873 </li>
    2874 <br>
    2875 <li>File 'SSR.bnc'<br>
    2876 The purpose of this configuration is to save Broadcast Corrections from RTCM SSR messages in a plain ASCII format as hourly files. See <u>http://igs.bkg.bund.de/ntrip/orbits</u> for further real-time IGS or EUREF orbit/clock products.
    2877 </li>
    2878 <br>
    2879 <li>File 'RinexConcat.bnc'<br>
    2880 The purpose of this configuration is to concatenate RINEX Version 3 files to produce a concatenated file and edit the marker name in the file header. The sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks.
    2881 </li>
    2882 <br>
    2883 <li>File 'RTK.bnc'<br>
    2884 The purpose of this configuration is to feed a serial connected receiver with observations from a reference station for conventional RTK. The stream is scanned for RTCM messages. Message type numbers and latencies of incoming observation are reported in BNC's logfile.
    2885 </li>
    2886 <br>
    2887 <li>File 'FeedEngine.bnc'<br>
    2888 The purpose of this configuration is to feed a real-time GNSS engine with observations from a number of remote reference stations. The configuration pulls streams provided in various formats from different NTRIP Broadcasters. Incoming observations are decoded, synchronized and output through a local IP port and saved into a file. Failure and recovery thresholds are specified to inform about outages.
    2889 </li>
    2890 <br>
    2891 <li>File 'PPP.bnc'<br>
    2892 The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a stream of Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in the logfile.
    2893 </li>
    2894 <br>
    2895 <li>File 'QuickStartPPP.bnc'<br>
    2896 The purpose of this configuration is Precise Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration reads RTCM Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in NMEA format on disc. Positions are also output through IP port for real-time visualization with tools like RTKPLOT.
    2897 </li>
    2898 <br>
    2899 <li>File 'PPPPostProc.bnc'<br>
    2900 The purpose of this configuration is Precise Point Positioning in Post Processing mode. BNC reads a RINEX Observation and a RINEX  Version 3 Navigation files and a Broadcast Corrections files. PPP processing options are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm.
    2901 </li>
    2902 <br>
    2903 <li>File 'SPPQuickStartGal.bnc'<br>
    2904 The purpose of this configuration is Single Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration uses GPS, GLONASS and Galileo observations and a Broadcast Ephemeris stream.
    2905 </li>
    2906 <br>
    2907 <li>File 'Sp3.bnc'<br>
    2908 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a Broadcast Corrections stream. Note that this requires an ANTEX file because SP3 file contents should be referred to CoM.
    2909 </li>
    2910 <br>
    2911 <li>File 'Sp3ETRF2000PPP.bnc'<br>
    2912 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an SP3 file containing orbits referred also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows to compare an 'INTERNAL' PPP solution with ETRF2000 reference coordinates.
    2913 </li>
    2914 <br>
    2915 <li>File 'Upload.bnc'<br>
    2916 The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to uploads them to an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format.
    2917 </li>
    2918 <br>
    2919 <li>File 'UploadPPP.bnc'<br>
    2920 This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution based on observations from a static reference station with known precise coordinates.  This allows a continuous quality check of the Broadcast Corrections through observing coordinate displacements.
    2921 </li>
    2922 <br>
    2923 <li>File 'Combi.bnc'<br>
    2924 The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an NTRIP Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format.
    2925 </li>
    2926 <br>
    2927 <li>File 'CombiPPP.bnc'<br>
    2928 This configuration equals the 'Combi.bnc' configuration. However, the combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements.
    2929 </li>
    2930 <br>
    2931 <li>File 'UploadEph.bnc'<br>
    2932 The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds.
    2933 </li>
     2970
    29342971</ol>
    29352972</p>
    … …  
    30433080<tr><td>reqcPlotDir</td><td>Reqc: QC plots directory</td></tr>
    30443081<tr><td>reqcOutLogFile=</td><td>Reqc: Output logfile</td></tr>
     3082<tr><td>reqcPlotDir=</td><td>Reqc: Plot file directory</td></tr>
    30453083<tr><td>reqcRnxVersion=</td><td>Reqc: RINEX version</td></tr>
    30463084<tr><td>reqcSampling=</td><td>Reqc: RINEX sampling</td></tr>
Note: See TracChangeset for help on using the changeset viewer.