Application guide

Projects, backup and recovery

Treat the project as a research record while retaining independent copies of raw data, exports and important reports.

What a project retains

A .qpls archive can retain data references, authored model objects, saved coordinates, method recipes, completed results, reports and provenance. Technical identities remain internal even when ordinary Results show researcher-facing labels.

Temporary samples

A packaged sample opens immediately as a temporary copy and can be calculated without first choosing Save editable copy. When closing, choose whether to retain it. If retained, select a writable destination once.

Saving and reopening

  1. Save before a long calculation or structural edit.
  2. Wait for the completed result to be persisted before closing.
  3. Close QuickPLS, reopen the exact project, and confirm the result selector and report.
  4. Do not replace a project while another application or process is writing it.

Backup practice

Keep dated project copies in an institutionally approved location. Retain the raw source file, data-cleaning record, exported tables and the installer checksum used for the analysis. Test a restore before relying on the backup.

Historical projects

Open older archives in a copy and review release notes before saving. Derived presentation views may improve without rewriting the canonical result. Never overwrite the only historical project when testing a newer release.

Recovery

If a result cannot be reconciled with the current saved project state, stop editing, preserve the file, reopen the exact project and retry the documented action. For persistent failures, report the version, project history and privacy-safe reproduction steps.