discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] work function - how it fits in the big picture


From: Eric Blossom
Subject: Re: [Discuss-gnuradio] work function - how it fits in the big picture
Date: Thu, 20 Apr 2006 13:54:30 -0700
User-agent: Mutt/1.5.9i

On Thu, Apr 20, 2006 at 03:31:05PM -0400, Charles Swiger wrote:
> On Thu, 2006-04-20 at 09:12 -0700, Eric Blossom wrote:
> > > 
> > > Runs, few issues in the qa script then will update cvs.
> > > 
> > > --Chuck
> > 
> > Don't commit the change to flow_graph.py, I believe the right answer
> > is elsewhere.  Please do commit the atsc changes even though it fails
> > make check, and I'll use it to test and fix.  I think this is a symptom
> > of the same problem Marcus is seeing when trying to use large numbers
> > of taps in the FFT filters.
> > 
> 
> atsc_trellis_encoder, atsc_viterbi_decoder and atsc_ds_to_softds to
> glue them together have been checked in. The python qa_atsc.py script
> has another loopback test 002 for 
> 
> src -> randomizer -> rs_encoder -> trellis_encoder -> ds_to_softds ->
>     viterbi_decoder -> rs_decoder -> derandomizer -> dst
> assert src = dst

OK.

> 
> Notice that it does NOT have the interleaver/deinterleaver as I
> don't know how to handle the 52 segment delay which causes
> trellis to choke on regular segment flag check.

I think that if you move the skiphead to the very end (or just do it
by slicing the 52 out of the python expected vs actual vals), it will
work with the interleaver in.

Eric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]