If you submit cluster jobs with ClusterPilot, your finished runs can now record themselves in Fieldnotes with no extra command to run.

Turn it on once. ClusterPilot has a Fieldnotes setting, off by default. Switch it on, and each time a job finishes and its results have synced back to your machine, ClusterPilot logs the run for you. You can name the project the runs belong to, or let it use the working directory's name.

No network, no account, no waiting. ClusterPilot calls your local Fieldnotes install directly, which writes to the same database as if you had typed the command yourself. Nothing goes over the wire at job completion, so it works from a laptop on hotel wifi as happily as from the office.

Array jobs, one record per task. Each task drops a small parameters file beside its own outputs, those files travel home with the results, and your workstation records the lot in one pass. Thousands of tasks, one writer, no half-written database.

Neither tool needs the other. Fieldnotes never requires ClusterPilot, ClusterPilot never requires Fieldnotes, and if the Fieldnotes command is not installed, ClusterPilot simply carries on. Logging never fails a job.

How to turn it on, and what ends up in each record: fieldnotes.sh/docs/logging-with-clusterpilot