Recursion and Fractals
en.scratch-wiki.info
en.scratch-wiki.info
[1] https://www.youtube.com/watch?v=gB9n2gHsHN4
[2] https://en.wikipedia.org/wiki/List_of_fractals_by_Hausdorff_...
This is not a misconception. Self-similarity at all length scales is indeed a defining factor of fractals.
From that fact it _does_ follow that _most_ fractals have a non-integer fractal dimension. However it is absolutely not true that fractals have non-integral dimensionalities; for example the most famous fractal of them all, the Mandelbrot set, has an integer Hausdorff dimension of 2.
> Mandelbrot himself summarized it as "beautiful, damn hard, increasingly useful. That's fractals." More formally, in 1982 Mandelbrot stated that "A fractal is by definition a set for which the Hausdorff–Besicovitch dimension strictly exceeds the topological dimension." Later, seeing this as too restrictive, he simplified and expanded the definition to: "A fractal is a shape made of parts similar to the whole in some way." Still later, Mandelbrot settled on this use of the language: "… to use fractal without a pedantic definition, to use fractal dimension as a generic term applicable to all the variants".
(Note that the mention of dimension only requires one notion of dimension to exceed another, not that either dimension be non-integral!)
From this comment I would guess this is an alternate meaning of 'dimension' which captures one key property from the usual meaning (i.e. ratio of surface to interior space depends on dimension), but leaves out the rest.
Like is there a sense in which we can rotate onto a fractional axis or something like that?
Then if you want to make this intuition precise, you need to look into the box-counting dimension, and then the Hausdorf dimension.
There was a specific thing I was looking for in my original question which was to understand how related vs. arbitrary the shared term 'dimension' is.
I think I found an answer after browsing a few Wikipedia articles—but happy to be corrected if it doesn't sound right:
The usual notion of dimension that people think of is topological only; fractal dimension (i.e. Hausdorf dimension) is also concerned with metric properties. These metric properties are what creates the need/possibility for fractional measures.
In that case, the scenario I was considering with 'fractional axes/directions' is not implied by the fractal dimension concept: fractal dimension is dealing with new subject matter, not just an extension of the old concept to deal with real numbers.
That's the main distinction: the old notion doesn't care about roughness or changes in measurement at varied scales since it has nothing to do with metric properties.
The generalization from integers to reals in the actual values is not indicative of the relationship between the two concepts.
Which also nicely and conclusively shows why self-similarity is just a special case of things that have fractional dimension.
Pick a stick to measure the length of the curve. As you break it into smaller sticks, you can fit them in tighter niches within the curve, and your measure of the curve's length becomes greater and greater. In the case of the Koch curve, breaking your stick in 3 means you'll be able to measure a length 4 times greater.
I'm a system administrator for the international Scratch Wikis. While I haven't been that active recently, I'll try and answer any questions that people want to ask. :)
The CS teacher at a local high school switched to using Scratch as a casual introduction to programming, moving away from Alice (and previously, I believe, a straight jump into Java). They use it for a few weeks to begin each term. I can get their thoughts if you're interested?
There are several books, and Scratch itself provides many lessons and features for teachers, see this page: [1] At one point, Pursuitery held an introduction to coding "camp" with Scratch, and you can read about their lessons here: [2] I've had less experience with Scratch in education, so it's hard for me to comment on what materials are the most effective. However, there are educator groups that can give advice, see the Facebook group listed on [1].
If I can go on a winding tangent, and this applies stronger to elementary & middle school... I think two of Scratch's strongest appeals are its freedom and feedback. It's okay to experiment, try new things, and fail. And the debugging that occurs along the way, in a way helps students debug their own thought processes. Giving some creative leeway for students can help them help themselves. Many students who are introduced to Scratch, stick with it personally after the class ends.
In other words, it can be great to focus on teaching algorithms or concepts, but letting people learn through projects often helps make learning more engaging. It helps to show that computers are not just something you do stuff on, but are part of a broader culture. It can be another medium for self expression, as many people share art, games, stories, and other content regularly on Scratch.
A few ideas were taken from Mitchel Resnik's keynote at the 2016 conference, which talks about a mix of how Scratch is used and powerful ideas.[3]
[0] http://u.cubeupload.com/Choco31415/DSCN3966.jpg
[1] https://scratch.mit.edu/educators
[2] https://en.scratch-wiki.info/wiki/Scratch_in_the_Media/Pursu...
I've got lots of experience with kids with Scratch (via my kids, and running a Code Club and CoderDojo - the Raspberry Pi Foundation has quite a few projects) and went to this year's Scratch Europe conference. As well as the advantages of being a visual programming language (so younger kids who struggle with typing don't get frustrated, and no syntax errors!), it does make it extremely easy to do visual stuff, moving sprites etc. to do things like make games which means that kids can do fun stuff very quickly.
I do wish it made it a bit easier to introduce slightly more advanced programming concepts though. You have to do a lot of stuff via broadcasting messages and cloning which gets really messy when you try and do anything complicated, and although sprites are objects, it doesn't map as nicely onto conventional object-orientation as I would like for example.
Is there some more UI depth that I've missed on my first spin that allows more ergonomic usage?