Skip to content

SEP 51: one rule for the saved planes and the end of a run #846

Open

Description

@jtravs

Tracking issue for SEP 51 (docs/dev/seps/sep-0051-save-planes.md).

Every route takes the same pair: n_save (a count including z = 0, default 201) or save_planes (positions), never both. A bare number in save_planes is refused with a hint, and the run's length is the upper limit that decides how far it goes: the route's length, or grid.length on object routes.

It came out of #533, where a recipe's save_planes = 80 on an object route is read as one plane at 80 m. Investigating that showed that no route ties the run's end to its length: the run ends at its last saved plane.

The SEP lists seven open questions (Q1–Q7) for the maintainer. #843 (draft) will be superseded by the SEP's implementation.

Refs #533

Activity

  1. added
    priority: mediumReal work that should not wait long
    area: interfacesprop_*, Simulation, defaults and public names
    sepTracks an enhancement proposal (SEP)
    on Nov 15, 2026
  2. jtravs commented on Nov 15, 2026

    @jtravs
    ContributorAuthor

    Accepted in #847. Implementation: draft PR #851 on feature/sep-0051-save-planes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: interfacesprop_*, Simulation, defaults and public namespriority: mediumReal work that should not wait longsepTracks an enhancement proposal (SEP)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions