mirror of
https://github.com/bspeice/speice.io
synced 2024-12-22 16:48:10 -05:00
196 lines
6.4 KiB
Plaintext
196 lines
6.4 KiB
Plaintext
---
|
|
slug: 2024/11/playing-with-fire-transforms
|
|
title: "Playing with fire: Transforms and variations"
|
|
date: 2024-11-15 13:00:00
|
|
authors: [bspeice]
|
|
tags: []
|
|
---
|
|
|
|
Now that we have a basic chaos game in place, it's time to spice things up. Transforms and variations create the
|
|
shapes and patterns that fractal flames are known for.
|
|
|
|
<!-- truncate -->
|
|
|
|
:::note
|
|
|
|
This post uses a set of [reference parameters](../params.flame) to demonstrate a working
|
|
implementation of the fractal flame algorithm. If you're interested in tweaking the parameters,
|
|
or generating your own art, [Apophysis](https://sourceforge.net/projects/apophysis/)
|
|
can load that file and gives full control over the image.
|
|
|
|
:::
|
|
|
|
## Transforms and variations
|
|
|
|
:::note
|
|
|
|
This post covers section 3 of the Fractal Flame Algorithm paper
|
|
|
|
:::
|
|
|
|
import CodeBlock from '@theme/CodeBlock'
|
|
|
|
We previously introduced transforms as the "functions" of an "iterated function system," and showed how
|
|
playing the chaos game leads to an image of Sierpinski's Gasket. Even though we used simple functions,
|
|
the image it generates is exciting. But it's still not nearly as exciting as the images the Fractal Flame
|
|
algorithm is known for.
|
|
|
|
This leads us to the first big innovation of the Fractal Flame algorithm: using non-linear functions
|
|
for the transforms. These functions are known as "variations":
|
|
|
|
$$
|
|
F_i(x, y) = V_j(a_i \cdot x + b_i \cdot y + c_i, d_i \cdot x + e_i \cdot y + f_i)
|
|
$$
|
|
|
|
import variationSource from '!!raw-loader!../src/variation'
|
|
|
|
<CodeBlock language="typescript">{variationSource}</CodeBlock>
|
|
|
|
Variations, labeled $V_j$ above, are functions just like transforms (we use $j$ to indicate a specific variation).
|
|
They take an input point $(x,y)$, and give an output point. However, the sky is the limit for what variation functions do in between
|
|
input to output. The Fractal Flame paper lists 49 different variation functions,
|
|
and the official `flam3` implementation supports [98 different functions](https://github.com/scottdraves/flam3/blob/7fb50c82e90e051f00efcc3123d0e06de26594b2/variations.c).
|
|
|
|
To draw our reference image, we'll focus on four variations:
|
|
|
|
### Linear (variation 0)
|
|
|
|
This variation is dead simple: just return the $x$ and $y$ coordinates as-is.
|
|
|
|
$$
|
|
V_0(x,y) = (x,y)
|
|
$$
|
|
|
|
import linearSrc from '!!raw-loader!../src/linear'
|
|
|
|
<CodeBlock language={'typescript'}>{linearSrc}</CodeBlock>
|
|
|
|
:::tip
|
|
|
|
In a way, we've already been using this variation! The functions that define Sierpinski's Gasket
|
|
apply the affine coefficients to the input point, and use that as the output point.
|
|
|
|
:::
|
|
|
|
### Julia (variation 13)
|
|
|
|
This variation is a good example of the non-linear functions the Fractal Flame Algorithm introduces.
|
|
It still receives an input point $(x, y)$, but does some crazy things with it:
|
|
|
|
$$
|
|
\begin{align*}
|
|
r &= \sqrt{x^2 + y^2} \\
|
|
\theta &= \text{arctan}(x / y) \\
|
|
\Omega &= \left\{
|
|
\begin{array}{lr}
|
|
0 \hspace{0.4cm} \text{w.p. } 0.5 \\
|
|
\pi \hspace{0.4cm} \text{w.p. } 0.5 \\
|
|
\end{array}
|
|
\right\} \\
|
|
|
|
V_{13}(x, y) &= \sqrt{r} \cdot (\text{cos} ( \theta / 2 + \Omega ), \text{sin} ( \theta / 2 + \Omega ))
|
|
\end{align*}
|
|
$$
|
|
|
|
import juliaSrc from '!!raw-loader!../src/julia'
|
|
|
|
<CodeBlock language={'typescript'}>{juliaSrc}</CodeBlock>
|
|
|
|
### Popcorn (variation 17)
|
|
|
|
Some variations rely on knowing the transform's affine coefficients; these are known as "dependent variations."
|
|
For the popcorn variation, we use the $c$ and $f$ coefficients:
|
|
|
|
$$
|
|
V_{17}(x,y) = (x + c \cdot \text{sin}(\text{tan }3y), y + f \cdot \text{sin}(\text{tan }3x))
|
|
$$
|
|
|
|
import popcornSrc from '!!raw-loader!../src/popcorn'
|
|
|
|
<CodeBlock language={'typescript'}>{popcornSrc}</CodeBlock>
|
|
|
|
### PDJ (variation 24)
|
|
|
|
Some variations have extra parameters that the designer can choose; these are known as "parametric variations."
|
|
For the PDJ variation, there are four extra parameters we can choose:
|
|
|
|
$$
|
|
p_1 = \text{pdj.a} \hspace{0.2cm} p_2 = \text{pdj.b} \hspace{0.2cm} p_3 = \text{pdj.c} \hspace{0.2cm} p_4 = \text{pdj.d} \\
|
|
V_{24} = (\text{sin}(p_1 \cdot y) - \text{cos}(p_2 \cdot x), \text{sin}(p_3 \cdot x) - \text{cos}(p_4 \cdot y))
|
|
$$
|
|
|
|
import pdjSrc from '!!raw-loader!../src/pdj'
|
|
|
|
<CodeBlock language={'typescript'}>{pdjSrc}</CodeBlock>
|
|
|
|
## Blending
|
|
|
|
Now, one variation is fun, but we can also combine variations in a process called "blending."
|
|
Each variation receives the same $x$ and $y$ inputs, and we add together each variation's $x$ and $y$ outputs.
|
|
We'll also give each variation a weight (called $v_{ij}$) that changes how much it contributes to the transform:
|
|
|
|
$$
|
|
F_i(x,y) = \sum_{j} v_{ij} V_j(a_i \cdot x + b_i \cdot y + c_i, \hspace{0.2cm} d_i \cdot x + e_i \cdot y + f_i)
|
|
$$
|
|
|
|
The formula looks intimidating, but it's not hard to implement:
|
|
|
|
import blendSource from "!!raw-loader!../src/blend";
|
|
|
|
<CodeBlock language={'typescript'}>{blendSource}</CodeBlock>
|
|
|
|
With that in place, we have enough to render a first full fractal flame. We'll use the same
|
|
chaos game as before, but use our new transforms and variations to produce a dramatically different image:
|
|
|
|
:::tip
|
|
This image is interactive! The sliders change the variation weights ($v_{ij}$ parameters)
|
|
so you can design your own image.
|
|
|
|
Try using the sliders to find which parts of the image each transform controls.
|
|
:::
|
|
|
|
import {SquareCanvas} from "../src/Canvas";
|
|
import FlameBlend from "./FlameBlend";
|
|
|
|
<SquareCanvas><FlameBlend/></SquareCanvas>
|
|
|
|
## Post transforms
|
|
|
|
Post transforms introduce a second affine transform, this time _after_ variation blending.
|
|
We'll use introduce some new variables, but the post transform function should look familiar by now:
|
|
|
|
$$
|
|
\begin{align*}
|
|
P_i(x, y) &= (\alpha_i x + \beta_i y + \gamma_i, \delta_i x + \epsilon_i y + \zeta_i) \\
|
|
F_i(x, y) &= P_i\left(\sum_{j} v_{ij} V_j(x, y)\right)
|
|
\end{align*}
|
|
$$
|
|
|
|
import postSource from '!!raw-loader!./post'
|
|
|
|
<CodeBlock language="typescript">{postSource}</CodeBlock>
|
|
|
|
The image below starts with the same initial transforms/variations as the previous fractal flame,
|
|
but allows modifying the post-transform coefficients.
|
|
|
|
<details>
|
|
<summary>If you want a challenge...</summary>
|
|
|
|
Challenge 1: What post-transform coefficients will give us the previous image?
|
|
|
|
Challenge 2: What post-transform coefficients will give us a _mirrored_ image?
|
|
</details>
|
|
|
|
import FlamePost from "./FlamePost";
|
|
|
|
<SquareCanvas><FlamePost/></SquareCanvas>
|
|
|
|
## Final transforms
|
|
|
|
import chaosGameFinalSource from "!!raw-loader!./chaosGameFinal"
|
|
|
|
<CodeBlock language="typescript">{chaosGameFinalSource}</CodeBlock>
|
|
|
|
import FlameFinal from "./FlameFinal";
|
|
|
|
<SquareCanvas><FlameFinal/></SquareCanvas> |