Namazu: a Full-Text Search Engine

This index contains 81,287 documents and 1,265,472 keywords.

Last modified: 2024-05-03

321. txtaytW3mfWca.txt (score: 2)

Author: unknown

Date: Thu, 01 Jun 2006 16:19:48 -0500

cvs diff: Diffing . Index: configure.ac == RCS file: /sources/gnuradio/gnuradio-core/configure.ac,v retrieving revision 1.47 diff -u -r1.47 configure.ac -- configure.ac 16 Apr 2006 03:41:58 -0000 1.4

/archive/html/discuss-gnuradio/2006-06/txtaytW3mfWca.txt (16,617 bytes)

322. [Discuss-gnuradio] gr.feval_ff (score: 3)

Author: Eric Blossom <eb@comsec.com>

Date: Thu, 8 Jun 2006 15:10:30 -0700

I've justed added 3 classes (not GR blocks) that allow C++ code to evaluate functions defined in Python. This isn't for performance critical things, but will be useful in certain situations. It uses

/archive/html/discuss-gnuradio/2006-06/msg00095.html (4,398 bytes)

323. [Discuss-gnuradio] Re: Multiplying blocks (score: 2)

Author: Johnathan Corgan <jcorgan@aeinet.com>

Date: Fri, 09 Jun 2006 15:58:58 -0700

I think you've got it, but not sure. I want to start with a stream of floats or complex floats, and process them in "chunks". That is what stream_to_vector will do--accumulate a set number of input s

/archive/html/discuss-gnuradio/2006-06/msg00103.html (6,976 bytes)

324. Re: [Discuss-gnuradio] Re: Multiplying blocks (score: 3)

Author: Eric Blossom <eb@comsec.com>

Date: Fri, 9 Jun 2006 16:41:31 -0700

OK. Here's how I think you could do it without any new code (admittedly it's a bit ugly): Use vector_source_f to provide your window, and set the repeat argument to True. Before using stream_to_vecto

/archive/html/discuss-gnuradio/2006-06/msg00104.html (7,436 bytes)

325. [Discuss-gnuradio] Swig problems compiling gnuradio-core/CVS on FC5 (score: 37)

Author: "Kyle Jamieson" <jamieson@gmail.com>

Date: Mon, 12 Jun 2006 15:12:32 -0400

I'm using FC5, compiling gnuradio-core from cvs. With both the current Fedora version of swig (1.3.24) and swig 1.3.29 from Sourceforge, I have problems compiling src/lib/swig/gnuradio_swig_python.cc

/archive/html/discuss-gnuradio/2006-06/msg00122.html (10,168 bytes)

326. [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS on FC5 (score: 33)

Author: "Kyle Jamieson" <jamieson@gmail.com>

Date: Tue, 13 Jun 2006 16:51:37 -0400

Well, I've resolved this issue for myself. I'd be interested in why this isn't bugging everyone else, and if I made a mistake. It just involved an apparently bad header prototype; patch follows. Inde

/archive/html/discuss-gnuradio/2006-06/msg00135.html (7,010 bytes)

327. RE: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS onFC5 (score: 34)

Author: "John E. Don Carlos" <jdcarlos@pacbell.net>

Date: Tue, 13 Jun 2006 15:24:41 -0700

Thanks, I had this problem a week ago after installing FC5 but didn't have the time or skill to solve it. Exactly how do i apply the patch? and to what? Thanks, John --Original Message-- From: addres

/archive/html/discuss-gnuradio/2006-06/msg00136.html (7,730 bytes)

328. Re: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS onFC5 (score: 34)

Author: "Kyle Jamieson" <jamieson@gmail.com>

Date: Tue, 13 Jun 2006 21:48:27 -0400

The patch gets applied in the gnuradio-core directory. Cut-n-paste the patch from my original email into some file 'foo', then patch -p0 < foo in dir gnuradio-core. On 6/13/06, John E. Don Carlos <ad

/archive/html/discuss-gnuradio/2006-06/msg00137.html (8,229 bytes)

329. RE: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS onFC5 (score: 35)

Author: "John E. Don Carlos" <jdcarlos@pacbell.net>

Date: Tue, 13 Jun 2006 22:52:33 -0700

I applied the patch but still get a whole lot of gnuradio_swig_python.cc warnings: dereferencing type-prunned pointer will break strict-aliasing rules. Then the build hangs. Before the patch, it woul

/archive/html/discuss-gnuradio/2006-06/msg00138.html (9,190 bytes)

330. Re: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS on FC5 (score: 33)

Author: Eric Blossom <eb@comsec.com>

Date: Tue, 13 Jun 2006 23:15:47 -0700

Hi Kyle, For some reason, g++ 4.0.2 wasn't reporting this as a problem. Thanks for the fix. I've applied it to CVS. Eric

/archive/html/discuss-gnuradio/2006-06/msg00139.html (6,432 bytes)

331. Re: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS onFC5 (score: 35)

Author: Eric Blossom <eb@comsec.com>

Date: Tue, 13 Jun 2006 23:18:22 -0700

FYI, I don't think it's hanging. It takes a pretty long time to compile gnuradio_swig_python.cc. Depending on your system, it could take 10 minutes or more. Can you let me know the versions of swig a

/archive/html/discuss-gnuradio/2006-06/msg00140.html (6,629 bytes)

332. Re: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS onFC5 (score: 36)

Author: "Kyle Jamieson" <jamieson@gmail.com>

Date: Wed, 14 Jun 2006 08:29:17 -0400

Right, depending on the version of swig you're using, you'll get either a lot or a whole lot of warnings, and then it'll take a minute or so to compile. FYI, I don't think it's hanging. It takes a pr

/archive/html/discuss-gnuradio/2006-06/msg00144.html (6,968 bytes)

333. RE: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS onFC5 (score: 38)

Author: "John E. Don Carlos" <jdcarlos@pacbell.net>

Date: Wed, 14 Jun 2006 17:01:14 -0700

Right! I let the warnings concern me too much. It did keep compiling. I'm now getting a configure error: gr-audio-osx required darwin or MacOS X. What do i need to install? i'm running on a pentium w

/archive/html/discuss-gnuradio/2006-06/msg00153.html (7,447 bytes)

334. Re: [Discuss-gnuradio] Re: Swig problems compiling gnuradio-core/CVS onFC5 (score: 34)

Author: Eric Blossom <eb@comsec.com>

Date: Wed, 14 Jun 2006 18:12:20 -0700

Don't build gr-audio-osx unless you're on a Mac ;) Eric Thanks, Eric

/archive/html/discuss-gnuradio/2006-06/msg00157.html (6,376 bytes)

335. Re: [Discuss-gnuradio] Threading in python? (score: 2)

Author: Ilia Mirkin <imirkin@MIT.EDU>

Date: Thu, 15 Jun 2006 00:35:50 -0400

Quoting Michael Ford <address@hidden>: Up until now, all of my networking projects have been in C/C++, and I'd like to think that I'm pretty good with threading in those languages. As with the previo

/archive/html/discuss-gnuradio/2006-06/msg00159.html (6,403 bytes)

336. Re: [Discuss-gnuradio] Threading in python? (score: 3)

Author: Eric Blossom <eb@comsec.com>

Date: Wed, 14 Jun 2006 22:09:45 -0700

Thanks Ilia. Actually it's not too bad. The GIL has been around for quite a while. Pretty sure it was before 2.4. Anyhow, if your threads are all in python everything "just works". Python threads are

/archive/html/discuss-gnuradio/2006-06/msg00161.html (6,677 bytes)

337. [Discuss-gnuradio] usrp_basic and gr_block (score: 2)

Author: "Michael Ford" <mford1@uiuc.edu>

Date: Sat, 17 Jun 2006 15:23:53 -0500

I'm trying to use a function in the usrp_basic class, but there's no SWIG .i script for it. While looking at the tutorials, I read that all processing blocks need to derive from the class gr_block. H

/archive/html/discuss-gnuradio/2006-06/msg00196.html (5,547 bytes)

338. Re: [Discuss-gnuradio] Threading in python? (score: 3)

Author: Ilia Mirkin <imirkin@MIT.EDU>

Date: Sat, 17 Jun 2006 16:36:27 -0700

You're right, the concept of the GIL has been around for a while. But Python 2.4 added a couple of crucial convenience functions: PyGILState_Ensure() and PyGILState_Release() Which allow a thread whi

/archive/html/discuss-gnuradio/2006-06/msg00197.html (6,537 bytes)

339. Re: [Discuss-gnuradio] usrp_basic and gr_block (score: 2)

Author: Eric Blossom <eb@comsec.com>

Date: Sun, 18 Jun 2006 09:58:02 -0700

Hi Michael, Pretty much all of usrp_basic.h as well as usrp_standard.h is wrapped by gr-usrp/src/usrp1.i. The usrp specific classes that derive from gr_block are usrp1_source_base.h and usrp1_sink_ba

/archive/html/discuss-gnuradio/2006-06/msg00208.html (6,237 bytes)

340. Re: [Discuss-gnuradio] usrp_basic and gr_block (score: 2)

Author: "Michael Ford" <mford1@uiuc.edu>

Date: Sun, 18 Jun 2006 12:31:40 -0500

by gr-usrp/src/usrp1.i. The usrp specific classes that derive from gr_block are usrp1_source_base.h and usrp1_sink_base.h. I recall Matt mentioning that to read the RSSI you use one of the aux adcs.

/archive/html/discuss-gnuradio/2006-06/msg00211.html (6,889 bytes)

This search system is powered by Namazu v2.0.21