Papers
Topics
Authors
Recent
Search
2000 character limit reached

WinkTPG: Efficient MAPF Execution Framework

Updated 7 July 2026
  • WinkTPG is a multi-agent path-finding framework that refines discrete MAPF plans into continuous, kinodynamically feasible and collision-free speed profiles.
  • It combines temporal plan graph reasoning, single-agent speed optimization, and receding-horizon replanning to dynamically manage uncertainties during execution.
  • Empirical evaluations show near real-time replanning for up to 1,000 agents, achieving reduced suboptimality and enhanced scalability.

Searching arXiv for the target paper and closely related MAPF execution work to ground the article. Windowed kTPG, abbreviated WinkTPG, is a multi-agent path-finding execution framework that incrementally refines a discrete collision-free MAPF plan into kinodynamically feasible speed profiles by combining temporal plan graph reasoning, single-agent speed optimization, and receding-horizon replanning (Yan et al., 2 Aug 2025). It is introduced together with kinodynamic Temporal Plan Graph Planning (kTPG), which addresses a central limitation of standard MAPF algorithms: their reliance on simplified kinodynamic models, which can prevent agents from directly following the generated MAPF plan. WinkTPG builds on kTPG by dynamically incorporating agent information during execution through a window-based mechanism intended to reduce uncertainty while preserving collision-freeness (Yan et al., 2 Aug 2025).

1. Problem setting and formal representation

The framework is defined for the Multi-Agent Execution Problem (MAEP) over a discrete collision-free MAPF solution encoded as a Temporal Plan Graph (TPG) (Yan et al., 2 Aug 2025). The agent set is denoted A={a1,…,aI}\mathcal{A}=\{a_1,\ldots,a_I\}, where each agent aia_i has a start qisq_i^s and goal qigq_i^g in an undirected graph GU=(VU,EU)G_U=(V_U,E_U). A MAPF plan is given as P={p1,…,pI}P=\{p_1,\ldots,p_I\}, where each path is a vertex-time sequence

pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},

with qi0=qisq_i^0=q_i^s and qizi=qigq_i^{z^i}=q_i^g. The plan is collision-free in the discrete sense, meaning that it contains no vertex conflicts and no edge-swap conflicts (Yan et al., 2 Aug 2025).

The TPG is a directed acyclic graph G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2) with vertex set

aia_i0

Type-1 edges aia_i1 encode sequential precedence along each agent path aia_i2, while Type-2 edges aia_i3 encode inter-agent ordering at shared locations. This graph is the temporal backbone that converts a discrete MAPF solution into a constrained continuous-time execution problem (Yan et al., 2 Aug 2025).

The execution variables are arrival times aia_i4 for agent aia_i5 at vertex aia_i6, with leave times defined as aia_i7. Each vertex is associated with a reserved interval aia_i8, initially aia_i9 and qisq_i^s0, and feasible profiles must satisfy qisq_i^s1. Segment lengths are given by qisq_i^s2, and agent dynamics are constrained by

qisq_i^s3

The optimization objective is to minimize total completion time,

qisq_i^s4

subject to boundary conditions, reserved-interval constraints, traversal-time bounds, and acceleration limits (Yan et al., 2 Aug 2025).

A central property of the formulation is that satisfying all reserved-interval constraints together with the kinodynamic bounds guarantees collision-free continuous execution that respects the TPG precedences (Yan et al., 2 Aug 2025). This places WinkTPG in the class of execution-layer methods that preserve a discrete MAPF ordering while re-optimizing continuous timing.

2. kTPG as the underlying speed optimization method

kTPG is the base speed optimization algorithm on which WinkTPG is constructed. Its role is to refine a MAPF plan into a continuous, kinodynamically feasible execution by iteratively enforcing collision avoidance through reserved-interval refinement and single-agent replanning (Yan et al., 2 Aug 2025).

At each iteration, kTPG first identifies Type-2 edges qisq_i^s5 whose current reserved intervals overlap; these are termed conflicting edges. For each agent qisq_i^s6, it counts how many conflicting edges originate from its unlocked vertices, where unlocked vertices are those whose incoming conflicts have already been cleared. The selected agent is the one maximizing this count (Yan et al., 2 Aug 2025). This agent-selection mechanism is a scheduling policy over the TPG conflict structure rather than a global joint optimization.

For the chosen agent, kTPG solves a single-agent subproblem:

qisq_i^s7

subject to

qisq_i^s8

qisq_i^s9

qigq_i^g0

qigq_i^g1

qigq_i^g2

In practice, the method uses a 1D Safe-Interval Path Planning with Kinodynamic Primitives, described as a variant of SIPP-IP, to compute the time-optimal profile over discretized speed levels, with completeness and optimality for the subproblem (Yan et al., 2 Aug 2025).

After replanning, kTPG updates reserved intervals. For each conflicting edge qigq_i^g3 from an unlocked vertex, it sets qigq_i^g4 and splits the shared-location time axis at qigq_i^g5 into qigq_i^g6 for qigq_i^g7 and qigq_i^g8 for qigq_i^g9, intersecting these with the current reserved intervals. This clears the conflict and may unlock additional vertices. The process repeats until no Type-2 conflicts remain (Yan et al., 2 Aug 2025).

The significance of kTPG for WinkTPG is structural: the windowed framework does not replace the base optimizer, but invokes it repeatedly on restricted subgraphs so that execution and replanning can be interleaved.

3. Windowed execution mechanism

WinkTPG extends kTPG with a receding-horizon execution loop designed to reduce uncertainty growth along long paths (Yan et al., 2 Aug 2025). The framework introduces two control parameters. The execution interval GU=(VU,EU)G_U=(V_U,E_U)0 is the time between successive replanning events; an example given is GU=(VU,EU)G_U=(V_U,E_U)1. The planning horizon GU=(VU,EU)G_U=(V_U,E_U)2 specifies the size of the lookahead window, measured either in number of vertices or in time (Yan et al., 2 Aug 2025).

The main loop proceeds by first initializing reserved intervals to GU=(VU,EU)G_U=(V_U,E_U)3 and computing an initial kTPGu plan. Then, while not all agents are at their goals, the system waits either GU=(VU,EU)G_U=(V_U,E_U)4 seconds or until an agent reports a new arrival time. For each agent GU=(VU,EU)G_U=(V_U,E_U)5, it identifies the most recently reported vertex GU=(VU,EU)G_U=(V_U,E_U)6 together with the exact time GU=(VU,EU)G_U=(V_U,E_U)7, and marks the next GU=(VU,EU)G_U=(V_U,E_U)8 vertices as enqueued, meaning they can follow the previous plan (Yan et al., 2 Aug 2025).

The planning window GU=(VU,EU)G_U=(V_U,E_U)9 is then built by including, for each agent, the vertices after P={p1,…,pI}P=\{p_1,\ldots,p_I\}0 up to horizon P={p1,…,pI}P=\{p_1,\ldots,p_I\}1. If any Type-2 edge crosses into P={p1,…,pI}P=\{p_1,\ldots,p_I\}2, predecessors are recursively added. Reserved intervals inside P={p1,…,pI}P=\{p_1,\ldots,p_I\}3 are reinitialized, using the actual P={p1,…,pI}P=\{p_1,\ldots,p_I\}4 for the last known vertex, and kTPGu is invoked on the subgraph induced by P={p1,…,pI}P=\{p_1,\ldots,p_I\}5 to produce new speed profiles. These profiles are then transmitted to agents for the next P={p1,…,pI}P=\{p_1,\ldots,p_I\}6 interval (Yan et al., 2 Aug 2025).

Three consequences are stated explicitly for this design. First, windowing confines replanning to a small subgraph. Second, actual feedback reduces temporal uncertainty. Third, the procedure ensures continuous collision-free execution (Yan et al., 2 Aug 2025). A plausible implication is that WinkTPG is intended to preserve the temporal ordering guarantees of the underlying TPG while avoiding full-horizon re-optimization after every execution update.

4. Temporal uncertainty model and dynamic replanning

The uncertainty model in WinkTPG is temporal and edge-local. Traversal time from P={p1,…,pI}P=\{p_1,\ldots,p_I\}7 to P={p1,…,pI}P=\{p_1,\ldots,p_I\}8 is represented as

P={p1,…,pI}P=\{p_1,\ldots,p_I\}9

Under this model, the stochastic reach time at vertex pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},0 satisfies

pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},1

with

pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},2

Thus, the variance accumulates along the path as a sum of segment-level uncertainties (Yan et al., 2 Aug 2025).

For a Type-2 edge pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},3, the execution requirement is

pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},4

which is equivalent to

pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},5

The uncertainty-aware variant kTPGu enforces this by adding a safety margin pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},6 when splitting reserved intervals (Yan et al., 2 Aug 2025).

As execution advances and actual times are reported, the accumulated uncertainty pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},7 diminishes, and the required margins shrink correspondingly (Yan et al., 2 Aug 2025). This is the formal basis for the claim that windowing reduces uncertainty during execution: feedback narrows the temporal distributions that otherwise broaden along long, unreconciled trajectories.

A frequent misconception in MAPF execution is that a discrete collision-free plan is sufficient for direct deployment. The formulation here explicitly rejects that assumption. In this framework, discrete collision-freeness is only the starting point; safe continuous execution further requires reserved-interval satisfaction and kinodynamic feasibility (Yan et al., 2 Aug 2025).

5. Complexity and scalability characteristics

The complexity analysis separates the base optimizer from the windowed framework. For kTPG and kTPGu, each iteration clears at least one Type-2 edge. Since there are at most pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},8 such edges and at most pi={(qi0,t0),…,(qizi,tzi)},p_i=\{(q_i^0,t_0),\ldots,(q_i^{z^i},t_{z^i})\},9 vertices, the number of iterations is qi0=qisq_i^0=q_i^s0. Each iteration solves one single-agent SIPP-IP problem in qi0=qisq_i^0=q_i^s1 time, where qi0=qisq_i^0=q_i^s2 is path length, yielding an overall complexity of roughly

qi0=qisq_i^0=q_i^s3

(Yan et al., 2 Aug 2025)

For WinkTPG, execution is divided into approximately qi0=qisq_i^0=q_i^s4 windows. Each window considers only qi0=qisq_i^0=q_i^s5 vertices per agent, reducing the per-window complexity to

qi0=qisq_i^0=q_i^s6

The paper states that by choosing qi0=qisq_i^0=q_i^s7 small, such as qi0=qisq_i^0=q_i^s8–qi0=qisq_i^0=q_i^s9 vertices, and qizi=qigq_i^{z^i}=q_i^g0 moderate, such as qizi=qigq_i^{z^i}=q_i^g1, the planner runs in milliseconds per window even for qizi=qigq_i^{z^i}=q_i^g2 (Yan et al., 2 Aug 2025).

The stated scalability enablers are decoupled single-agent subproblems, conservative but efficient reserved-interval updates that avoid a global MILP, and the receding horizon, which limits problem size (Yan et al., 2 Aug 2025). This suggests that WinkTPG is architected as a decomposition-based alternative to approaches whose central bottleneck is coupled global optimization.

6. Experimental evaluation and reported performance

The evaluation uses MovingAI benchmark maps: empty qizi=qigq_i^{z^i}=q_i^g3, random qizi=qigq_i^{z^i}=q_i^g4, room qizi=qigq_i^{z^i}=q_i^g5, den520d qizi=qigq_i^{z^i}=q_i^g6, Boston qizi=qigq_i^{z^i}=q_i^g7, and warehouse-large qizi=qigq_i^{z^i}=q_i^g8, with up to qizi=qigq_i^{z^i}=q_i^g9 agents and paths generated by PBS (Yan et al., 2 Aug 2025). Two robot models are considered. The first is omnidirectional with G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)0 and G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)1, using speed discretization G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)2. The second is differential-drive with turns at zero speed, taking G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)3 for a G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)4 turn and G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)5 for a G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)6 turn (Yan et al., 2 Aug 2025).

The reported metrics are the suboptimality ratio,

G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)7

runtime, defined as total planning time for kTPG or per-window planning time for WinkTPG, MAPF time, and success rate (Yan et al., 2 Aug 2025).

For omnidirectional robots without uncertainty, kTPG is compared with ADG and KDN. The reported findings are that kTPG improves over ADG by up to G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)8 suboptimality reduction on the warehouse map; KDN slightly outperforms kTPG but fails beyond approximately G=(V,E1,E2)\mathcal{G}=(V,E_1,E_2)9 agents because of exponential MILP behavior; and both kTPG and ADG maintain aia_i00 success up to aia_i01 agents, with kTPG runtime below aia_i02 per problem (Yan et al., 2 Aug 2025).

Under stochastic noise aia_i03, WinkTPG is compared with ADG. For aia_i04, WinkTPG yields aia_i05–aia_i06 better solution quality than ADG. The study also reports that smaller execution windows aia_i07, corresponding to more frequent replanning, and choices with aia_i08 improve quality. For aia_i09 agents, per-window planning time is approximately aia_i10 when aia_i11, compared with approximately aia_i12 when aia_i13 (Yan et al., 2 Aug 2025).

Overall, the reported conclusion is that WinkTPG achieves near real-time replanning for up to aia_i14 agents, robustly handling uncertainty and improving execution efficiency over ADG and KDN (Yan et al., 2 Aug 2025). A plausible interpretation is that its empirical contribution lies less in altering discrete path assignment than in making MAPF plans executable under kinodynamic and stochastic timing constraints at large scale.

Definition Search Book Streamline Icon: https://streamlinehq.com
References (1)

Topic to Video (Beta)

No one has generated a video about this topic yet.

Whiteboard

No one has generated a whiteboard explanation for this topic yet.

Follow Topic

Get notified by email when new papers are published related to Windowed kTPG (WinkTPG).