Papers › Learning to Iteratively Solve Routing Problems with Dual-Aspect Collaborative Transformer

Learning to Iteratively Solve Routing Problems with Dual-Aspect Collaborative Transformer

6 Oct 2021NeurIPS 2021 12arXiv:2110.02544archive 2025-07-28

Yining Ma, Jingwen Li, Zhiguang Cao, Wen Song, Le Zhang, Zhenghua Chen, Jing Tang

Recently, Transformer has become a prevailing deep architecture for solving vehicle routing problems (VRPs). However, it is less effective in learning improvement models for VRP because its positional encoding (PE) method is not suitable in representing VRP solutions. This paper presents a novel Dual-Aspect Collaborative Transformer (DACT) to learn embeddings for the node and positional features separately, instead of fusing them together as done in existing ones, so as to avoid potential noises and incompatible correlations. Moreover, the positional features are embedded through a novel cyclic positional encoding (CPE) method to allow Transformer to effectively capture the circularity and symmetry of VRP solutions (i.e., cyclic sequences). We train DACT using Proximal Policy Optimization and design a curriculum learning strategy for better sample efficiency. We apply DACT to solve the traveling salesman problem (TSP) and capacitated vehicle routing problem (CVRP). Results show that our DACT outperforms existing Transformer based improvement models, and exhibits much better generalization performance across different problem sizes on synthetic and benchmark instances, respectively.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

Syntology holds a reference implementation of Dual-Aspect Collaborative Transformer (DACT), generated from the paper text (not the authors' code), at level 3 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” (quoted from Syntology's server card). For this implementation, level 3 is recorded, but its report lists no property test that passed on both. No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='Dual-Aspect Collaborative Transformer (DACT)') (how to connect); the free check have('2110.02544') needs no token.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 16 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 7 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 11 samples from 1 repository, 7 ran (7 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 5 samples from 1 repository, 2 ran (2 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

yining043/VRP-DACT officialmentioned in papermentioned on GitHubpytorchSyntology: 11 samples, 7 ran (0 instrument-failed) · 4 unverified report
yining043/TSP-improve mentioned on GitHubpytorchSyntology: 5 samples, 2 ran (0 instrument-failed) · 3 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

16 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 7 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

9ran
7unverified

Licence: 0 of the 16 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

yining043/VRP-DACT official repository 11 samples, 7 ran (0 instrument-failed) · 4 unverified
EmbeddingNet nets/actor_network.py ran MIT (permissive) · d32eca8fe0b18c43 · report fixture: signature x:Tensor/3/float, solutions:Tensor/2/int, visited_time:NoneType/0/? · returned tuple · level recorded 2026-09-24
FFandNormsubLayer nets/actor_network.py ran · metamorphic tier: deterministic MIT (permissive) · 850da12d3368c65a · report fixture: signature input1:Tensor/3/float, input2:Tensor/3/float · returned tuple · level recorded 2026-09-22
MLP in 375 papers nets/actor_network.py ran · metamorphic tier: invariant MIT (permissive) · 355814dd5ff90a73 · report fixture: signature in_:Tensor/2/float · returned Tensor · level recorded 2026-09-22
MultiHeadAttention in 124 papers
census: 9 implementations from 7 papers, 9 distinct outputs across 3 buckets, one shared input per bucket
nets/actor_network.py ran MIT (permissive) · fa54d99ecac04864 · report fixture: signature h_node_in:Tensor/3/float, h_pos_in:Tensor/3/float · returned tuple · level recorded 2026-09-24
MultiHeadCompat nets/actor_network.py ran · metamorphic tier: invariant MIT (permissive) · 211b65805e3d00f5 · report fixture: signature q:Tensor/3/float, h:Tensor/3/float, mask:NoneType/0/? · returned Tensor · level recorded 2026-09-22
MultiHeadDecoder nets/actor_network.py ran MIT (permissive) · 30b971afd000a522 · report fixture: signature h_em:Tensor/3/float, pos_em:Tensor/3/float, solving_state_for_net:NoneType/0/? · returned Tensor · level recorded 2026-09-24
Normalization in 11 papers nets/actor_network.py ran · metamorphic tier: invariant MIT (permissive) · 08bc67177889a2b3 · report fixture: signature input:Tensor/3/float · returned Tensor · level recorded 2026-09-22
Actor in 68 papers nets/actor_network.py unverified MIT (permissive) · c62ea025f6578059 · report
MultiHeadAttentionsubLayer nets/actor_network.py unverified MIT (permissive) · 500395d982e1b1bb · report
MultiHeadEncoder nets/actor_network.py unverified MIT (permissive) · 8147e91b3d0fe9f1 · report
mySequential nets/actor_network.py unverified MIT (permissive) · b48a3565db4b5491 · report
yining043/TSP-improve community (archive-listed) 5 samples, 2 ran (0 instrument-failed) · 3 unverified
MultiHeadAttention in 124 papers
census: 9 implementations from 7 papers, 9 distinct outputs across 3 buckets, one shared input per bucket this sample: bucket 3 of 3, arg 1: rank 3, kind float, dtype float32 · arg 2: rank 3, kind float, dtype float32
nets/attention_model.py ran · metamorphic tier: invariant MIT (permissive) · 3e9c7f43e77628ea · report fixture: signature q:Tensor/3/float, h:Tensor/3/float, mask:NoneType/0/? · returned Tensor · level recorded 2026-09-22
MultiHeadDecoder nets/attention_model.py ran · metamorphic tier: deterministic MIT (permissive) · 5b8ea40ba7cb0c66 · report fixture: signature q:Tensor/3/float, exchange:Tensor/2/int, rec:Tensor/2/float · returned tuple · level recorded 2026-09-22
AttentionModel in 8 papers nets/attention_model.py unverified MIT (permissive) · afcbe0b62b04095b · report
EmbeddingNet nets/attention_model.py unverified MIT (permissive) · 5a3c7c6596133237 · report
MultiHeadAttentionLayer in 6 papers nets/attention_model.py unverified MIT (permissive) · 1905f5c7465accec · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another. Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

3 assemblies on this paper: 2 harvested, 1 generated, listed in 2 groups (siblings lifted in one batch form one group).

generated Assembly for Dual-Aspect Collaborative Transformer (DACT) (graph method: Dual-Aspect Collaborative Transformer (DACT)), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer; level 3 is recorded, but its report lists no property test that passed on both.

label matches by construction: the code was generated for this method (not judged by a model)

  1. ppo_clip_objective_gradient_step entry · level 3 · ran · honoured contract · 4822786f826bcb45b66d0648856d85e75f158f728eedc637648107376050d66d

2 sibling assemblies for Dual-Aspect Collaborative Transformer (DACT) (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for Dual-Aspect Collaborative Transformer (DACT) (graph method: Dual-Aspect Collaborative Transformer (DACT)). 11 bricks; individually on a fixture: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. Actor entry · level 0 · unverified · c62ea025f6578059
  2. EmbeddingNet model · level 1 · ran · d32eca8fe0b18c43
  3. MultiHeadDecoder model · level 1 · ran · 30b971afd000a522
  4. MultiHeadEncoder model · level 0 · unverified · 8147e91b3d0fe9f1
  5. mySequential helper · level 0 · unverified · b48a3565db4b5491
  6. MLP helper · level 1 · ran · 355814dd5ff90a73
  7. MultiHeadCompat model · level 1 · ran · 211b65805e3d00f5
  8. FFandNormsubLayer helper · level 1 · ran · 850da12d3368c65a
  9. MultiHeadAttentionsubLayer helper · level 0 · unverified · 500395d982e1b1bb
  10. Normalization helper · level 1 · ran · 08bc67177889a2b3
  11. MultiHeadAttention model · level 1 · ran · fa54d99ecac04864

harvested Assembly for Dual-Aspect Collaborative Transformer (DACT) (graph method: Dual-Aspect Collaborative Transformer (DACT)). 7 bricks; individually on a fixture: 4 ran (of which 2 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. AttentionModel entry · level 0 · unverified · afcbe0b62b04095b
  2. EmbeddingNet model · level 0 · unverified · 5a3c7c6596133237
  3. MultiHeadAttentionLayer model · level 0 · unverified · 1905f5c7465accec
  4. MultiHeadDecoder model · level 1 · ran · 5b8ea40ba7cb0c66
  5. MultiHeadAttention model · level 1 · ran · 3e9c7f43e77628ea
  6. Normalization helper · level 1 · ran · d7486b45b2dfeb02
  7. SkipConnection helper · level 1 · ran · 8101e9e48232516f

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2110.02544") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Traveling Salesman Problem

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections