23.02.2014 Views

Shape

Shape

Shape

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

284 II Seeing How It Works<br />

applies in the usual way to define a series of shapes<br />

C Þ ðC<br />

tðAÞÞ þ tðBÞ Þ Þ D<br />

that starts with the shape C and finishes with the shape D. When the rule A fi B is<br />

tried, a transformation t of A is taken away and the same transformation t of B is added<br />

back. But this is only the algebraic mechanism for applying the rule. What’s interesting<br />

about the series is what I can say about it as a continuous process, especially when<br />

parts are resolved in surprising ways. For example, I can calculate so<br />

to turn a pair of touching chevrons into a pair of squares and back again, so that the<br />

pair of chevrons is reflected in between. The rule<br />

that translates a chevron, and the rule<br />

that translates a square, are used for this purpose. It looks hard—chevrons and squares<br />

stay the same when they’re moved—but it works. What parts do I need to account for<br />

the change, so that there’s no break or inconsistency? How are the parts the rules pick<br />

out related? When do chevrons become squares, and vice versa? What does it mean for<br />

this process to be continuous?<br />

I’m going to build on a configurational (combinatorial) idea that’s part of normal<br />

experience to answer these questions. It’s the very idea I’ve been against as a way of<br />

handling shapes to calculate. Still, the idea works when it comes to describing what<br />

happens as rules are applied. Keep this foremost in mind—there’s a huge difference between<br />

describing shapes and calculating with them. The latter doesn’t depend on the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!