Changeset 2821 in ntrip
- Timestamp:
- Dec 19, 2010, 8:24:50 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
TabularUnified trunk/BNC/bnchelp.html ΒΆ
r2820 r2821 1277 1277 <p><a name="pppsync"><h4>3.11.6 Sync Corr - optional</h4></p> 1278 1278 <p> 1279 Zero value (or empty field) means that BNC processes each epoch of data 1280 immediately after its arrival using satellite clock corrections available at 1281 that time. Non-zero value "pppSync" means that the epochs of data are buffered 1282 and the processing of each epoch is postponed till the satellite clock 1283 corrections not older than "pppSync" are available. 1284 <p> 1285 </p> 1286 Using only observations which come in sync with the corrections can avoid a possible high frequency noise of PPP solutions. Such noise could result from processing all observations regardless of how late after a clock correction they were received. 1287 </p> 1288 <p> 1289 Default is an empty option field, meaning that you want BNC to determine a PPP solution from all incoming observations through applying the latest received clock correction. 1279 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. 1280 </p> 1281 <p> 1282 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. 1283 </p> 1284 <p> 1285 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. 1290 1286 </p> 1291 1287
Note:
See TracChangeset
for help on using the changeset viewer.