Skip to content

Learn

This is the catalogue of teaching and training material that uses GLACIER tools.

GLACIER is developed inside a university department, and a good deal of it exists because it is used to teach — manufacturing systems, cyber-physical systems, control software engineering. This section is where that material is published as it becomes publicly available.

Attending the FDL 2026 Summer School?

The GLACIER hands-on session has its own preparation page: what to install, what to download, and how to check that your laptop is ready before the session starts.

Prepare for FDL 2026

The catalogue is being populated

Several of the categories below have no public entries yet. Rather than list placeholders, each page says what it is for and what a published entry will look like. Nothing here links to a resource that does not exist.

  • Tutorials

    Step-by-step, self-paced material: build something with GLACIER from beginning to end.

    Tutorials

  • Labs and exercises

    Hands-on sessions and exercise sets, usually taught alongside a course.

    Labs and exercises

  • Lectures

    Slide decks and recorded talks on the ideas behind GLACIER.

    Lectures

  • Events

    Preparation pages for sessions taught in person at conferences and summer schools.

    Events

Start here instead

If you are looking to learn the tools rather than take a course, the fastest route today is the documentation itself:

  1. What is GLACIER? — the problem and the approach, in about five minutes.
  2. Architecture — how the pieces fit together.
  3. Connecting to a link — the smallest Frost program that does something.
  4. Invoking a method and Subscribing to a variable — the two interaction patterns everything else is built from.
  5. frost-template — start your own project from a working skeleton.

Contributing a resource

This site catalogues resources; it does not host them. A lecture lives in whatever repository or archive its author publishes it to, and the entry here points at it.

Adding one means editing a single Markdown file — docs/learn/tutorials.md, docs/learn/labs.md or docs/learn/lectures.md — and adding a section following the pattern already on the page. No frontend code is involved. An event preparation page is the one exception: it is a new file under docs/learn/events/, plus one line in nav:.

The only rule is the one stated above: an entry must point at something that exists and is publicly reachable. A resource that is planned, or that is restricted to enrolled students, can be described as such in prose, but must not be presented as a link a visitor can follow.