- Pythagoras Tree
- Cantor Dust
- Koch Curve
- Sierpinski Triangle (this)
- Dragon Curve
- Fractal Plant
Example 5 : Sierpinski Triangle
First, let’s define our L-System:
Since we have done a lot of the heavy lifting in the last post (recall the Path module we created), we actually don’t have much to do here.
The only thing of interest here is that both ‘A’ and ‘B’ mean “draw forward”, but need to be represented different for the growth rules.
As far as I know, (please correct me in the comments if I’m wrong about this) there is no way to handle both symbols using case..of here, e.g.
case sym of
‘A’ | ‘B’ –> …
similar to how one would do in F#:
match sym of
| ‘A’ | ‘B’ –> …
| ‘+’ –> …
| ‘–‘ –> …
Hence why I opted for a multi-way if statement here instead.
Here’s how it looks, feel free to try it out yourself via the live demo links below.
But wait, the L-System wikipedia page also mentions a second way to draw the Sierpinski Triangle:
So, let’s implemented this as well, as v2.
When I used the suggested 120 degrees, I got an upside-down triangle. So instead, I used –120 degrees here:
Yup, it’s basically a carbon copy of the first version, except for a different value for angle plus different symbols.
Why are the examples not consistent with the choice of symbols for “draw forward”? One wonders…
Anyhow, here’s how it looks, which you can also try out via the live demo links below.
Use LEFT and RIGHT arrow keys to evolve/devolve the L-System.
Next : Dragon Curve
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong