Front View of a #Peripteral (#Sexastyle) #Colonnade with #IonicColumns arranged in #Eustyle #intercolumniation. Ever since prehistoric architects at #Stonehenge designed rock columns and labored to lift the heavy rocks atop them, humanity has been fascinated with columns and entablatures, whether they were known by that name or not, and the designs have continued to evolve. #Vitruvius described five classes of temples, designated as follows: "#pycnostyle, with the columns close together; #systyle, with the intercolumniations a little wider; #diastyle, more open still; #araeostyle, farther apart than they ought to be; #eustyle, with the intervals apportioned just right." So, what does it mean to have "intervals apportioned just right?" Aside from the subjective aesthetic criteria mentioned in https://pixelfed.social/p/Splines/802974815166948953, such as avoiding columns that "look thin and mean" and shafts that "look swollen and ungraceful," there were practical considerations, such as the gap being too wide to support heavy stone entablatures. There was also the practical matter with intercolumniation that was noo narrow. "When the [temple] matrons mount the steps for public prayer…, they cannot pass through [narrow] intercolumniations with their arms about one another, but must form single file; then again, the effect of the folding doors is thrust out of sight by the crowding of the columns, and likewise the statues are thrown into shadow; the narrow space interferes also with walks round the temple." So, intercolumniations of 2 column diameters (4µ) or less, as in #pycnostyle and #systyle, were considered too narrow. Likewise 3 column diameters (6µ) or more, as in #diastyle and #araeostyle, were too wide. The consensus sweet spot was 2.25 diameters (4.5µ) between column shafts at the bottom (6.5µ axis-to-axis), except for the two middle columns where the spacing was 3 column diameters (8µ from axis-to-axis). The image shows this variable intercolumniation.
@charlesrkiss "there is an ideal range of values… the largest span… would determine the remaining openings. And this would depend on the material strength." Exactly. Now we can model #elasticity using #HookesLaw (deformation is directly proportional to the deforming force or load — small displacements of a material's constituent molecules, atoms, or ions from normal positions is also proportional to the force that causes the displacement) and #YoungsModulus (measure of the ability of a material to withstand deformation when under tension or compression). Architects back then didn't know those, and had to rely on costly and sometimes catastrophic experimentation lasting years or decades. #Vitruvius wrote, "With regard to burnt brick, nobody can tell offhand whether it is of the best or unfit to use in a wall, because its strength can be tested only after it has been used on a roof and exposed to bad weather and time—then, if it is good it is accepted. If not made of good clay or if not baked sufficiently, it shows itself defective there when exposed to frosts and rime. Brick that will not stand exposure on roofs can never be strong enough to carry its load in a wall. Hence the strongest burnt brick walls are those which are constructed out of old roofing tiles." It is implicit that roofs sometimes had to collapse for architects to learn that the material or the design dimensions had to be rejected.
charlesrkiss
Thank you again for this excellent documentation! I have not previously seen or imagined any stories on stone "deformation," or any reporting on #creep analysis across a period of centuries. Here is a question: Extend this idea of stone deformation not over hundreds of years, but over THOUSANDS of years, on the pyramids of Eygpt, and other historic monoliths. Given all the purported "refined shaping" of stone to incomprehensible tolerances, could you imagine the super fine spacing between these stones were actually due to creep, and not craftsmanship — creep on the order of 1-2 mm per 1000 years? What would be a good approximation on such stones, in your opinion? It's probably not zero.