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


Ignore:
Timestamp:
Mar 14, 2008, 4:01:49 PM (16 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r726 r728  
    8686&nbsp; &nbsp; &nbsp; 3.8.4. <a href=#pause>Pause</a><br>
    8787&nbsp; &nbsp; &nbsp; 3.8.5. <a href=#advscript>Advisory Script</a><br>
    88 &nbsp; &nbsp; &nbsp; 3.8.6. <a href=#latelog>Latency Logging</a><br>
     88&nbsp; &nbsp; &nbsp; 3.8.6. <a href=#perflog>Performance Logging</a><br>
    89893.9. <a href=#mountpoints>Mountpoints</a><br>
    9090&nbsp; &nbsp; &nbsp; 3.9.1. <a href=#mountadd>Add Mountpoints</a><br>
     
    448448</p>
    449449
    450 <p><a name="latelog"><h4>3.8.6 Latency Logging - optional </h4></p>
    451 <p>
    452 Latency is defined here by the following equation:
     450<p><a name="perflog"><h4>3.8.6 Performance Logging - optional </h4></p>
     451<p>
     452<u>Latency:</u> Latency is defined in BNC by the following equation:
    453453</p>
    454454<pre>
     
    459459  = Latency
    460460</pre>
    461 <p>BNC can average the latencies per stream over a certain period of GPS time. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation per second. Mean latencies are recorded in the Log file/section at the end of each 'Latency logging' interval. Select a 'Latency logging' interval or select the empty option field if you do not want BNC to log latency information. Note that computing correct latencies requires the clock of the host computer to be properly synchronized.
     461<p>
     462 BNC can average the latencies per stream over a certain period of GPS time, the 'Performance logging' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation per second. Note that computing correct latencies requires the clock of the host computer to be properly synchronized.
     463</p>
     464<p>
     465<u>Statistics:</u> BNC counts the number of GPS seconds covered by at least one observation. It also estimates an observation rate from all observations received throughout the first full 'Performance logging' interval. Based on this rate, BNC estimates the number of data gaps when appearing in subsequent intervals.
     466</p>
     467<p>
     468Latencies and statistical information can be recorded in the Log file/section at the end of each 'Performance logging' interval. Select a 'Performance logging' interval to activate this function or select the empty option field if you do not want BNC to log latencies and statistical information.
    462469</p>
    463470
Note: See TracChangeset for help on using the changeset viewer.