Skip to content
Ungewitter

Help

Teacher guide

Ungewitter needs no accounts and no server. An assignment is a link, a student’s answer is a link, and the checks run in the browser of whoever opens it.

Building an assignment

Open Write an assignment. An assignment has four parts, and everything you enter goes into its link; nothing is uploaded.

  1. A title and a brief: what the students should do, and why.
  2. A starting design: one of the book examples, a design of your own (paste its Studio link), or the Studio’s default church.
  3. Up to twelve checks, which the model evaluates on the design a student hands in:
    • Number of vessels and Choir polygon, for plan exercises;
    • Uses a chevet and Vault type (by vessel: nave, aisles or choir);
    • Nave height to width, the height to the vault crown over the clear width;
    • Kern rule of 1890: the line of thrust stays in the kern of every outer buttress;
    • Buttress depth, as an upper limit, wall included;
    • Geometric safety factor, after Heyman, with the buttress cracked.
  4. The link: copy it and send it to your students by e-mail, in your course page or on a slide.

Try the checks on the starting design before you share it. A good assignment starts with some checks failing, so that the students have something to find. Mixing the 1890 checks with Heyman’s factor makes them meet the two methods where they disagree. What cannot be checked automatically (a drawing, an argument) you ask for in the brief, as a sentence or an export to hand in with the link.

The builder keeps your work in its own address, so a bookmark brings it back. Every assignment, including the ones below and the examples, has an Edit a copy link that opens it in the builder.

A semester in 24 lessons

The 24 lessons fit a semester of 15 weeks with one session a week, grouped so that each unit ends in the Studio. Each lesson has live figures and opens the Studio or the Lab at the point it discusses; glossary terms explain themselves on hover. Take the units in any order after the first two; the late-Gothic unit needs the plan unit.

  1. Weeks 1–2

    Arches and the line of thrust

  2. Weeks 3–5

    Plan, bay and choir

    Assignment 1 fits here.

  3. Weeks 6–8

    Holding the vault up, by the rules of 1890

  4. Weeks 9–10

    Modern statics

    Assignment 2 fits here.

  5. Weeks 11–12

    Elevation and detail

  6. Weeks 13–14

    Late Gothic and the craft

    Assignment 3 fits here.

  7. Weeks 15

    Reading buildings

Three ready-made assignments

Three assignments to use as they are or to edit. Each starts from a design that does not yet pass all its checks, and each can be solved with the Studio’s own controls.

  1. 1. A first basilica

    Plan a three-aisled basilica with a 5/8 choir. Vault the nave in sexpartite bays, make the nave between 2.2 and 3 times as high as it is wide, and keep the line of thrust in the kern of every buttress.

    • The church has 3 vessels.
    • The choir closes in the polygon 5/8.
    • Every straight bay of the nave has a sexpartite vault.
    • The nave is between 2.2 and 3 times as high (to the vault crown) as it is wide (clear).
    • Every buttress keeps the line of thrust in the kern of every joint under every load case (1890).

    Open as a student →Edit a copy

  2. 2. Holding back the thrust

    Example II of the book sets the hall church on slender round piers. Reach a geometric safety factor of 2 in every outer buttress, keep the kern rule of 1890, and make no buttress deeper than 2.6 m, wall included. Say in one sentence which change did it.

    • Every buttress keeps the line of thrust in the kern of every joint under every load case (1890).
    • Every buttress has a geometric safety factor of at least 2 (Heyman, cracked).
    • No buttress is deeper than 2.6 m, wall included.

    Open as a student →Edit a copy

  3. 3. A late-Gothic hall church

    Start from the hall church of Example I. Give the nave a net vault and the aisles a star vault, keep three vessels and the kern rule of 1890. Then compare the load on the abutments with the quadripartite vaults you started from.

    • The church has 3 vessels.
    • Every straight bay of the nave has a net vault.
    • Every straight bay of the aisles has a star vault.
    • Every buttress keeps the line of thrust in the kern of every joint under every load case (1890).

    Open as a student →Edit a copy

How students hand in

  1. The student opens the assignment link and reads the brief and the list of checks.
  2. Open the starting design in the Studio loads it; they work on it there as long as they like.
  3. They copy the Studio’s address (it ends in #d=…), paste it into the assignment page and press Check my design. The results appear at once, each with what the model measured and the findings behind a failure, and they can go back and improve the design.
  4. When they are done, the address of the assignment page holds both the assignment and their design: that address, Link to this result, is the hand-in. They send it to you the way you collect work anyway: by e-mail, in your learning platform, in a shared document. Print the result prints it, or saves it as a PDF, without the site’s menus.

Checking without accounts

Open a hand-in link and the checks run again, in your browser, on the design in the link. Nothing is stored on a server and there are no accounts: the link is the whole record. Results cannot be edited into a link, because they are not in it; only the design is, and the model judges it afresh each time.

  • Follow the result’s links into the Studio to see the design itself, in every view, with its findings.
  • Gather the class’s designs with Add to collection in the Studio, and share the whole set back as one collection link for a review session.
  • Links survive updates of the site: a design made this semester still opens next year, migrated to the current format.
  • The automatic checks are a floor, not a grade. They tell you that a design meets its numbers; whether the student understood why is still for you to ask.

The part of a link after # never reaches our server, so a student’s work stays between the student and you. See privacy. For the controls themselves, see Help.