Eric Blossom wrote:
We could just blindly preform the replace, but that fails on the
pathological case of *nix filenames with literal \'s in them.
Hmmm, didn't think about that.
We probably also should introduce \ before any spaces in windows filenames.
Or just spit out an error like:
You used
On Tue, Jul 12, 2005 at 12:54:21AM +0200, Martin Dvh wrote:
> Eric Blossom wrote:
>
> >OK.
> >
> >Running python on windows, can you please send me the output of this:
> >
> >$ python
> >
> import distutils.sysconfig
> print distutils.sysconfig.get_python_inc(plat_specific=False)
>
> This
On Mon, Jul 11, 2005 at 02:09:25PM -0700, Charles Chen wrote:
> Hi All,
>
> I have everything installed and was trying to run
> ./usrp_oscope.py according to the instructions at
> http://comsec.com/wiki?UsrpInstall . However, I get an
> error when I try to run the file.
>
> from gnuradio_sw
Eric Blossom wrote:
OK.
Running python on windows, can you please send me the output of this:
$ python
import distutils.sysconfig
print distutils.sysconfig.get_python_inc(plat_specific=False)
This is similar to what I did before my last post.
If I start the python command promt on windows
Hi All,
I have everything installed and was trying to run
./usrp_oscope.py according to the instructions at
http://comsec.com/wiki?UsrpInstall . However, I get an
error when I try to run the file.
[EMAIL PROTECTED] usrp]# ./usrp_oscope.py
Traceback (most recent call last):
File "./usrp_oscope
Sachi wrote:
> The ideal situation appearing in my mind is we send a
> text file, and we should be able to recover it
> correctly at the receiver and read it. Have you ever
> really achieved this?
Yes.
> Do you have any suggestion that we can improve the
> realibility of the FSK transmisstion
On Monday 11 July 2005 12:43, Matt Ettus wrote:
> Sounds like a very interesting application. However, getting all those
> bits in and out of the computer would only solve half the problem. You
> need to be able to perform computations on that data, and your PC would
> not be able to keep up. Th
> The USRP is capable of sampling 256MS/s (64MS/s across four channels), so you
> need 256MB/s to not lose data, if you are interested in, say, doing a
> continuous spectrum capture across a 128MHz band. We have an application for
> Radio Astronomy that involves interferometry where bandwidth
On Mon, Jul 11, 2005 at 06:26:51AM +0200, Martin Dvh wrote:
> Eric Blossom wrote:
> >On Mon, Jul 11, 2005 at 01:38:43AM +0200, Stephane Fillod wrote:
> >
> >>>I checked in a new version of gr_python.m4 that uses distutils to
> >>>determine the include path for Python.h. I tested it on GNU/Linx and
On Sunday 10 July 2005 06:20, Tim Ansell wrote:
> Forgive me if I'm wrong (I only kinda lurk, rather then participate),
> but wasn't the whole idea of Gigabit Ethernet to allow long cable runs?
Partially. There are other advantages to GigE; but I'm kindof just mentioning
alternatives.
> So that
10 matches
Mail list logo
