Lightnews — Scholar-powered news

Jern @jernd.bsky.social · 14h

Have you considered build123d? In short it combines benefits of OpenSCAD with benefits of BREP CAD like Fusion.

Reposted by Jern

OSH Park @oshpark.bsky.social · 8d

Live now!
Open Source Hardware Association (OSHWA) is doing a Show and Tell 12 hour Membership Drive with creators from all over joining us to show off their work! @oshwassociation.bsky.social www.youtube.com/watch?v=Yn0e...

Show and Tell 12 hour Membership Drive

YouTube video by The Open Source Hardware Association

www.youtube.com

4 6

Reposted by Jern

OSHWA @oshwassociation.bsky.social · 22d

It's almost October which means it's almost Open Hardware Month! Mark your calendars and get excited because there's going to be really amazing speakers and perhaps even some sloths during our 12hr membership livestream! How are you celebrating Open Hardware Month?
www.youtube.com/watch?v=Yn0e...

12 23

Jern @jernd.bsky.social · 12d

See the [build123d cheatsheet](build123d.readthedocs.io/en/latest/ch...) for further information about available arc types (supports hovering to see doc string). 3/3

Cheat Sheet — build123d 0.1.dev194+g0166408f6 documentation

build123d.readthedocs.io

1

Jern @jernd.bsky.social · 12d

Assumption 1 is described above. Assumption 2 is that the arc starts at an angle perpendicular to an axis passing through the regular polygon center. For that build123d's `TangentArc` was a good choice, however it may also be possible to use `RadiusArc` which accepts two points and a radius. 2/3

1 1

Jern @jernd.bsky.social · 12d

No, I simply set the point at which the arc would terminate. The resulting radii are different for each regular polygon. There are a number of approaches here that would work. The correct way to formalize this is a technical drawing, but given the lack of that I had to make some assumptions. 1/2

1 1

Jern @jernd.bsky.social · 13d

Nice, yes OpenSCAD also supports 2D offsets -- so that is probably a good idea here.

Jern @jernd.bsky.social · 13d

Awesome, glad to hear I understood your goal better this time! This is python, yes. build123d supports exporting to a wide range of 3D formats; STL, 3MF, GLTF, STEP, and BREP.

1

Jern @jernd.bsky.social · 14d

OK, I generalized it and it now works for even and odd regular polygons. FYI, It is also totally possible to use various transformations to turn these 1D objects into 3D solids (not demonstrated here). Quick and dirty video demo + code:

1 1 1

Jern @jernd.bsky.social · 14d

Here's my first attempt at the square, I think should be generalizable to all regular polygons fairly easily but need to think on it a bit. 1D are first class citizens in build123d, which makes this quite a bit easier

1 1

Jern @jernd.bsky.social · 14d

Hmm, is there a rule defining the orientation/angle of the arc at the e.g. square corner?

2

Jern @jernd.bsky.social · 14d

How about this? I made a few improvements since my last post. I also fused the hexagons together and then offset them to create some tolerance to allow for a better fit. The tolerance I used is quite high just to make it visually obvious.

1

Jern @jernd.bsky.social · 14d

Wondering if build123d could work for you? I watched your video and came up with this approach using construction geometry that act as helpers to place hexagons. This approach should scale very well to more complex hexagonal tilings.

1 1

Jern @jernd.bsky.social · 19d

Ah, didn't realize you had your own implementation of Minkowski! Nice progress for sure

1

Jern @jernd.bsky.social · 19d

Nice, how fast is minkowski these days?

1 1

Jern @jernd.bsky.social · 25d

Do you have any thoughts on the app signing requirements that are becoming more and more mandatory?

1

Jern @jernd.bsky.social · 27d

It's even worse than it seems because the most popular CAD packages use just a handful of CAD kernels. The prices of these CAD packages simply can't go below a certain number due to the cost of licensing the kernel. The Plasticity dev has talked at length about this on YT.

1 2

Jern @jernd.bsky.social · 28d

FYI SW for makers creates files that cannot be opened by regular SW.

1

Jern @jernd.bsky.social · 28d

Have witnessed some of these issues as well. I have tried to adopt the approach that if (A) a potential dependency is not maintained by "professionals" and/or (B) is not absolutely essential to our application then it should not be adopted. Usually easier said than done.

Jern @jernd.bsky.social · Sep 15

The way people act lately is much more impersonal and to categorize others without much room for graceful reconsideration.

Jern @jernd.bsky.social · Sep 15

I hear what you are saying but I think the way you wrote your experience is key. Your friends asked you to do better. They presumably remained your friends and presumably gave you space to reflect and implement it. That's not really how people act (especially online) these days. 1/2

1

Jern @jernd.bsky.social · Sep 10

(or also hangar rods, which might be an even closer analogue with a larger diameter)

1 1

Jern @jernd.bsky.social · Sep 10

I wonder how the cost of curtain rods might compare?

1 1

Jern @jernd.bsky.social · Sep 3

Designed and rendered a measuring scoop using #build123d and #blender respectively. The user inputs a target volume for the measuring scoop, and then scipy traverses the search space and finds a scoop with the matching volume. There is a lot of potential in this kind of design optimization approach!

1 5

Jern @jernd.bsky.social · Sep 1

Just imagine what would happen if they didn't like the actual content -_-

1