[Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Mostafa Alizadeh
Hi, I worked on GNURadio for many hours. After all, I prepared my blocks in c++. However, the source by which I produce random bits (items with sizeof(char) ) doesn't work properly! By properly I mean, I wanted GNURadio to lead me control how it's going to call the *source.* It's crazily calling

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Mike Jameson
The Throttle block is required if you are not using any external hardware: http://gnuradio.org/doc/doxygen/classgr_1_1blocks_1_1throttle.html Mike -- Mike Jameson M0MIK BSc MIET Ettus Research Technical Support Email: supp...@ettus.com Web: http://ettus.com On Sun, Jun 1, 2014 at 9:30 AM,

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Mostafa Alizadeh
Hi Mike, No, the throttle isn't a source! It just controls the flow of items in an specific time interval. I don't want this! I want cognitively tell the source produces the random bits after some special procedures have done (a message can do this for the source). But the scheduler crazily wants

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Marcus Müller
Mostafa, I know you've been working many hours on this :) so don't worry, you're being heard. Nevertheless, GNU Radio is surely not calling the asking the source crazily to produce items. GNU Radio is a streaming-into-buffers architecture, which means that the runtime will ask a source to

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Mostafa Alizadeh
Hi Marcus, By mentioning that I spent many hours I wanted to say I'm hardly stuck on this problem yet! :) You said the there is no problem that we wait on the source to produce as long as we want! But this is not true when I have other blocks waiting for processing!! In other word, when the

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Marcus Müller
Hi Mostafa, You said the there is no problem that we wait on the source to produce as long as we want! But this is not true when I have other blocks waiting for processing!! Not true. If your block can't produce something, it's not GNU Radio's fault your downstream blocks don't have anything to

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Activecat
On Sun, Jun 1, 2014 at 4:56 PM, Mostafa Alizadeh m.alizade...@gmail.com wrote: Hi Mike, No, the throttle isn't a source! It just controls the flow of items in an specific time interval. I don't want this! I want cognitively tell the source produces the random bits after some special

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Mostafa Alizadeh
Hi Marcus, On Sun, Jun 1, 2014 at 2:44 PM, Marcus Müller marcus.muel...@ettus.com wrote: Hi Mostafa, You said the there is no problem that we wait on the source to produce as long as we want! But this is not true when I have other blocks waiting for processing!! Not true. If your block

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Mostafa Alizadeh
Activecat, I think change my topology to get rid of this things. :) However, I still believe in that the GNURadio fails in this scenario. As we have throttle or message_strobe blocks, I need to have a source which generates items controlled by another block. I'll try to see this problem in

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Marcus Müller
Hi Mostafa, this is no good. If you don't tell us why and how you would want to do that, we can't discuss if and how GNU Radio is lacking. Really, the GNU Radio architecture wasn't meant for this kind of flow control, but that's less of a shortcoming than a design choice, keeping flow graph

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Marcus Müller
Hi Mostafa, On 01.06.2014 19:23, Mostafa Alizadeh wrote: This is not true because when I produce 1-3 packet of bits, the scheduler doesn't go to the other blocks while there is items for them! The scheduler calls the random bit generator for about 10 times!! I have tried that, and can disprove

Re: [Discuss-gnuradio] a criticism to GNURadio's scheduler!

2014-06-01 Thread Activecat
On Mon, Jun 2, 2014 at 1:27 AM, Mostafa Alizadeh m.alizade...@gmail.com wrote: Activecat, I think change my topology to get rid of this things. :) However, I still believe in that the GNURadio fails in this scenario. As we have throttle or message_strobe blocks, I need to have a source

[Discuss-gnuradio] C++11 support

2014-06-01 Thread Activecat
Hi list, Could anyone tell me about the C++11 support in gnuradio? Thanks. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] C++11 support

2014-06-01 Thread Tom Rondeau
On Sun, Jun 1, 2014 at 7:54 PM, Activecat active...@gmail.com wrote: Hi list, Could anyone tell me about the C++11 support in gnuradio? Thanks. For continued support with various and older systems, we don't support C++11. Tom ___

[Discuss-gnuradio] OFDM_Cyclic_Prefixer

2014-06-01 Thread xianda
Hi all: Thank you in advance. I want to test my understanding about ofdm_cyclic_prefixer.As this picture say:I place a file sink before and after ofdm_cyclic_prefixer block respectively.And the result is that file d.dat just add the 16 cp when compared to c.dat.And maybe the

Re: [Discuss-gnuradio] OFDM_Cyclic_Prefixer

2014-06-01 Thread Ron Economos
If the rolloff parameter is zero, the block does not do any pulse shaping. The rolloff parameter is in symbols, and must be at least 2 and less than or equal to CP length. Ron On 6/1/2014 5:53 PM, xianda wrote: Hi all: Thank you in advance. I want to test my understanding about