Custom Query (104 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 104)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1 fixed Error message "Wrong observation epoch(s)" weber weber
Description We continuously pull about 50 streams with BNC to feed an RTNet installation. A regular phenomen we see is lots of error messages "Wrong observation epoch(s)" in the logfile associated with a few streams like LPG20, MAL20, and RCMN0 coming from www.igs-ip.net. It ends up with daily logfiles of 300 to 400 MByte size. The error message is generated in bncgetthread.cpp around line 475. Once BNC is restarted, the error messages disappear for some time. My feeling is that following a time tag problem in the incoming stream, BNC gets into the stage (week != obs->_o.GPSWeek
dt > maxDt) which continuously generates the error messages and cannot be left. Examples for logfiles containing many of the error messages described above are to be found in our LAN on host "gref-ip" in directory /home/weber/bnc-call/bnc_server.
#2 fixed Ntrip-caster crash with segmentation fault: doublicate entry in sourcemounts.aut stoecker stoecker
Description

When the sourcemounts.aut contains a duplicate entry, then caster detects this, but later crashs with segfault.

Example data stored in igs-ip.net directory on friedrich.

#3 fixed Duplicate data records in generated RINEX files stoecker johansen
Description

When the RTCM data contains GPS and Glonass data, data records are output both when receiving the 1004 GPS message and the 1012 Glonass message. Observed in NO_RTCM3_MAIN mode with RINEX v. 2.

A patch is attached to output a data record only after receiving the last RTCM message for an epoch.

1 2 3 4 5 6 7 8 9 10 11
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.