discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] [EXT] Re: How NOT to write a GRC block?


From: Chesir, Aaron M.
Subject: Re: [Discuss-gnuradio] [EXT] Re: How NOT to write a GRC block?
Date: Tue, 12 Mar 2019 19:07:01 +0000

Chris,

 

I am referring to the first GRC screen (attached, or below):

 

 

The reason I am requesting the source GRC file is that I have no idea what the parameters are in the various blocks, for which the above display shows “…”

 

Thanks in advance,

 

Aaron

 

 

From: Chris Kuethe <address@hidden>
Sent: Tuesday, March 12, 2019 3:03 PM
To: Chesir, Aaron M. <address@hidden>
Cc: address@hidden
Subject: [EXT] Re: [Discuss-gnuradio] How NOT to write a GRC block?

 

1) It was not clear which source file you are referring to. I assume it's "pam_timing.grc" based on a search of "how not to write a block"... but I don't know exactly what file you're reading, nor exactly which file you're missing.

2) based on this assumption, I searched github for pam_timing.grc and found this

 

With a little bit of digging, I found an old official version:

 

On Tue, Mar 12, 2019 at 11:42 AM Chesir, Aaron M. <address@hidden> wrote:

Folks,

 

As part of my GNUradio/GRC training, I am reviewing Tom Rondeau’s August 24, 2015 presentation “How Not To Write A Block”. I would like to go through its paces to learn how to write good blocks. Unfortunately, I do not see any way of accessing the original GRC source file which he uses as his starting point.

 

If any of you have come across the referenced source file, could you please email me a copy?

 

Thanks in advance,

 

Aaron

 

 

Aaron Chesir

The MITRE Corporation

200 Valley Road

Mount Arlington, NJ 07856

w: (973) 810-0612

c: (908) 380-5798

address@hidden

“Ignorance is Bliss, but Knowledge is Power”

 

_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


 

--

GDB has a 'break' feature; why doesn't it have 'fix' too?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]