Create a machine file Start from the closest configuration template, change the few values you actually know, download the file.

Nothing on this page is uploaded. The file is built inside your browser and validated live by the local engine. The CSP connect-src is 'self', so this page is technically incapable of sending data to any server.

Every value in a template is inferred from a machine class; not one of them comes from your machine. Change only the ones you actually know and leave the rest — each one you fill in is one assumption fewer. The parameter number next to each field is where to find it on the machine's parameter screen.

The resulting file

Below is exactly what will be downloaded. It updates as you edit and is validated by the engine. You cannot download it while validation fails — so you will never end up with a file the engine cannot read. The header lists the fields you changed, so later you can tell which values are real and which are still the template's assumptions.



Next

  1. Load the downloaded .toml on the cycle time estimate page with "Load machine file". Every real value you put in is one assumption the result no longer depends on.
  2. The same file works with the CLI and the desktop version: nccs estimate program.nc --machine your-machine.toml.
  3. Files produced here are still recorded as family defaults for calibration source — even after you change values, this page has no way to tell which ones you looked up and which ones you guessed. See the disclaimer for what raises that level.