Are you looking to have these put into the core or do you wish to work
on it some more first? These are very useful and I look the finite
state machine formulation.
Bob
Achilleas Anastasopoulos wrote:
I just realized I had the wrong website.
The correct one is:
www.eecs.umich.edu/~anast
I just realized I had the wrong website.
The correct one is:
www.eecs.umich.edu/~anastas/gnuradio
Best,
Achilleas
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Something was recently changed in the gnuradio-core make that causes an
error:
Notice the waiting for jobs. This was compiled with make, not buildit.
I was having a problem with doing the build on darwin, MacOSX and then I
ran into the same problem at Frank Brickle's.
By the way, the build
Hi everybody,
I finally found some time and ported in gnuradio-2.7
my old ANSI-C implementation of a generic framework
for finite state machines (FSM) and corresponding
sequence detection using the Viterbi algorithm (VA).
The code is more generic (and I guess slower; 117 Kbps
for an 1/2 CC with 1
On Tue, Apr 11, 2006 at 06:05:11PM -0400, Charles Swiger wrote:
> On Tue, 2006-04-11 at 09:52 -0400, Charles Swiger wrote:
> > Well, it compiles but there are likely still issues since the 0.9 work
> > function in GrAtscTrellisEncoder.cc has stuff to deal with an array
> > of encoders that I don't
On Sun, Apr 09, 2006 at 08:56:38PM -0700, Ges wrote:
> Thanks Eric.
>
> I looked up the max gain. It is 20dB. So I set it to 20 dB on the tx
> and rx side. Also I was using payload size of 1024; so I tried
> different sizes 512, 256 and 64. The size of the file was 1087
> bytes. But it doesnt s
I have been reading about how the Tx path works in the USRP and was slightly
confused. I know that some of the interpolation is done in the FPGA and
some of it is done in the DUCs on the external chips. Noting the following
code from class usrp_standard_tx:
/*!
* \brief Set output mux con
On Wed, 2006-04-12 at 01:23 +0200, Martin Dvh wrote:
> Did you check that the type of &out[i] is atsc_data_segment
> and the type of &in[i] is atsc_mpeg_packet_rs_encoded?
>
OK - atsc_trellis_encoder.cc compiles and runs and produces
reasonable looking output:
01 00 34 00 06 01 01 06
