It was just too easy to replace them with somewhat more cent stuff. A colleague even rolled his own from wire, epoxy glue and ferrite beads smashed in a mortar. That looked, hmm, ugly, but performed excellently. Now, you get them from MCL and Coilcraft. But for a 10 or 100 MHz lowpass, that's way over the top. Not even if you are nuts.

First let me say this is first time I have posted to the group so go easy on me. :) Secondly I want everyone to know that you guys make me feel so NORMAL for wanting to use and understand accurate timing devices.

The NoC Shell hides the complexity of RFNoC from your block, making it easy to plug your IP into the USRP.

If I setup logging will errors automatically propagate > to the top block? Currently, my blocks in the flowgraph will throw an > error and not report it to the TB. What is the best method to handle > OOT block errors?

, extruding it vertically, then adding > a lip at the top that is thicker.

Bill, it is quite easy: When running LH type 'T', you will then see the list 'Reference' then hit 'U' for UTC-time. This should resolve the problem. I had the same effect before confusing on top left side is showing 'UTC ofs: 18' but this is only the information for the difference GPS/ UTC time I understand. But LH was still running with GPS-time setting.

It’s quite easy. The other thing I did is make 2 half tooth profiles instead of one whole. Now N = 2 works. I also found that skin() did not work at low tooth counts and had to use a combination of skin and hull. If two profiles are very different sizes and far apart, that seemed to be the problem area.

You're drawing a black shape, and then drawing a super-bright shape on top of it so that only the outline shows. So just use difference.  That way you don't need to simulate the background; you can let the actual background show through. 

On Tue, 2026-05-12 at 21:48 -0400, Jon Bondy via Discuss wrote: > Any easy way to round the edges on this shape? If I was asked to make this shape, I'd probably do it this way.

) > Yeah, specials are still a fuzzy thing for me .. even after Jordan’s > diligent attempt to educate me on how they work i am not at all clear > on what they bring to the language that is any different from having > global variables at the top level of scope > They *aren't* necessarily at the top level.  Try running this...