Re: [Discuss-gnuradio] a silly question about the sream to vector block

2014-05-16 Thread Mike Jameson
The 'Stream To Vector' block takes a stream of samples and makes a vector stream out of them. This vector stream is just the samples from the stream put into parallel so that for each sample you are actually sending the vector length per second as the sample rate. The use of the 'Stream To Vector

[Discuss-gnuradio] a silly question about the sream to vector block

2014-05-16 Thread Abouda Yassine
Hi guys, While i was trying to figure out what the stream to vector block does,I understood that if I choose for example nitems=1024 and vector length=1,I get in the output 1024 vectors of 1 item each.And when I was reading about it on this web page ( http://gnuradio.org/redmine/projects/gnuradio/

Re: [Discuss-gnuradio] A silly question

2012-09-12 Thread sumitstop
Thanks Josh I did it :) -- View this message in context: http://gnuradio.4.n7.nabble.com/A-silly-question-tp29214p37567.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org h

Re: [Discuss-gnuradio] A silly question

2012-08-29 Thread Alick Zhao
On Mon, 27 Aug 2012 09:46:56 -0700, Josh Blum wrote: > >> >> How can we do that in a C++/Python hybrid flowgraph? Is there a Python >> interface out there? >> > > So to register a python callback into C++ is tricky. The answer is SWIG > directors. However, I nearly killed myself yesterday trying

Re: [Discuss-gnuradio] A silly question

2012-08-27 Thread Josh Blum
> > How can we do that in a C++/Python hybrid flowgraph? Is there a Python > interface out there? > So to register a python callback into C++ is tricky. The answer is SWIG directors. However, I nearly killed myself yesterday trying to get that madness to work. So until I figure that out... If

Re: [Discuss-gnuradio] A silly question

2012-08-26 Thread Alick Zhao
On Fri, 24 Aug 2012 10:18:53 -0700, Josh Blum wrote: > > > On 08/24/2012 06:26 AM, sumitstop wrote: >> >> Thanks Ryan...it worked for the three UHD warnings. Now I shall do something >> about >> > > http://files.ettus.com/uhd_docs/manual/html/general.html#disabling-or-redirecting-prints-to-stdou

Re: [Discuss-gnuradio] A silly question

2012-08-24 Thread Josh Blum
On 08/24/2012 06:26 AM, sumitstop wrote: > > Thanks Ryan...it worked for the three UHD warnings. Now I shall do something > about > http://files.ettus.com/uhd_docs/manual/html/general.html#disabling-or-redirecting-prints-to-stdout Make this one-time call in c++ at the start of your process.

Re: [Discuss-gnuradio] A silly question

2012-08-24 Thread sumitstop
Thanks Ryan...it worked for the three UHD warnings. Now I shall do something about ~ linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.003-177-g584b7ae2 -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 by

Re: [Discuss-gnuradio] A silly question

2012-08-24 Thread Ryan Wolfarth
If you execute the following commands you will get rid of those warnings. These adjust the maximum read and write buffer sizes allowed that the OS is allowed to use for network interfaces. See more here: http://wwwx.cs.unc.edu/~sparkst/howto/network_tuning.php sudo sysctl -w net.core.rmem_max=500

[Discuss-gnuradio] A silly question

2012-08-24 Thread sumitstop
Hi Community , Whenever we open a UHD device following message appears on the terminal : linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.003-177-g584b7ae2 -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Curre