labcode 0.3.1__tar.gz → 0.4.0__tar.gz

{labcode-0.3.1 → labcode-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: labcode
-Version: 0.3.1
+Version: 0.4.0
 Summary: labcode -- a dialect wrapper over the Object-Flow Programming Language toolchain
 Author-email: Kazunari Kaizu <kwaizu@gmail.com>
 License-Expression: MIT
@@ -21,8 +21,8 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: ofplang-validate<0.3,>=0.2
-Requires-Dist: ofplang-schedule<0.6,>=0.5
-Requires-Dist: ofplang-run<0.7,>=0.6
+Requires-Dist: ofplang-schedule<0.9,>=0.8
+Requires-Dist: ofplang-run<0.8,>=0.7
 Provides-Extra: test
 Requires-Dist: pytest>=7.0; extra == "test"
 Requires-Dist: opentelemetry-sdk>=1.20; extra == "test"
@@ -143,7 +143,8 @@ described below.
 lc run <workflow> --env <env>
     [--boundary DOC] [-o OUT] [--boundary-out FILE] [--observation-out FILE]
     [--seconds-per-tick S] [--op-timeout S | --no-op-timeout] [--no-probe]
-    [--ignore-resources] [--trace] [--mission-id ID] [--object-ids seeded|real]
+    [--max-transport-legs N] [--ignore-resources] [--trace] [--mission-id ID]
+    [--object-ids seeded|real]
 ```
 
 - `<workflow>` — the portable v0 workflow: *what* happens.
@@ -176,6 +177,15 @@ lc run <workflow> --env <env>
   else 7200 real seconds. The two forms exclude each other.
 - `--no-probe` — ignore the environment's `x-labcode.probe` policies and treat every
   machine as reachable (§1.6). The documents are still validated.
+- `--max-transport-legs N` — how many transport activities one Object-bearing arc may
+  be carried in (schedule spec §6.4.1), joined by **relay** activities. It is 1 by
+  default: the single hop. Raise it where the transporter cannot reach an instrument
+  from where the plate is — a bench it serves from one position only, or a hand-off
+  station a plate has to cross — and the move is planned as the shortest chain between
+  the two spots instead of being reported unreachable. Only the fewest possible moves
+  are offered, so a plate one move away is never sent round by way of somewhere else.
+  This describes the laboratory's reach rather than tuning the loop, which is why it is
+  here and not among the replan knobs below.
 - `--ignore-resources` — switch the consumable model off. The environment's resource
   declarations are still checked for shape but none is applied, so a bench whose devices
   declare stocks nobody is tracking runs without the boundary saying what they held.

{labcode-0.3.1 → labcode-0.4.0}/README.md

@@ -99,7 +99,8 @@ described below.
 lc run <workflow> --env <env>
     [--boundary DOC] [-o OUT] [--boundary-out FILE] [--observation-out FILE]
     [--seconds-per-tick S] [--op-timeout S | --no-op-timeout] [--no-probe]
-    [--ignore-resources] [--trace] [--mission-id ID] [--object-ids seeded|real]
+    [--max-transport-legs N] [--ignore-resources] [--trace] [--mission-id ID]
+    [--object-ids seeded|real]
 ```
 
 - `<workflow>` — the portable v0 workflow: *what* happens.
@@ -132,6 +133,15 @@ lc run <workflow> --env <env>
   else 7200 real seconds. The two forms exclude each other.
 - `--no-probe` — ignore the environment's `x-labcode.probe` policies and treat every
   machine as reachable (§1.6). The documents are still validated.
+- `--max-transport-legs N` — how many transport activities one Object-bearing arc may
+  be carried in (schedule spec §6.4.1), joined by **relay** activities. It is 1 by
+  default: the single hop. Raise it where the transporter cannot reach an instrument
+  from where the plate is — a bench it serves from one position only, or a hand-off
+  station a plate has to cross — and the move is planned as the shortest chain between
+  the two spots instead of being reported unreachable. Only the fewest possible moves
+  are offered, so a plate one move away is never sent round by way of somewhere else.
+  This describes the laboratory's reach rather than tuning the loop, which is why it is
+  here and not among the replan knobs below.
 - `--ignore-resources` — switch the consumable model off. The environment's resource
   declarations are still checked for shape but none is applied, so a bench whose devices
   declare stocks nobody is tracking runs without the boundary saying what they held.

{labcode-0.3.1 → labcode-0.4.0}/examples/README.md

@@ -57,6 +57,15 @@ and writes its artifacts under [`outputs/`](outputs/):
 python examples/render_plate_line.py
 ```
 
+🔴 **These are a record of one run, not a reproducible golden.** The labcode backend
+runs its operations out of process against a **wall clock** (`seconds_per_tick`), so
+which tick a subprocess finishes on varies between runs: re-rendering the same commit
+gives a final `now` of 10 one time and 13 the next. Do not treat a difference here as a
+regression, and do not gate a change on these files being byte-identical — the way the
+scheduler's and the runner's own artifacts can be, both of those being driven by a
+virtual clock. What *is* stable is the plan the scheduler produces from a given input,
+which the tests cover.
+
 - [`outputs/plate_line.plan.yaml`](outputs/plate_line.plan.yaml) — the **final execution
   schedule** (the §6/§7 status document: every activity, `completed`).
 - [`outputs/plate_line.observation.yaml`](outputs/plate_line.observation.yaml) — the

{labcode-0.3.1 → labcode-0.4.0}/labcode/run_cli.py

@@ -65,6 +65,13 @@ def _build_parser() -> argparse.ArgumentParser:
         "--margin", type=int, default=None, metavar="M",
         help="running-task margin for replans (default: the poll interval)",
     )
+    p.add_argument(
+        "--max-transport-legs", type=int, default=1, metavar="N",
+        help="how many transport activities one Object-bearing arc may be carried in "
+             "(default 1: the single hop), joined by relays -- raise it for an "
+             "instrument the transporter reaches at one position only, or a plate "
+             "that has to cross a hand-off station",
+    )
     p.add_argument(
         "--poll-interval", type=int, default=1, metavar="D",
         help="poll every D time units (default 1)",
@@ -329,6 +336,11 @@ def main(argv: Sequence[str] | None = None) -> int:
             running_task_margin=args.margin,
             random_seed=args.seed,
             poll_interval=args.poll_interval,
+            # How many moves one arc may be carried in (schedule SPEC §6.4.1). Passed
+            # through rather than decided here: it is the scheduler's offer, and a real
+            # laboratory is exactly where an instrument reachable from one position
+            # only makes the single hop insufficient.
+            max_transport_legs=args.max_transport_legs,
             # 0 is "no limit" here as it is upstream; the runner spells that None.
             max_ticks=args.max_ticks or None,
             seconds_per_tick=args.seconds_per_tick,

{labcode-0.3.1 → labcode-0.4.0}/labcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: labcode
-Version: 0.3.1
+Version: 0.4.0
 Summary: labcode -- a dialect wrapper over the Object-Flow Programming Language toolchain
 Author-email: Kazunari Kaizu <kwaizu@gmail.com>
 License-Expression: MIT
@@ -21,8 +21,8 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: ofplang-validate<0.3,>=0.2
-Requires-Dist: ofplang-schedule<0.6,>=0.5
-Requires-Dist: ofplang-run<0.7,>=0.6
+Requires-Dist: ofplang-schedule<0.9,>=0.8
+Requires-Dist: ofplang-run<0.8,>=0.7
 Provides-Extra: test
 Requires-Dist: pytest>=7.0; extra == "test"
 Requires-Dist: opentelemetry-sdk>=1.20; extra == "test"
@@ -143,7 +143,8 @@ described below.
 lc run <workflow> --env <env>
     [--boundary DOC] [-o OUT] [--boundary-out FILE] [--observation-out FILE]
     [--seconds-per-tick S] [--op-timeout S | --no-op-timeout] [--no-probe]
-    [--ignore-resources] [--trace] [--mission-id ID] [--object-ids seeded|real]
+    [--max-transport-legs N] [--ignore-resources] [--trace] [--mission-id ID]
+    [--object-ids seeded|real]
 ```
 
 - `<workflow>` — the portable v0 workflow: *what* happens.
@@ -176,6 +177,15 @@ lc run <workflow> --env <env>
   else 7200 real seconds. The two forms exclude each other.
 - `--no-probe` — ignore the environment's `x-labcode.probe` policies and treat every
   machine as reachable (§1.6). The documents are still validated.
+- `--max-transport-legs N` — how many transport activities one Object-bearing arc may
+  be carried in (schedule spec §6.4.1), joined by **relay** activities. It is 1 by
+  default: the single hop. Raise it where the transporter cannot reach an instrument
+  from where the plate is — a bench it serves from one position only, or a hand-off
+  station a plate has to cross — and the move is planned as the shortest chain between
+  the two spots instead of being reported unreachable. Only the fewest possible moves
+  are offered, so a plate one move away is never sent round by way of somewhere else.
+  This describes the laboratory's reach rather than tuning the loop, which is why it is
+  here and not among the replan knobs below.
 - `--ignore-resources` — switch the consumable model off. The environment's resource
   declarations are still checked for shape but none is applied, so a bench whose devices
   declare stocks nobody is tracking runs without the boundary saying what they held.

{labcode-0.3.1 → labcode-0.4.0}/labcode.egg-info/requires.txt

@@ -1,6 +1,6 @@
 ofplang-validate<0.3,>=0.2
-ofplang-schedule<0.6,>=0.5
-ofplang-run<0.7,>=0.6
+ofplang-schedule<0.9,>=0.8
+ofplang-run<0.8,>=0.7
 
 [dev]
 pytest>=7.0

labcode-0.4.0/labcode.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "0.4.0",
+  "distance": 0,
+  "node": "ge84abdb92eead9230494348c19d0e418605aaecb",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-09-11"
+}

{labcode-0.3.1 → labcode-0.4.0}/pyproject.toml

@@ -41,7 +41,10 @@ classifiers = [
 # `dispatch_replenishment` seam and the `kind: replenishment` the child harness has to
 # recognise as side-effect only.
 #
-# `ofplang-schedule>=0.5` is required, not merely tested against: an environment may
+# `ofplang-schedule>=0.8` is required, not merely tested against: `lc run` passes
+# `--max-transport-legs` through to it (schedule SPEC §6.4.1), and a job may leave a
+# running plan (§6.11), which needs the `withdraw` argument and the levels carried
+# forward with it. The `>=0.5` floor it replaces was required because an environment may
 # declare a route that needs no transporter (`transporter: null`, schedule §4.6/§5.4) and
 # this dialect accepts a `sila2` script on one, but an older scheduler refuses the
 # environment with `wrong_type` before there is a plan to run -- and `ofplang-run>=0.6` is
@@ -61,8 +64,8 @@ dependencies = [
 # bounds cannot protect what is already on PyPI without one, which is why they go
 # in now rather than at the first breakage.
     "ofplang-validate>=0.2,<0.3",
-    "ofplang-schedule>=0.5,<0.6",
-    "ofplang-run>=0.6,<0.7",
+    "ofplang-schedule>=0.8,<0.9",
+    "ofplang-run>=0.7,<0.8",
 ]
 
 [project.urls]

labcode-0.3.1/labcode.egg-info/scm_version.json

@@ -1,8 +0,0 @@
-{
-  "tag": "0.3.1",
-  "distance": 0,
-  "node": "g8ed9be19f0560168d506f98a6e9f54b3e7085aa0",
-  "dirty": false,
-  "branch": "HEAD",
-  "node_date": "2026-09-06"
-}