[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] MSB
From: |
Eric Blossom |
Subject: |
Re: [Discuss-gnuradio] MSB |
Date: |
Tue, 20 Mar 2007 07:27:58 -0700 |
User-agent: |
Mutt/1.5.9i |
On Mon, Mar 19, 2007 at 10:55:46AM -0700, Matt Ettus wrote:
>
> >No particular fault. However, the outputs from the USRP are almost
> >always some kind of complex values. They may be encoded as 16-bit I &
> >Q, or 8-bit I & Q or 4-bit or 2-bit or 1-bit. The question is how do
> >we want to deal with them downstream from the USRP? The existing
> >usrp.source_s could be considered broken (although there are users of
> >it.) The data is really interleaved 16-bit I & Q, though it's
> >presented as if each sample was only 16-bits wide. In fact a "sample"
> >is really composed of 2 16-bit values.
> >
>
>
> Maybe we should make gr_complex_short be a typedef for complex<short>
> and output those.
>
> Matt
That would make sense.
We'd need to come up with some kind of unambiguous naming convention
for the variants.
Eric
- Re: [Discuss-gnuradio] MSB, (continued)
- Re: [Discuss-gnuradio] MSB, Matt Ettus, 2007/03/19
- Re: [Discuss-gnuradio] MSB, Davide Anastasia, 2007/03/20
- Re: [Discuss-gnuradio] MSB, Davide Anastasia, 2007/03/22
- Re: [Discuss-gnuradio] MSB, Davide Anastasia, 2007/03/23
- [Discuss-gnuradio] Sampling rate of USRP board, eenrti, 2007/03/26
- Re: [Discuss-gnuradio] Sampling rate of USRP board, Hans Glitsch, 2007/03/26
- [Discuss-gnuradio] Intrerleave output from usrp_rx_cfile.py, eenrti, 2007/03/29
- [Discuss-gnuradio] Asking info about the Interleaving of samples, eenrti, 2007/03/29
- Re: [Discuss-gnuradio] Asking info about the Interleaving of samples, Matt Ettus, 2007/03/29
- Re: [Discuss-gnuradio] Asking info about the Interleaving of samples, Eric Blossom, 2007/03/29
- Re: [Discuss-gnuradio] MSB,
Eric Blossom <=
- Message not available
- Message not available
- Message not available
- Re: [Discuss-gnuradio] MSB, Eric Blossom, 2007/03/22