Valerii Zapodovnikov

> .. It is calculated against successful decodes instead of total words processed. Yep, against words_decode. Still, 121 out of (3547+121+444) is a lot. Is there any one with C_1...

>I have not tested for that specific case . That is the question though. Arguably you may want to correct parity bit in this case, but it depends whether there...

BTW, are those ephemeris better than what is available through Google SUPL? Higher precision? For RTK one needs ephemeris that are real, not predicted (as in SUPL or these), so...

> For RTK it is always better to setup a base station That is DGNSS (or even more cool WAAS, e.g., that uses a separate satellite, PRN == 131 and...

``` diff --git a/src/core/system_parameters/glonass_gnav_navigation_message.cc b/src/core/system_parameters/glonass_gnav_navigation_message.cc index 5b02162a6..e1391d1d5 100644 --- a/src/core/system_parameters/glonass_gnav_navigation_message.cc +++ b/src/core/system_parameters/glonass_gnav_navigation_message.cc @@ -14[8](https://github.com/gnss-sdr/gnss-sdr/actions/runs/3036341256/jobs/4887523145#step:6:9),8 +148,[9](https://github.com/gnss-sdr/gnss-sdr/actions/runs/3036341256/jobs/4887523145#step:6:10) @@ bool Glonass_Gnav_Navigation_Message::hamming_correct(std::bitset

> requires so much RAM/storage to compile? Cause C++. Simple.

> That's not a very helpful answer. True though. One removal of std::string: https://github.com/bastibl/gr-rds/pull/30

>Sure, the memory footprint of 1280x4x(sizeof(char const*)) is less than 1280x4x(sizeof(std::string)), Can you say 100% that something like this does not exist in this codebase? Even simple printf() that is...

> there is workaround available - they decode just fine once you correct the StripByteCounts on these 0.3%. Can you please attach corrected in hex editor file? Just for posterity....

Yep, that one does work without any warnings.