Changeset 2628 in ntrip


Ignore:
Timestamp:
Oct 28, 2010, 11:48:54 AM (14 years ago)
Author:
weber
Message:

Improve BNC's convergence behaviour?

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/todo.txt

    r2627 r2628  
    2727age of RTCM SSR data should be put.
    2828
    29 (2) BNC has a problem when the observation update rate is > 1Hz. Records get
     29(2) Should we spend time to improve BNC's convergence? Should we follow a
     30procedure like the one Oscar implemented? If not: Can we do something which
     31helps a bit and does not involve too much work?
     32
     33(a) Calculate, for each satellite, the STD of the code multipath in the
     34iono-free combination Pc, as a combination the carrier phase and the code.
     35Do this continuously, using a circular register that contains the observations
     36of the previous 10 minutes.
     37(b) Introduce a default STD that is used when, either at the beginning or
     38after an interruption in the data, there is less than 10 minutes worth of
     39data for finding the multipath STD as in (1), and the STD with insufficient
     40data is less than this default.
     41(c) Introduce use a "fudge factor" to multiply the data-based STD and get the
     42actual value used to get the data. This is necessary, because the correct weight
     43of the data depends on numerous factors, particularly the weights assigned to
     44the phase and to the a priori values of the unknowns. This problem also is true
     45for (b), (c), and (d). So the fudge factor really depends on the overall strategy
     46and cannot be used in different software implementations.
     47Everyone has to find it the hard way, by trial and error, making lots of solutions.
     48(The variance of unit weight is of very limited help for this purpose.)
     49(d) Downweight the code by a large factor when a satellite is below 20 degrees
     50in elevation, or the 3-D precision of the coordinates being estimated falls
     51below something like 25 cm (again, this will be a different threshold with
     52different software).
     53
     54(3) BNC has a problem when the observation update rate is > 1Hz. Records get
    3055mixed then in the RINEX files. A 10 Hz stream to test the situation is
    3156available from GFZ caster 139.17.3.112:4080 through stream A17H.
    3257
    33 (3) GW: Keep an eye on www.igs-ip.net/PENC0.
     58(4) GW: Keep an eye on www.igs-ip.net/PENC0.
    3459
Note: See TracChangeset for help on using the changeset viewer.