|
From: | Ceren Karaköse |
Subject: | Re: Symbol Sync Block Python Source File Passing Wrong Constellation |
Date: | Fri, 6 Dec 2024 12:23:02 +0000 |
Dear Adrian & Daniel, thanks for the reply. You're absolutely right. symbol_sync_cc_impl.cc invokes d_ted(timing_error_detector::make(detector_type, slicer)). However, timing_error_detector.cc ignores the argument by the following:
case TED_GARDNER:
return std::make_unique<ted_gardner>(); Best, Ceren From: discuss-gnuradio-bounces+ceren.karakose=outlook.com@gnu.org <discuss-gnuradio-bounces+ceren.karakose=outlook.com@gnu.org> on behalf of Adrian
Musceac <kantooon@droiddv.org>
Sent: Friday, December 6, 2024 12:32 To: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org> Subject: Re: Symbol Sync Block Python Source File Passing Wrong Constellation On Friday, 6 December 2024 10:30:33 EET Ceren Karaköse wrote:
> Hi all, > > I'm using Symbol Sync from core GNU library. Although when Gardner TED is > selected, the parameters section **do not**have any option to define a > slicer constellation, the generated python file passes qpsk.base as slicer > argument as follows: Hi, Daniel is right I believe. Only decision-directed algorithms use the slicer constellation. That includes M&M, modified M&M and zero-crossing. Check out the descriptions for the TED type in doxygen for example. Adrian |
[Prev in Thread] | Current Thread | [Next in Thread] |