No hubris is greater or more despised by the gods than that of a man who believes he has written a robust curve offsetting algorithm.
My offsetting algorithm is still giving me problems, but I do feel slightly better that when I tried the latest edge-case in #Rhino3D to see how they handle it I get exactly the same result as from my own crappy code:
If you can't be right, at least be wrong in company.
In fairness to both myself and McNeel; it's not entirely obvious what the correct behaviour here actually is. When you get right down to it, what exactly constitutes an 'offset curve' is a bit fuzzily defined and there's several ways of approaching it.
Fixed it! Stay tuned to hear how the horrible hacky bodge that I used comes back to bite me in the butt in a few days...
• • •
Missing some Tweet in this thread? You can try to
force a refresh
This thread by @eng_mclare has (deservedly) got a lot of attention and as it chimes with a lot of what we've been discussing in @ramboll_uk about #skills, retention and the need to '#digitalize' in #AEC I thought I'd share some thoughts on how we can do that. THREAD ALERT! 1/
You can consider this thread a sequel to my talk on 'Computational Design at Scale' at the @IStructE last year: . This is what we need to do at an *even bigger* scale. All opinions my own etc. 2/
Let's take it as-read that the industry *needs* to digitalize, although I'm very aware that there are still quite a few... um... 'more experienced' engineers who might still wish to debate that. They are, however, decreasing in number one way or the other. 3/
This work depicts the time Marie Antoinette took her pet rocks on a picnic. The Eiffel Tower in a bottle represents the bottled-up resentment of the Parisian lower classes. The grapes represent grapes.
I started with no plan this year other than to create an 'analogue' #roguelike (i.e. one without the typical grid-based movement). Every other design choice stemmed from what was most fun or (as I didn't have much free time this week) easiest to implement!
Originally I went for a more expressly turn-based I-go-you-go system (a bit like Worms), but this was a bit slow and tedious so I dialled that back to a more SuperHot-like everything simultaneous time-stops-when-you-do mechanic.
Interesting event on @speckle_works tonight at @ArupGroup. It seems like a really powerful platform, though to be honest I think it suffers from the same problem @flux_io had in that it doesn't *by itself* solve a major pain point many people have.
Where it adds value is when other tools that *are* intrinsically useful are built on top of it. Emphasis: tools plural. Just one useful thing? No value. Two useful things? Might as well have connected them directly. Three useful things? Now we're starting to get going...
All platforms require a 'killer app'. The tricky thing for connection platforms like @speckle_works and @flux_io is that they needs *at least 3* killer apps before they're actually worth using, which is a big ask (especially on the first two of those, which have to take a risk).
We're recruiting! We currently have three different positions open in the @ramboll_uk Computational Design/SiteSolve team. We're after:
A Computational Design expert to focus on development of SiteSolve, our suite of interactive generative design tools, creating new algorithms to generate and analyse building geometry: ramboll.wd3.myworkdayjobs.com/Experienced_Pr…