Projects

A project is a folder for related simulations — every run you start lives inside one. The project page is where you create new runs, browse and filter the ones you already have, and open their results. This page documents every control on it: what it does and when you would use it. The ⓘ next to each control links straight to its section here.

If you are new, the loop is simple: press + New Simulation, set up a powertrain, run it, then click the finished row to read the results. Everything else on this page just helps you organize a growing list of runs.

Project actions

The toolbar in the top-right of the project page holds the three project-level actions. The ⓘ beside them links here; each action also has its own section below.

• Edit — rename the project and edit its notes. Only changes the label/description, never the runs inside.
• Delete — permanently removes the project and every simulation, sweep, and dynamic run inside it. You are asked to confirm first; it cannot be undone.
• + New Simulation — starts a fresh powertrain run inside this project.

Related: + New Simulation · Edit · Delete

+ New Simulation

Starts a fresh powertrain simulation inside this project. You pick a propeller, motor, ESC, and battery for each rotor, set a throttle and the air conditions, then run — ThrustLab predicts the thrust, current, power, and efficiency you would measure on a bench.

When to use it. Any time you want to test a new combination of parts, or a new operating point for parts you have already tried.

Related: Type badge · Re-open exact inputs

Edit

Renames the project and edits its notes. This only changes the project's own label and description — it leaves every simulation inside it exactly as it was.

When to use it. When a project's name no longer matches what it has grown into, or you want to jot down what you were testing.

Delete

Permanently removes this whole project and every simulation, sweep, and dynamic run inside it. Because there is no undo, you are asked to confirm first.

When to use it. Only when you are sure you no longer need any of the runs in the project. To remove a single run instead, use Delete in that row's ⋯ menu.

Related: Delete a run

Search by name

Filters the list to runs whose name contains what you type. It searches names only — not results or inputs — so naming your runs clearly (e.g. "6S hover sweep") makes them easy to find later.

When to use it. When a project has many runs and you remember roughly what you called the one you want.

Rotors filter

Shows only runs that used a given number of rotors. It is handy when a project mixes single-motor bench tests with multi-rotor aircraft and you want to look at one group at a time.

When to use it. To compare like with like — for example, only your 4-rotor builds.

Type filter

Shows only one kind of run: Single (one operating point), Sweep (a range of points), or Dynamic (a flight over time). It pairs with the Type badge in the table so you can isolate, say, just your sweeps.

When to use it. When you only care about one run style and want the rest out of the way.

Related: Type badge

Solver filter advanced

Filters runs by the propeller solver that produced them. New runs all use ThrustLab's vortex-BEM solver — a Drela vortex-based blade-element model that closes the local inflow at each blade station. The filter still distinguishes older runs that recorded a different solver label.

When to change it. When a project mixes newer vortex-BEM runs with older runs computed under a different solver and you want to compare like with like.

Compare Selected

Opens a side-by-side comparison of the runs you have ticked. Select two or more completed runs, and ThrustLab lines up their thrust, power, and efficiency on one screen — the quickest way to decide between designs.

When to use it. After you have run a few candidate builds and want to pick a winner. The button appears once two or more completed runs are selected.

Star

Marks a run as a favorite so it stands out in a long list. Starring is purely organizational — it changes nothing about a run's inputs or results. Click the star again to unstar.

When to use it. To flag the runs you keep coming back to so they are easy to spot.

Status

Tells you where a run is in its life. Staged is parked until you dispatch it, Waiting has been handed to the server and is about to be picked up, Running is computing now, Completed is finished (click the row to open results), Failed stopped with an error, and Draft was saved but never started. Only completed runs can be opened or compared.

How to read it. A run you can open shows Completed; if it shows Failed, re-open its inputs to check what you entered. A Draft is yours to finish whenever. A Staged run never starts by itself — dispatch it from the run tray.

Related: Staged / Waiting · Open results · Continue editing

Staged / Waiting

The two pre-run states, split by whose move it is. Staged means the run is parked on your account — nothing happens until you dispatch it. Waiting means it has been handed to the server and a solver will pick it up in a moment.

How to read it. Staged = your action needed; Waiting = the server's turn. The status filter shows both under one Staged / Waiting option, since they are two sides of the same pre-run state.

Related: Status · Run all staged

Run all staged

Dispatches every staged run in the tray at once — the button shows the count, for example Run all staged (3). Runs with the same rotor configuration share solver warm-up when dispatched together, so batching them is faster than firing one at a time.

When to use it. After staging a batch of variations from the simulation form, fire them all in one click. Use Run selected (N) to dispatch only the rows you tick.

Related: Staged / Waiting

Clear finished

Removes finished rows — Completed, Failed, and Canceled — from the run tray. Clear finished (N) in the tray header clears them all at once; the × on a row clears just that one.

What it does not do. Clearing only tidies the tray. The runs themselves are untouched — every result stays in the project's runs table. Cleared rows stay cleared on this browser.

Related: Run all staged · Status

Type

Tells you what kind of run a row is. Single is one steady operating point, Sweep is a whole range of points (for example a throttle curve), and Dynamic is a flight that changes over time. The type decides which results page you get when you open it.

How to read it. Use it to scan a busy project — sweeps and dynamic runs carry richer results pages (plots, time-series) than a single point.

Related: Type filter

Open results

Opens the full results page for a finished run — the KPI strip, per-rotor breakdown, power-flow diagram, and thermals. It is the same thing as clicking a completed row directly, and it is only offered once a run has completed.

When to use it. To read a completed run's numbers. For drafts use Continue editing instead.

Related: Status

Re-open exact inputs

Loads this run's exact inputs back into a new simulation form so you can change one thing and run again. It always creates a brand-new run — your original is never modified — which makes it the safe way to explore "what if I bumped the throttle?"

When to use it. To iterate from an existing run, or to retry a failed one after fixing an input. Offered for completed, failed, and canceled runs.

Continue editing

Re-opens a draft — a run you saved but never started — back in the simulation form so you can finish setting it up and run it. It is shown only for draft rows.

When to use it. To pick up where you left off on a setup you saved for later.

Related: Status

Cancel

Stops a run before it finishes. For a sweep, any points already computed are kept and the rest are abandoned. It is offered while a run is staged or waiting; a running sweep or dynamic mission can also be cancelled (a running single-point finishes in seconds and cannot).

When to use it. To free up a worker slot or stop a long run you no longer need.

Delete a run

Permanently removes a single run from the project. There is no undo, so you are asked to confirm. To remove the whole project at once, use Delete in the page header instead.

When to use it. To tidy up a project once a run has served its purpose.

Related: Delete project