Changeset 2947 in ntrip for trunk/BNC/bnchelp.html


Ignore:
Timestamp:
Feb 2, 2011, 12:08:48 PM (14 years ago)
Author:
weber
Message:

PPP section updated

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r2863 r2947  
    182182&nbsp; &nbsp; &nbsp; 3.11.2.3 <a href=#pppglo>Use GLONASS</a><br>
    183183&nbsp; &nbsp; &nbsp; 3.11.2.4 <a href=#pppgal>Use Galileo</a><br>
    184 &nbsp; &nbsp; &nbsp; 3.11.3 <a href=#pppoptcont>Options cont'd</a><br>
    185 &nbsp; &nbsp; &nbsp; 3.11.3.1 <a href=#pppsigcp>Sigma Code/Phase</a><br>
    186 &nbsp; &nbsp; &nbsp; 3.11.3.2 <a href=#pppquick>Quick-Start</a><br>
    187 &nbsp; &nbsp; &nbsp; 3.11.3.3 <a href=#pppaverage>Averaging</a><br>
    188 &nbsp; &nbsp; &nbsp; 3.11.4 <a href=#pppparasig>Parameter Sigmas</a><br>
    189 &nbsp; &nbsp; &nbsp; 3.11.4.1 <a href=#pppsigxyzi>XYZ Init</a><br>
    190 &nbsp; &nbsp; &nbsp; 3.11.4.2 <a href=#pppsigxyzn>XYZ White Noise</a><br>
    191 &nbsp; &nbsp; &nbsp; 3.11.4.3 <a href=#pppsigtrpi>Tropo Init</a><br>
    192 &nbsp; &nbsp; &nbsp; 3.11.4.4 <a href=#pppsigtrpn>Tropo White Noise</a><br>
    193 &nbsp; &nbsp; &nbsp; 3.11.5 <a href=#pppout>Output</a><br>
    194 &nbsp; &nbsp; &nbsp; 3.11.5.1 <a href=#pppnmeafile>NMEA File</a><br>
    195 &nbsp; &nbsp; &nbsp; 3.11.5.2 <a href=#pppnmeaport>NMEA Port</a><br>
    196 &nbsp; &nbsp; &nbsp; 3.11.5.3 <a href=#pppplot>PPP Plot</a><br>
    197 &nbsp; &nbsp; &nbsp; 3.11.6 <a href=#pppsync>Sync Corr</a><br><br>
     184&nbsp; &nbsp; &nbsp; 3.11.3 <a href=#pppoptcont1>Options cont'd</a><br>
     185&nbsp; &nbsp; &nbsp; 3.11.3.1 <a href=#pppsigxyzi>XYZ Init</a><br>
     186&nbsp; &nbsp; &nbsp; 3.11.3.2 <a href=#pppsigxyzn>XYZ White Noise</a><br>
     187&nbsp; &nbsp; &nbsp; 3.11.3.3 <a href=#pppquick>Quick-Start</a><br>
     188&nbsp; &nbsp; &nbsp; 3.11.3.4 <a href=#pppplot>PPP Plot</a><br>
     189&nbsp; &nbsp; &nbsp; 3.11.4 <a href=#pppnmea>NMEA</a><br>
     190&nbsp; &nbsp; &nbsp; 3.11.4.1 <a href=#pppnmeafile>NMEA File</a><br>
     191&nbsp; &nbsp; &nbsp; 3.11.4.2 <a href=#pppnmeaport>NMEA Port</a><br>
     192&nbsp; &nbsp; &nbsp; 3.11.5 <a href=#ppprecant>Receiver Antenna</a><br>
     193&nbsp; &nbsp; &nbsp; 3.11.5.1 <a href=#pppantex>ANTEX File</a><br>
     194&nbsp; &nbsp; &nbsp; 3.11.5.2 <a href=#ppprecantenna>Antenna Name</a><br>
     195&nbsp; &nbsp; &nbsp; 3.11.6 <a href=#pppsatant>Satellite Antenna</a><br>
     196&nbsp; &nbsp; &nbsp; 3.11.6.1 <a href=#pppsatantignore>Ignore Offsets</a><br>
     197&nbsp; &nbsp; &nbsp; 3.11.7 <a href=#pppsigmas>Sigmas</a><br>
     198&nbsp; &nbsp; &nbsp; 3.11.7.1 <a href=#pppsigc>Code</a><br>
     199&nbsp; &nbsp; &nbsp; 3.11.7.2 <a href=#pppsigp>Phase</a><br>
     200&nbsp; &nbsp; &nbsp; 3.11.7.3 <a href=#pppsigtrpi>Tropo Init</a><br>
     201&nbsp; &nbsp; &nbsp; 3.11.7.4 <a href=#pppsigtrpn>Tropo White Noise</a><br>
     202&nbsp; &nbsp; &nbsp; 3.11.8 <a href=#pppoptcont2>Options cont'd</a><br>
     203&nbsp; &nbsp; &nbsp; 3.11.8.1 <a href=#pppsync>Sync Corr</a><br>
     204&nbsp; &nbsp; &nbsp; 3.11.8.2 <a href=#pppaverage>Averaging</a><br><br>
    1982053.12. <a href=#streams>Streams</a><br>
    199206&nbsp; &nbsp; &nbsp; 3.12.1 <a href=#streamedit>Edit Streams</a><br>
    200207&nbsp; &nbsp; &nbsp; 3.12.2 <a href=#streamdelete>Delete Stream</a><br>
    201208&nbsp; &nbsp; &nbsp; 3.12.3 <a href=#streamconf>Reconfigure Streams On-the-fly</a><br><br>
    202 3.13. <a href=#logs>Logging</a><br>
     2093.13. <a href=#logs>Logging</a><br><br>
    203210&nbsp; &nbsp; &nbsp; 3.13.1 <a href=#logfile>Log</a><br>
    204211&nbsp; &nbsp; &nbsp; 3.13.2 <a href=#throughput>Throughput</a><br>
    … …  
    11221129<ul>
    11231130<li>BNC does correct for Solid Earth Tides and Phase Windup.</li>
    1124 <li>Satellite Antenna Offsets are not corrected because applied orbit/clock correctors are referred to the satellite's antenna phase center.</li>
    1125 <li>Satellite Antenna Offset Variations are neglected because this is a small effect usually less than 2 centimeters.</li>
    1126 <li>Receiver Antenna Offsets are not corrected which means that the estimated position is that of the receiver's antenna phase center and not that of the receiver's Antenna Reference Point.</li>
     1131<li>Satellite Antenna Phase Center Offsets are not corrected because applied orbit/clock correctors are referred to the satellite's antenna phase center.</li>
     1132<li>Satellite Antenna Phase Center Variations are neglected because this is a small effect usually less than 2 centimeters.</li>
     1133<li>Observations can be corrected for a Receiver Antenna Offset. Depending on whether or not this correction is applied, the estimated position is either that of the receiver's antenna phase center or that of the receiver's Antenna Reference Point.</li>
    11271134<li>Receiver Antenna Phase Center Variations are not included in the model. The bias caused by this neglect depends on the receiver antenna type. For most antennas it is smaller than a few centimeters.</li>
    11281135<li>Ocean and atmospheric loading is neglected. Atmospheric loading is pretty small. Ocean loading is usually also a small effect but may reach up to about 10 centimeters for coastal stations.</li>
    … …  
    11881195</p>
    11891196
    1190 <p><a name="pppoptcont"><h4>3.11.3 Options cont'd</h4></p>
    1191 <p>
    1192 You may want to introduce specific sigmas for code and phase observations. You may also like to carry out your PPP solution in Quick-Start mode or output averaged position values.
    1193 </p>
    1194 
    1195 <p><a name="pppsigcp"><h4>3.11.3.1 Sigma Code/Phase - mandatory if 'Use Phase Obs' is set</h4></p>
    1196 <p>
    1197 When 'Use phase obs' is set in BNC the PPP solution will be carried out using both, code and phase observations. A sigma of 5.0 m for code observations and a sigma of 0.02 m for phase observations (defauls) is used to combine both types of observations.
    1198 As the convergence characteristic of a PPP solution can be influenced by the ratio of the sigmas for code and phase, you may like to introduce you own sigmas for code and phase observations which differ from the default of 5.0 m and 0.02 m respectively.
     1197<p><a name="pppoptcont1"><h4>3.11.3 Options cont'd</h4></p>
     1198<p>
     1199You may want to introduce specific sigmas for code and phase observations. You may also like to carry out your PPP solution in Quick-Start mode or output a time series of displacement compoments.
     1200</p>
     1201
     1202<p><a name="pppsigxyzi"><h4>3.11.3.1 XYZ Init - mandatory</h4></p>
     1203<p>
     1204Enter a sigma in meters for the initial XYZ coordinate componentes. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode.
     1205</p>
     1206
     1207<p><a name="pppsigxyzn"><h4>3.11.3.2 XYZ White Noise - mandatory</h4></p>
     1208<p>
     1209Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate considering the potential movement of a rover.
     1210</p>
     1211
     1212<p><a name="pppquick"><h4>3.11.3.3 Quick-Start - optional if XYZ is set</h4></p>
     1213<p>
     1214Enter the lenght of a startup period in seconds for which you want to fix the PPP solution to a known XYZ coordinate. Constraining coordinate components is done in BNC through setting the 'XYZ White Noise' temporarily to zero.
     1215</p>
     1216<p>
     1217This so-called Quick-Start option allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the know position throughout the defined period. A value of 120 (default) is likely to be an appropriate choice for 'Quick-Start'
     1218<p>
     1219You may need to create your own reference coordinate through running BNC for an hour in normal mode before applying the Quick-Start option. Don't forget to introduce a realistic sigma 'XYZ Ini' according to the coordinate's precision.
     1220</p>
     1221
     1222<p><img src=":bnchelp/screenshot17.png"/></p>
     1223<p><u>Figure:</u> BNC in 'Quick-Start' mode</p>
     1224
     1225<p><a name="pppplot"><h4>3.11.3.4 PPP Plot - optional</h4></p>
     1226<p>
     1227PPP time series of North (red), East(green) and Up (blue) coordinate components will be plotted in the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes.
     1228</p>
     1229<p>
     1230Note that a PPP time series makes only sense for a stationary operated receiver.
     1231</p>
     1232
     1233<p><a name="pppnmea"><h4>3.11.4 NMEA - optional</h4></p>
     1234<p>
     1235BNC allows to output results from Precise Point Positioning in NMEA format.
     1236</p>
     1237
     1238<p><a name="pppnmeafile"><h4>3.11.4.1 NMEA File - optional</h4></p>
     1239<p>
     1240The NMEA sentences generated about once per second are pairs of
     1241<ul>
     1242<li> GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus</li>
     1243<li> GPRMC sentences which mainly carry date and time information.</li>
     1244</ul>
     1245</p>
     1246<p>
     1247Specify the full path to a file where Point Positioning results are saved as NMEA messages. The default value for 'NMEA file' is an empty option field, meaning that BNC will not saved NMEA messages into a file.
     1248</p>
     1249<p>
     1250Note that Tomoji Takasu has written a Windows program called RTKPlot for visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA output of BNC's 'PPP Client' option.
     1251</p>
     1252
     1253<p><a name="pppnmeaport"><h4>3.11.4.2 NMEA Port - optional</h4></p>
     1254<p>
     1255Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same.
     1256</p>
     1257<p>
     1258NASA's 'World Wind' software (see <u>http://worldwindcentral.com/wiki/NASA_World_Wind_Download</u>) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from <u>http://worldwindcentral.com/wiki/GPS_Tracker</u> for that. The 'Word Wind' is not meant for showing centimeter level details.
     1259</p>
     1260
     1261<p><a name="ppprecant"><h4>3.11.5 Receiver Antenna - optional</h4></p>
     1262<p>
     1263BNC allows to correct observations for receiver antenna phase center offsets and variations.
     1264</p>
     1265
     1266<p><a name="pppantex"><h4>3.11.5.1 ANTEX File - optional</h4></p>
     1267<p>
     1268IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required for correcting observations for antenna phase center offsets and variations. It allows you to specify the name of your receiver's antenna (as contained in the ANTEX file) to apply such corrections.
     1269</p>
     1270<p>
     1271Default is an empty option field meaning that you don't want to correct observations for antenna phase center offsets and variations.
     1272</p>
     1273
     1274<p><a name="ppprecantenna"><h4>3.11.5.2 Antenna Name - optional if 'ANTEX File' is set</h4></p>
     1275<p>
     1276Specify the receiver's antenna name as defined in your ANTEX file.Observations will be corrected for the antenna phase center's offset which may result in a reduction of a few centimeters at max. Phase center variations are not yet applied by BNC.
     1277</p>
     1278<p>
     1279Default is an empty option field meaning that you don't want to correct observations for antenna phase center offsets.
     1280</p>
     1281
     1282<p><a name="pppsatant"><h4>3.11.6 Satellite Antenna - optional</h4></p>
     1283<p>
     1284BNC allows to correct observations for satellite antenna phase center offsets.
     1285</p>
     1286
     1287<p><a name="pppsatantapply"><h4>3.11.6.1 Apply Offsets - optional if 'ANTEX File' is set</h4></p>
     1288<p>
     1289Satellite orbit and clock corrections refer to the satellite's antenna phase centers and hence observations are <u>not</u> to be corrected for satellite antenna phase center offsets. Tick 'Ignore Offsets' to force BNC to not correct observations for satellite antenna phase center offsets. So far satellite antenna phase center variations remain unconsidered in BNC.
     1290</p>
     1291<p>
     1292Default is to <u>not</u> correct observations for satellite antenna phase center offsets.
     1293</p>
     1294
     1295<p><a name="pppsigmas"><h4>3.11.7 Parameter Sigmas</h4></p>
     1296<p>
     1297You may like to introduce specific sigmas for code and phase observations and for the estimation of troposphere parameters.
     1298</p>
     1299
     1300<p><a name="pppsigc"><h4>3.11.7.1 Code - mandatory if 'Use Phase Obs' is set</h4></p>
     1301<p>
     1302When 'Use phase obs' is set in BNC, the PPP solution will be carried out using both, code and phase observations. A sigma of 5.0 m for code observations and a sigma of 0.02 m for phase observations (defauls) is used to combine both types of observations. As the convergence characteristic of a PPP solution can be influenced by the ratio of the sigmas for code and phase, you may like to introduce you own sigmas for code and phase observations which differ from the default values.
    11991303<ul>
    12001304<li>Introducing a smaller sigma (higher accuracy) for code observations or a larger sigma for phase observations leads to better results shortly after program start. However, it may take more time till you finally get the best possible solutions.</li>
    … …  
    12021306</ul>
    12031307</p>
    1204 
    1205 <p><a name="pppquick"><h4>3.11.3.2 Quick-Start - optional if XYZ is set</h4></p>
    1206 <p>
    1207 Enter the lenght of a startup period in seconds for which you want to fix the PPP solution to a known XYZ coordinate. Constraining coordinate components is done in BNC through setting the 'XYZ White Noise' temporarily to zero.
    1208 </p>
    1209 <p>
    1210 This so-called Quick-Start option allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the know position throughout the defined period. A value of 120 (default) is likely to be an appropriate choice for 'Quick-Start'
    1211 <p>
    1212 You may need to create your own reference coordinate through running BNC for an hour in normal mode before applying the Quick-Start option. Don't forget to introduce a realistic sigma 'XYZ Ini' according to the coordinate's precision.
    1213 </p>
    1214 
    1215 <p><img src=":bnchelp/screenshot17.png"/></p>
    1216 <p><u>Figure:</u> BNC in 'Quick-Start' mode</p>
    1217 
    1218 <p><a name="pppaverage"><h4>3.11.3.3 Averaging - optional if XYZ is set</h4></p>
     1308<p>
     1309Specify a sigma for code observations. Default is 5.0 m.
     1310</p>
     1311
     1312<p><a name="pppsigp"><h4>3.11.7.2 Phase - mandatory if 'Use Phase Obs' is set</h4></p>
     1313<p>
     1314Specify a sigma for phase observations. Default is 0.02 m.
     1315</p>
     1316
     1317<p><a name="pppsigtrpi"><h4>3.11.7.3 Tropo Init - mandatory if 'Estimate tropo' is set</h4></p>
     1318<p>
     1319Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice.
     1320</p>
     1321
     1322<p><a name="pppsigtrpn"><h4>3.11.7.4 Tropo White Noise - mandatory if 'Estimate tropo' is set</h4></p>
     1323<p>
     1324Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 1e-6 (default) would mean that the tropospheric effect may vary for 3600 * 1e-6 = 0.0036 meters per hour.
     1325</p>
     1326
     1327<p><a name="pppoptcont2"><h4>3.11.8 Options cont'd - optional</h4></p>
     1328<p>
     1329You may like to introduce sigmas for code and phase observations and the estimation of troposphere parameters.
     1330</p>
     1331
     1332<p><a name="pppsync"><h4>3.11.8.1 Sync Corr - optional</h4></p>
     1333<p>
     1334Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'Sync Corr' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'Sync Corr' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of the update rate.
     1335</p>
     1336<p>
     1337Using observations in sync with the corrections can avoid a possible high frequency noise of PPP solutions. Such noise could result from processing observations regardless of how late after a clock correction they were received. Note that applying the 'Sync Corr' option significantly reduces the PPP computation effort for BNC.
     1338</p>
     1339<p>
     1340Default is an empty option field, meaning that you want BNC to process observations immediately after their arrival through applying the latest received clock correction.
     1341</p>
     1342
     1343<p><a name="pppaverage"><h4>3.11.8.2 Averaging - optional if XYZ is set</h4></p>
    12191344<p>
    12201345Enter the length of a sliding time window in minutes. BNC will continuously output moving average values ns and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenit path delays are bias reduced while RMS values for Nort/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string &quot;AVE-XYZ&quot; in BNC's log file and 'Log' section while averaged values for NEU displacements and their RMS are marked with string &quot;AVE-NEU&quot; and averaged values for the tropospheric delays and their RMS are marked with string &quot;AVE-TRP&quot;. Example:
    … …  
    12271352<p>
    12281353Entering any positive value up to 1440 (24h mean value) is allowed. An empty option field (default) means that you don't want BNC to output moving average positions into the log file and the 'Log' section. Note that averaging positions makes only sense for a stationary receiver.
    1229 </p>
    1230 
    1231 <p><a name="pppparasig"><h4>3.11.4 Parameter Sigmas</h4></p>
    1232 <p>
    1233 You may like to introduce specific estimates for sigmas of parameters to be estimated in the PPP solution.
    1234 </p>
    1235 
    1236 <p><a name="pppsigxyzi"><h4>3.11.4.1 XYZ Init - mandatory</h4></p>
    1237 <p>
    1238 Enter a sigma in meters for the initial XYZ coordinate componentes. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode.
    1239 </p>
    1240 
    1241 <p><a name="pppsigxyzn"><h4>3.11.4.2 XYZ White Noise - mandatory</h4></p>
    1242 <p>
    1243 Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate considering the potential movement of a rover.
    1244 </p>
    1245 
    1246 <p><a name="pppsigtrpi"><h4>3.11.4.3 Tropo Init - mandatory if 'Estimate tropo' is set</h4></p>
    1247 <p>
    1248 Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice.
    1249 </p>
    1250 
    1251 <p><a name="pppsigtrpn"><h4>3.11.4.4 Tropo White Noise - mandatory if 'Estimate tropo' is set</h4></p>
    1252 <p>
    1253 Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 1e-6 (default) would mean that the tropospheric effect may vary for 3600 * 1e-6 = 0.0036 meters per hour.
    1254 </p>
    1255 
    1256 <p><a name="pppout"><h4>3.11.5 Output - optional</h4></p>
    1257 <p>
    1258 BNC allows to output results from Precise Point Positioning in NMEA format or as a time series plot of displacements.
    1259 </p>
    1260 
    1261 <p><a name="pppnmeafile"><h4>3.11.5.1 NMEA File - optional</h4></p>
    1262 <p>
    1263 The NMEA sentences generated about once per second are pairs of
    1264 <ul>
    1265 <li> GPGGA sentences which mainly carry the estimated latitude, longitude, and height values, plus</li>
    1266 <li> GPRMC sentences which mainly carry date and time information.</li>
    1267 </ul>
    1268 </p>
    1269 <p>
    1270 Specify the full path to a file where Point Positioning results are saved as NMEA messages. The default value for 'NMEA file' is an empty option field, meaning that BNC will not saved NMEA messages into a file.
    1271 </p>
    1272 <p>
    1273 Note that Tomoji Takasu has written a Windows program called RTKPlot for visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA output of BNC's 'PPP Client' option.
    1274 </p>
    1275 
    1276 <p><a name="pppnmeaport"><h4>3.11.5.2 NMEA Port - optional</h4></p>
    1277 <p>
    1278 Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same.
    1279 </p>
    1280 <p>
    1281 NASA's 'World Wind' software (see <u>http://worldwindcentral.com/wiki/NASA_World_Wind_Download</u>) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from <u>http://worldwindcentral.com/wiki/GPS_Tracker</u> for that. The 'Word Wind' is not meant for showing centimeter level details.
    1282 </p>
    1283 
    1284 <p><a name="pppplot"><h4>3.11.5.3 PPP Plot - optional</h4></p>
    1285 <p>
    1286 PPP time series of North (red), East(green) and Up (blue) coordinate components will be plotted in the 'PPP Plot' tab when this option ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes.
    1287 </p>
    1288 <p>
    1289 Note that a PPP time series makes only sense for a stationary operated receiver.
    1290 </p>
    1291 
    1292 
    1293 <p><a name="pppsync"><h4>3.11.6 Sync Corr - optional</h4></p>
    1294 <p>
    1295 Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'pppSync' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'pppSync' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of the update rate.
    1296 </p>
    1297 <p>
    1298 Using observations in sync with the corrections can avoid a possible high frequency noise of PPP solutions. Such noise could result from processing observations regardless of how late after a clock correction they were received. Note that applying the 'Sync Corr' option significantly reduces the PPP computation effort for BNC.
    1299 </p>
    1300 <p>
    1301 Default is an empty option field, meaning that you want BNC to process observations immediately after their arrival through applying the latest received clock correction.
    13021354</p>
    13031355
Note: See TracChangeset for help on using the changeset viewer.