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


Ignore:
Timestamp:
Mar 11, 2008, 10:06:25 AM (16 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r721 r723  
    8484&nbsp; &nbsp; &nbsp; 3.8.2. <a href=#advfail>Failure Threshold</a><br>
    8585&nbsp; &nbsp; &nbsp; 3.8.3. <a href=#advreco>Recovery Threshold</a><br>
    86 &nbsp; &nbsp; &nbsp; 3.8.4. <a href=#advscript>Advisory Script</a><br>
    87 &nbsp; &nbsp; &nbsp; 3.8.5. <a href=#latelog>Latency Logging</a><br>
     86&nbsp; &nbsp; &nbsp; 3.8.4. <a href=#pause>Pause</a><br>
     87&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>
    88893.9. <a href=#mountpoints>Mountpoints</a><br>
    8990&nbsp; &nbsp; &nbsp; 3.9.1. <a href=#mountadd>Add Mountpoints</a><br>
     
    383384</p>
    384385<p>
    385 <u>Stream corruption:</u> Not all bits chunk transfers to BNC's internal decoders return valid observations. Sometimes several chunks might be needed before the next observation can be properly decoded. BNC buffers all the outputs (both valid and invalid) from the decoder for a short time span (size derived from the expected 'Observation rate') and then determines whether a stream is valid or corrupted. In case of a corrupted stream, the decoding process is paused and decodings are then attempted again at decreasing rate. BNC will first attempt to decode again after a 30 second lag and if unsuccessful, make another attempt within 60 seconds after the previous attempt. If it is still unsuccessful, it will make another attempt to decode within 120 seconds after the previous attempt and so on. Each decoding attempt doubles the wait time since the previous attempt. The maximum wait time between attempts is limited to 960 seconds.
     386<u>Stream corruption:</u> Not all bits chunk transfers to BNC's internal decoders return valid observations. Sometimes several chunks might be needed before the next observation can be properly decoded. BNC buffers all the outputs (both valid and invalid) from the decoder for a short time span (size derived from the expected 'Observation rate') and then determines whether a stream is valid or corrupted.
    386387</p>
    387388<p>
     
    410411</p>
    411412
    412 <p><a name="advscript"><h4>3.8.4 Advisory Script - optional </h4></p>
     413<p><a name="pause"><h4>3.8.4 Pause - optional</h4></p>
     414<p>
     415In case of a corrupted stream, the decoding process can be paused and decodings are then attempted again at decreasing rate. BNC will first attempt to decode again after a 30 second lag and if unsuccessful, make another attempt within 60 seconds after the previous attempt. If it is still unsuccessful, it will make another attempt to decode within 120 seconds after the previous attempt and so on. Each decoding attempt doubles the wait time since the previous attempt. The maximum wait time between attempts is limited to 960 seconds. Tick 'Pause' to activate this function. Note that it is only effective if an 'Observation rate' is specified.
     416</p>
     417<p>
     418Do not tick 'Pause' if you want to prevent BNC from making any decoding pause. Be aware that this may incur an unnecessary workload.
     419</p>
     420
     421<p><a name="advscript"><h4>3.8.5 Advisory Script - optional </h4></p>
    413422<p>
    414423As mentioned previously, BNC can trigger a shell script or a batch file to be executed when one of the events described are reported. This script can be used to email an advisory note to network operator or stream providers. To enable this feature, specify the full path to the script or batch file in the 'Script' field. The affected mountpoint and type of event reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script as command line parameters (%1 and %2 on Windows systems or $1 and $2 on Unix/Linux systems) together with date and time information.
     
    439448</p>
    440449
    441 <p><a name="latelog"><h4>3.8.5 Latency Logging - optional </h4></p>
     450<p><a name="latelog"><h4>3.8.6 Latency Logging - optional </h4></p>
    442451<p>
    443452Latency is defined here by the following equation:
     
    811820latIntr=
    812821logFile=/home/user/log.txt
     822makePause=0
    813823mountPoints=//user:pass@www.euref-ip.net:2101/ACOR0 RTCM_2.3 43.36 351.60 no, //user:pass@www.igs-ip.net:2101/FFMJ3 RTCM_3.0 41.58 1.40 no
    814824obsRate=
Note: See TracChangeset for help on using the changeset viewer.