Skip to content

Commit aece230

Browse files
jdaw1jdaw1
committed
Small aesthetic fixes
1 parent b1d25b9 commit aece230

File tree

6 files changed

+18
-12
lines changed

6 files changed

+18
-12
lines changed

‎.DS_Store‎

0 Bytes
Binary file not shown.

‎images/path15_bad.svg‎

Lines changed: 2 additions & 2 deletions
Loading

‎images/path15_good.svg‎

Lines changed: 2 additions & 2 deletions
Loading

‎text/c.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -247,14 +247,14 @@ And there are other positions for which holes or gaps have a unique completion,
247247

248248
### Exporting code ###
249249

250-
* There is occasional need to `sprintf()` to a string, for subsequent use. So [<kbd>exportTilings.c</kbd>](../C/exportTilings.c) creates `scratchString[]` of length 32767, which many export routines access with `extern char scratchString[];`.
250+
* There is occasional need to `sprintf()` to a string, for subsequent use. So [<kbd>main.c</kbd>](../C/main.c) creates `scratchString[]` of length 32767, which many export routines access with <code>extern&nbsp;char&nbsp;scratchString[];</code>.
251251

252252
* Some of the output files are large. There should be some effort to not enlarge them needlessly. In particular, the likes of &ldquo;<samp>1.000000000</samp>&rdquo; should be trimmed to &ldquo;<samp>1</samp>&rdquo;. This should not be done with scientific notation: if an _x_ or _y_ value is almost zero, then it should be &ldquo;<samp>0</samp>&rdquo; rather than &ldquo;<samp>-1.234567E-89</samp>&rdquo;. So there is a routine `stringClean()`, in [<kbd>stringClean.c</kbd>](../C/stringClean.c), which cleans a string in this style. Almost always, the string passed to this is `scratchString`.
253253

254254

255255
There are two very different types of export format.
256256

257-
* Those with `enum` `ExportFormat` values {`JSON`, `TSV`, `PS_data`} hold data from multiple tilings, for subsequent processing. In [<kbd>exportTilings.c</kbd>](../C/exportTilings.c) it loops over tilings, calling code in [<kbd>exportTiling.c</kbd>](../C/exportTiling.c). Each of these loops over arrays, so repeatedly calling code in [<kbd>exportPathStats.c</kbd>](../C/exportPathStats.c), in [<kbd>exportPath.c</kbd>](../C/exportPath.c), and in [<kbd>exportRh.c</kbd>](../C/exportRh.c). For `TSV`the passed item can be a `NULL` pointer, instructing that the header row be output.
257+
* Those with `enum` `ExportFormat` values {`JSON`, `TSV`, `PS_data`} hold data from multiple tilings, for subsequent processing. In [<kbd>exportTilings.c</kbd>](../C/exportTilings.c) it loops over tilings, calling code in [<kbd>exportTiling.c</kbd>](../C/exportTiling.c). Each of these loops over arrays, so repeatedly calling code in [<kbd>exportPathStats.c</kbd>](../C/exportPathStats.c), in [<kbd>exportPath.c</kbd>](../C/exportPath.c), and in [<kbd>exportRh.c</kbd>](../C/exportRh.c). For `TSV` the passed item can be a `NULL` pointer, instructing that the header row be output.
258258

259259
* Those with `enum` `ExportFormat` values {`PS_rhomb`, `PS_arcs`, `SVG_rhomb`, `SVG_arcs`} output something useful as-is. That is, an SVG can be viewed; a PostScript file can be distilled (using [Adobe Distiller](https://en.wikipedia.org/wiki/Adobe_Distiller) or [Ghostscript](https://en.wikipedia.org/wiki/Ghostscript)) into a PDF. For these, code in [<kbd>export_SoloTiling.c</kbd>](../C/export_SoloTiling.c) calls the appropriate one of [<kbd>export_PaintArcsPS.c</kbd>](../C/export_PaintArcsPS.c), [<kbd>export_PaintArcsSVG.c</kbd>](../C/export_PaintArcsSVG.c), [<kbd>export_PaintRhPS.c</kbd>](../C/export_PaintRhPS.c), [<kbd>export_PaintRhSVG.c</kbd>](../C/export_PaintRhSVG.c). Some SVG processing is in [<kbd>Smalls_SVG.c</kbd>](../C/Smalls_SVG.c).
260260

‎text/paths.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ In it:
8181

8282
Observe that the length of a long path varies as the square root of its area (which is a linear measure) to the power of ln(2)&#8239;/&#8239;ln(&phi;)&nbsp;&asymp;&nbsp;1.44042.
8383
That is, long paths are approximately 1.44 dimensional.
84-
(Trivially ln(2)&#8239;/&#8239;ln(&phi;)&nbsp;&NotElement;&nbsp;&Qopf;, but I don&rsquo;t know whether [algabraic](http://en.wikipedia.org/wiki/Algebraic_number).)
84+
(Trivially ln(2)&#8239;/&#8239;ln(&phi;)&nbsp;&NotElement;&nbsp;&Qopf;, but I don&rsquo;t know whether [algebraic](http://en.wikipedia.org/wiki/Algebraic_number).)
8585

8686
The observed data is consistent with, in a suffiently large tiling, the number of closed paths of each length being [geometrically distributed](http://en.wikipedia.org/wiki/Geometric_distribution), with decay
8787
&frac12;(3&nbsp;&minus;&nbsp;&radic;5) &asymp;&nbsp;0.381966.

‎text/physical_tiling.md‎

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -87,14 +87,20 @@ But it would be wrong.
8787
In a correct Penrose tiling, never do two parallel fats touch.
8888
That is, the following is forbidden.
8989

90-
<center><img align="center" width="384" height="144.29" src="../images/two_forbidden_fats.svg"></center>
90+
91+
<div align="center">
92+
93+
<img align="center" width="384" height="144.29" src="../images/two_forbidden_fats.svg"></center>
94+
95+
</div>
9196

9297
In the following the left diagram has five visible errors, so is a particularly obvious instance of the problem.
9398

94-
<center>
95-
<img align="center" width="192" height="201.7726" src="../images/path15_bad.svg"> &nbsp; &nbsp;
96-
<img align="center" width="192" height="201.7726" src="../images/path15_good.svg">
97-
</center>
99+
<div align="center">
100+
101+
<img align="center" width="192" height="201.7726" src="../images/path15_bad.svg"> &nbsp; &nbsp; <img align="center" width="192" height="201.7726" src="../images/path15_good.svg">
102+
103+
</div>
98104

99105
If two fats are parallel and touching, whether touching at an edge or a vertex, then this is an error, perhaps caused by mis&#8209;rotation of a round&nbsp;5 path.
100106

0 commit comments

Comments
 (0)