Tutorials: learn Konjugate by doing it, inside the app

November 15, 2026

Reading about a feature and getting it to work are different things. Parameter tuning, controllers, data sources and the live twin are all explained in these docs, but until now nothing in the app walked you through them. Tutorials do that. There are 23 of them, each about one feature and a few minutes long, and each one happens in the real interface, on a model you can keep.

Where to find them

Look for the Tutorials button on the left edge of the window, just above Help & feedback. It is a book icon, and it shows its name when you point at it. On a phone, where that edge is hidden, the menu lists Tutorials instead.

The empty canvas, with a book icon at the bottom of the left edge, above the feedback icon
The book icon is Tutorials. It sits in the same place in the desktop app and in the web edition.

It opens a list with a search field at the top, ready for typing.

The Tutorials list, with a search field and entries grouped under Start here and Modelling
Each entry says what you will be able to do, how long it takes and where it starts. The tick beside the first one means it has been finished.

Each entry gives a title, one sentence on what you will be able to do afterwards, roughly how many minutes it takes and where it starts, either from an empty canvas or from one of the shipped examples. With nothing typed, the list is grouped under Start here, Modelling, Results, Tuning and calibration, Control and Data and twins. A tutorial you have finished gets a Done tick but never moves or disappears, so you can take it again.

Searching

Type and the list narrows as you go. A search looks at each tutorial's title, its sentence, its tags and the name of the example it starts from. Every word you type has to match, and a title match ranks above a tag match, which ranks above a match anywhere else. So you can search for the thing you want to do or for what you already have:

  • pid finds Tune a controller.
  • measured data finds the calibration tutorial and the one on replaying a lab's log.
  • Tank Calibration finds the two tutorials that start from that example.
The list searched for the word calibrate, showing three matching tutorials
A search matches titles first, then tags, then the rest. The third result matches on a tag.

Nothing you type is sent anywhere. The search runs in the app.

Starting from an example

Most tutorials do not start from an empty canvas. A person learning parameter tuning should be tuning a model, not first building one, so these start from an example Konjugate already ships. Pressing Start loads that example the way the Examples menu does: if your open project has unsaved changes you are asked first, and the example opens as an unsaved copy, so the shipped file is never touched and whatever you make is yours to keep.

It also works the other way round. On the desktop, an example that has tutorials shows a card for each at the top of its guide, with a Take the tutorial button. Tank Calibration has two, one for calibrating and one for optimising, and Position Controlled Joint has three.

What a card asks of you

Let us follow Calibrate a model against measured data, which starts from the Tank Calibration example. A water tank is warmed by a heater and loses heat to the room, but two of its numbers are only guesses: how much heat it takes to warm the tank and how fast it leaks heat away. The tutorial fits both to eight hours of measured temperatures.

The first card, titled Calibrate a model against measured data, with Leave tutorial and Start buttons, over the Tank Calibration model
The first card says what you will do and why. Leave tutorial is always one click away.

After Start, each card gives one step, says why, and rings the control to use. The label above the title counts the steps, six in this one. The next card appears when you have done the step, not when you press a button.

Step 2 of 6, Add the measurements, with a ring around the Choose CSV file button in Parameter tuning
The ring marks the control. The card explains the file, and the link under the text downloads it to your Downloads folder.

This is a deliberate choice. Choosing a CSV file is part of what the tutorial teaches, so the card does not load the measurements for you. It gives you a link to download the file that ships beside the example, rings Choose CSV file and says what the file holds: a time column in seconds and a tankTemperature column. It also says that columns are matched to the model's states by name, which is exactly what you need to know when you come back with your own data.

The steps after that are to run the fit, apply the fitted values (which should land close to 209,000 J/K and 20 W/K, the numbers the measurements were made with), run the calibrated model for the eight hours and plot the tank's temperature.

Step 4 of 6, Keep the fitted values, with the fit finished and a ring around Apply fitted values
The fit is done and the card points at Apply fitted values. This screenshot came from using Skip this step on the two steps before it.

The card checks, so it can tell when you went wrong

Each step has a check on the model or the interface, and the card moves on only when the check holds. The checks ask about the change a step was for, not about the model in general. An example starts full, so "do two nodes exist" would mean nothing. The calibration tutorial asks whether the two parameters now differ from how the example came.

A check that held also keeps being watched. If you undo something an earlier step asked for, the card notices and offers to take you back to that step, so you do not get stuck three steps on with something missing.

Skip this step, or leave

Every step with something to do has two links beside it: Leave tutorial and Skip this step.

Skip this step does the step for you, through the page's own fields and buttons, as you would. It creates the node, runs the model and waits for it to end, loads the measurements or closes the results, so the steps after it find what they expect. If a skip cannot do its step, the card says so and stays where it is instead of moving on to a step that needs it. The skip is for when you already know a step or are stuck on it. A step you skipped is never reported as undone afterwards, because it was not yours to redo.

Leave tutorial closes it, and says that it can be taken again from Tutorials. Nothing is recorded about a tutorial you left part way. A finished one is remembered only as a Done tick, kept in the app's own settings on the desktop and in the browser's local storage in the web edition. Nothing about your tutorials is sent anywhere.

The 23 tutorials

The first, Build and run your first model, is the guided tour from the earlier post, now one tutorial among many. Its first-launch start and the Welcome window's card stay as they were.

Area Tutorials
Start here Build and run your first model
Modelling Build from components, Organise a larger model, Equations that do more, Write a relationship as a program, Ask the model assistant, Parameters and run settings, Lay out and dress a model, Fix an unstable model
Results Ask what if with branches, Keep and share your work, Take a model elsewhere, Extend Konjugate
Tuning and calibration Calibrate a model against measured data, Optimise towards a goal
Control Tune a controller, Steer a model by hand, Schedule changes during a run
Data and twins Discover equations from data, Replay a lab's data log, Run a live digital twin, Match your signals to the model, Refit a drifting twin

Fourteen of them play in both the desktop app and the web edition. Nine need the desktop app, because they need something the browser cannot give: a run that takes commands while it goes, checkpoints to fork from, the live twin's own window or the model assistant. The list is the same in both editions, and a tutorial the web edition cannot play is shown with "In the desktop app" in place of its Start button, so you can see what exists.

Some of the tutorials tie into posts you may have read:

Kept from going stale

Each tutorial is played the whole way by an automated test in the real interface, mixing steps done by hand with skips. A change to the interface that breaks a tutorial fails the build, so it is caught before you meet it. The tests also check that the names, ids and starting values the cards rely on are the examples' own. An example and its tutorial are one piece of content in two files, and changing one without the other fails a test.

What the tutorials do not cover

Every feature of the modelling and analysis workflow is taught somewhere. What is left out is housekeeping: Settings, the interface size, the diagnostics log, Help & feedback and new windows. A few features are named on a closing card instead of done as a step, because a step would need something you may not have: encrypted saving (a password of yours), an FMU used as a node (a plugin), MQTT and OPC UA sources (equipment or a script of yours) and installing a package from a file.

Try one

Press the book icon, type what you are curious about and start the one that matches. If you have never used Konjugate, start with the first one. It takes about three minutes and leaves you with a model of your own.

Follow Konjugate on LinkedIn for updates, or subscribe via RSS.

Comments