Skip to content
verletverletverlet

Environments

An environment is a machine verlet can run simulations on.

KindWhat it isStatus
LocalThe computer verlet runs on. Added automatically.available
RemoteAny Linux machine you can reach over SSH: a workstation, a GPU node, a cluster login node.available
CloudNodes started on a cloud account for a run and shut down after.planned
The environments page and an environment's detailsThe environments page and an environment's details

Ready, pending, failed

Section titled “Ready, pending, failed”

An environment is ready once at least one engine executable on it has been run and verified. Until then it is pending, with the reason shown. Failed means the last scan could not complete.

Scans

Section titled “Scans”

A scan records what the machine offers:

  • System: operating system, kernel, CPU, cores, memory, GPUs.
  • Toolchain: compilers, MPI launchers, CMake, make, and whether a module system is present.
  • Executables: every engine binary on the PATH, in ~/.local/bin, in the usual prefixes, in the scan paths you add, and in ~/.verlet/bin where verlet’s own builds go. Each is run to read its version, packages, compiler and MPI.

Scans run when an environment is added, when you press Rescan, and after a build finishes.

Tags and the default

Section titled “Tags and the default”

Tags label an environment; some you set, some the scan sets. One environment is the default: where checks run, where the agent tests its drafts, and whose executable the editor uses. Set as default changes it.

Remote environments

Section titled “Remote environments”

A remote environment is an SSH host. verlet uses your system’s OpenSSH, so anything ssh <host> accepts in a terminal works. On connect, verlet installs verletrc in ~/.verlet there and talks to it through a forwarded port. See Run on a remote machine.