-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typo's + Question #97
base: master
Are you sure you want to change the base?
Conversation
lejafar, Mostly just experience. The tricky part about having multiple control loops within one another is that they can cause instability. See, for example, the symtrack object's loop here at http://liquidsdr.org/doc/symtrack/: The remodulated symbol value is a bit of ugly code... but I didn't come up with a better way to handle it so that's what I ended up committing. Thanks! |
with respect to the unused |
Thanks for the clarification! And thanks for making this awesome library and putting together all the examples and documentation, it really helped me a lot in understanding how some of these DSP elements are implemented! |
You're absolutely welcome! It's been a lot of fun working on this, but I know liquid-dsp has a long, long way to go! |
Hi Joseph!
Besides the typo's I wanted to ask you for any reference or reasoning that went into picking these bandwidth calculating factors inside
symtrack.c
, or is it solely based on experience?What also got me going for a while is the following statement inside
modem_qam.c
EDIT: after dubble checking it does gives the expected result so I must have looked over something
Because the value that is put into
_q->x_hat
is not an estimate or re-modulation of_x
right? For 16-QAM, the thing that is being put intores_i
iscimagf(_x) - _ref[1] - _ref[0]
, same forres_q
andcrealf(_x)
. Because_ref[0]
is just 0,_q->x_hat
will contain_ref[1]
, but that still works as an indication of the error calculated bymodem_get_demodulator_evm
, so that might be how it is supposed to be?Thanks in advance!