pmonta / gnss-dsp-tools Goto Github PK

Hi pmonta,

your project looks really promising. I could not find any information about a license concerning using your contributions. I recommend you to take a look at the great help page https://help.github.com/articles/open-source-licensing and add a license file to your project to allow others to properly use it.
I am working with a research and development institute doing software development for GNSS receivers and would be very interested to also use your code in our projects. I would recommend the MIT license: http://choosealicense.com/licenses/mit/

If you need help and grant me the permission I also offer my help in adding this license information to your repository if you give me the commit right.

Hello!

def make_l5q(prn):
xb_offset = l5q_init[prn]
n = code_length
xb_shift = xb[np.mod(np.arange(xb_offset,xb_offset+n),n)]
return np.logical_xor(xa,xb_shift)

Periodicity of of xb is 2**13-1 (8191), thus the correct xb_shift should be (?):
xb_shift = xb[np.mod(np.arange(xb_offset,xb_offset+n), 8191)]

Here is another source for comparison:
https://github.com/danipascual/GNSS-matlab/tree/master/prn_codes

I am trying to implement Galileo E1 acquisition and tracking. but I have some doubts:

1. What is this offset to L1 carrier frequency? (Line no: 96 in Track_galileo_E1b.py)
2. While parsing command line arguments, why the sampling frequency is different from the initialised value at the top of acquisition and tracking code?

Thank you
Raza Javed

For offsetting the early and late fingers for L1 tracking, the python tracking code uses 0.05 vs the typical 0.5 (1/2 chip) offset. When i change the 0.05 to 0.5, the EPL values look more acceptable to me, i.e. the P value is always the peak value. Is the 0.05 an error, or is there some reason to use a 1/20 chip offset? This seems way too tight to me. thx!