If we do the top of the bird on the T side, we get a different design and arrangement. It is still a TGTG type because the Heesch identification always begins with a T if there is a T side. (If there is no T side, it will begin with a C if there is a C side. The other sides follow in clockwise order.)
Another variant that looked promising was taking the hexagonal TG1G2TG2G1 type and drop the legs on one of the G edges rather than on the T edge. My limited playing with it was disappointing and not worth developing.
Finally, the pentagon type CG1G2G1G2 in the last post had the C side placed on the tail. It could also be placed on the bill, as below.
Sometimes the end result hides the TesselManiac! starting point. The pattern below looks like TGTG. However, it was created using a hexagonal TG1G2TG2G1 type. The lines were manipulated so that one of the G pairs was eliminated.
The stork pattern below appears to be a TG1G2TG2G1 type, but it was constructed using a TGTG type in TesselMania. (It was done in 2012.)
In the original posts about these tessellations (which this and another post replaced) I did not pay enough attention to that possibility that the starting point in Tesselmaniac might not identify the final result. I originally used the design below as an illustration of TGTG, but it touches six adjacent birds, so it is more correctly labeled a type TG1G2TG2G1.
My original example of a CGCG type also touched six others and should be classified as CG1CG2G1G2
Also a CG1CG2G1G2 type is the example originally presented as G1G2G1 and built from that starting point in TesselManiac!.
The example I gave originally for a pentagonal CG1G2G1G2 type was constructed in TesselManiac! from that type, but I overlapped lines on the bills to get what is actually a CG1CG2G1G2 type.
I have learned a lot about Heesch types from this exercise and am beginning to get comfortable with the terminology. I corrected a lot of mistakes in these revisions of the original posts and hopefully have not left or introduced any major ones.
(Revised 02/20/2015)
No comments:
Post a Comment