Carles Fernandez

You can test if gnss-sdr is alive with: ``` $ gnss-sdr --version ``` But I guess this is not working. I don't know how you have built the binary, but...

Maybe something like this: ``` std::array dims_input{d_input_signal.size(), 1}; matvar = Mat_VarCreate("input_signal", MAT_C_DOUBLE, MAT_T_DOUBLE, 1, dims_input.data(), d_input_signal.data(), 0); Mat_VarWrite(matfp, matvar, MAT_COMPRESSION_ZLIB); Mat_VarFree(matvar); ```

Dear @rom-burner, I've just built the software in a docker container and I can't reproduce this problem: ``` docker run -it --rm archlinux:latest pacman -Syu --noconfirm pacman -S --noconfirm gcc...

Hi @rom-burner , `volk_gnsssdr` uses a vector template with its own allocator (see [src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/include/volk_gnsssdr/volk_gnsssdr_alloc.h](https://github.com/gnss-sdr/gnss-sdr/blob/main/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/include/volk_gnsssdr/volk_gnsssdr_alloc.h)): ``` namespace volk_gnsssdr { ... template using vector = std::vector; } ``` The library passes the...

Something like this should work, and it writes the data in the right position: ``` std::move(in, in + buff_increment, d_data_buffer.begin() + d_buffer_count); ``` Could you please confirm that replacing the...

It does compile and run under macOS (so it actually _moves_ the data). It can be replaced by ``` std::copy(in, in + buff_increment, d_data_buffer.begin() + d_buffer_count); ``` which maybe is...

The `next` branch should be ok now.

Hi all, no, you cannot retrieve RINEX files before getting the first PVT fix. In the case of using a multi-signal receiver (e.g. L1 and L2), you need the first...

Totally agree, that part of the code is poorly written. I'm in favour of rewriting it and implementing an actual Hamming decoder.

I guess you are using a quite old version of gnss-sdr. What's the output of: ``` $ gnss-sdr --version ``` It should be `gnss-sdr version 0.0.14`, or `gnss-sdr version 0.0.14-git-next-xxxxxx`...