Resources
Software, people, and reference workflows.
Open scientific software is built by communities. This is where we connect those tools, the people behind them, and the engineering questions they answer — with every claim traced to a public source.
How it connects
From a plant component to a reproducible workflow.
- A plant componentStart from the Fusion Atlas chamber or heat-transfer system.
- An engineering questionTransport, deposition, coolant behaviour, thermal response.
- The softwareDocumentation, source, licence, citation and limits.
- The peopleWho built it, in what role, with the evidence.
- A reference workflowInputs, outputs, assumptions and what has been run.
- The HubWhere execution is offered, with its own operational status.
Try it from the Atlas plant explorer: pick the target chamber or the heat-transfer system and open its simulation resources.
Three labels, three different facts
What the labels mean.
Hub availability
Runs in the Hub · Hub beta · planned · reference
Whether the Morton Labs Hub offers automated runs of a tool today. An operational fact, not a judgement of the software.
Evidence
Listed · Upstream example · Morton reproduced · Benchmark assessed
What is known about a specific tool entry or reference case. Only a real run with retained outputs earns “Morton reproduced”; only a named benchmark with stated acceptance criteria earns “Benchmark assessed”.
Profile review
Editorial · Self-reviewed
Whether a person has actually reviewed their own profile. Every profile starts as an editorial profile written from public sources, and says so.