MOP 节拍放行 icon

MOP 节拍放行

流水线节拍放行（版本 2）：每次执行只放行 **一辆车**，剩余车辆暂存静态队列；仅当 `mopTwinTaktPipelineContinuation` 为 true 时续接回路，末辆车为 false 时用 **IF** 断开回路。版本 1 为兼容性遗留模式，新工作流请使用版本 2。

MOP 节拍放行

AI-generated

Summary

Simulate and output a takt-based vehicle release schedule for a manufacturing pipeline, dynamically managing a queue of vehicles to emit one per execution pass according to a specified hourly rate and simulation duration, supporting versioned behavior and configurable speed multiplier.

Inputs

  • 流水线队列 ID — Identifier for the static queue used to distinguish multiple production lines; recorded per emitted vehicle as mopTwinTaktPipelineLineId.
  • 续发前在本节点内等待（节拍墙钟） — If enabled, before emitting the next vehicle in continuation runs, the node waits the calculated interval (except before the first vehicle).
  • 每小时投放 (JPH) (required) — Nominal number of vehicles to release per simulated hour, used to compute emission intervals.
  • 总运行时长（小时） — Total simulation duration in hours. If set to a positive value, the total vehicle count is calculated as JPH × total hours, overriding "本轮投放总数". Zero means unlimited duration using configured total vehicle count instead.
  • 倍速 (required) — Simulation speed multiplier to scale down the real-time waiting intervals accordingly.
  • 本轮投放总数 (required) — Mode selecting whether the total vehicle count for the run matches the JPH or a custom number.
  • 自定义总辆数 — When using custom vehicle count mode, specifies the exact number of vehicles to release in this run.

Output shape

a single item per execution representing one vehicle release with scheduling metadata.

Each workflow execution emits exactly one vehicle's data in the output item with fields indicating continuation status, queue length remaining, vehicle serial number, timing parameters, and pipeline identifiers. The node manages a static queue internally to support multi-step continuation. Errors occur if continuation is requested but the queue is empty. Version 1 outputs a batched array of all vehicles at once, while version 2 outputs a single vehicle per execution pass and requires upstream logic to control continuation (mopTwinTaktPipelineContinuation). The output JSON includes mopMeta metadata for downstream processing.

Links

Discussion