Papers › Learning Flexible Body Collision Dynamics with Hierarchical Contact Mesh Transformer

Learning Flexible Body Collision Dynamics with Hierarchical Contact Mesh Transformer

19 Dec 2023arXiv:2312.12467archive 2025-07-28

Youn-Yeol Yu, Jeongwhan Choi, Woojin Cho, Kookjin Lee, Nayong Kim, Kiseok Chang, Chang-Seung Woo, Ilho Kim, Seok-Woo Lee, Joon-Young Yang, Sooyoung Yoon, Noseong Park

Recently, many mesh-based graph neural network (GNN) models have been proposed for modeling complex high-dimensional physical systems. Remarkable achievements have been made in significantly reducing the solving time compared to traditional numerical solvers. These methods are typically designed to i) reduce the computational cost in solving physical dynamics and/or ii) propose techniques to enhance the solution accuracy in fluid and rigid body dynamics. However, it remains under-explored whether they are effective in addressing the challenges of flexible body dynamics, where instantaneous collisions occur within a very short timeframe. In this paper, we present Hierarchical Contact Mesh Transformer (HCMT), which uses hierarchical mesh structures and can learn long-range dependencies (occurred by collisions) among spatially distant positions of a body -- two close positions in a higher-level mesh correspond to two distant positions in a lower-level mesh. HCMT enables long-range interactions, and the hierarchical mesh structure quickly propagates collision effects to faraway positions. To this end, it consists of a contact mesh Transformer and a hierarchical mesh Transformer (CMT and HMT, respectively). Lastly, we propose a flexible body dynamics dataset, consisting of trajectories that reflect experimental settings frequently used in the display industry for product designs. We also compare the performance of several baselines using well-known benchmark datasets. Our results show that HCMT provides significant performance improvements over existing methods. Our code is available at https://github.com/yuyudeep/hcmt.

PaperPDFCodeCode Syntology ran

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.

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

Code

Syntology 17 code samples harvested from 2 repositories linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 6 samples from 1 repository, 5 ran (3 with no instrument failure; 2 where Syntology's instrument failed); found in paper text by Syntology: 11 samples from 1 repository, 7 ran (5 with no instrument failure; 2 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

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

yuyudeep/hcmt officialmentioned in papermentioned on GitHubtfSyntology: 6 samples, 5 ran (2 instrument-failed) · 1 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

17 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
2ran; the contract check could not run
6ran
5unverified

Licence: 6 of the 17 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.

yuyudeep/hcmt official repository 6 samples, 5 ran (2 instrument-failed) · 1 unverified
add_targets dataset.py ran no licence file found · pointer only · 0f74786d92f7b6a0 · report fixture: signature ds:MockDataset/0/?, fields:list/1/str, add_history:bool/0/bool · returned MockDataset · level recorded 2026-09-24
get_check_point_num util.py ran · our draft was wrong fingerprinted no licence file found · pointer only · a951207c022a9c79 · report fixture: signature path:str/0/str · returned str · level recorded 2026-09-24
get_mask_impact_normal util.py ran · violated contract no licence file found · pointer only · 7182e4b73a148e4c · report fixture: signature initial_state:dict/0/? · returned EagerTensor · level recorded 2026-09-24
pairwise_dist in 10 papers model.py ran · honoured contract fingerprinted no licence file found · pointer only · 7872fb172aaec6b0 · report fixture: signature A:EagerTensor/2/float, B:EagerTensor/2/float · returned EagerTensor · level recorded 2026-09-24
triangles_to_edges util.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 3fc3d053754bcdfb · report fixture: signature faces:EagerTensor/2/int · returned tuple · level recorded 2026-09-24
load_dataset in 276 papers dataset.py unverified no licence file found · pointer only · ace670d545ed0b9d · report
google-deepmind/deepmind-research found in paper text by Syntology 11 samples, 7 ran (2 instrument-failed) · 4 unverified
build_crops_biases alphafold_casp13/contacts_network.py ran Apache-2.0 (permissive) · c2695f5eb1e963a3 · report fixture: signature bias_size:int/0/int, raw_biases:EagerTensor/2/float, crop_x:EagerTensor/2/int, crop_y:EagerTensor/2/int, back_prop:bool/0/bool · returned EagerTensor · level recorded 2026-09-24
call_on_tuple alphafold_casp13/contacts_network.py ran · our draft was wrong Apache-2.0 (permissive) · 2a0b71f3e9b5a0d7 · report fixture: signature f:callable/0/? · returned function · level recorded 2026-09-24
conv2d in 119 papers alphafold_casp13/two_dim_convnet.py ran Apache-2.0 (permissive) · 27c6606148980218 · report fixture: signature x:EagerTensor/4/float, w:EagerTensor/4/float, atrou_rate:int/0/int, data_format:str/0/str · returned EagerTensor · level recorded 2026-09-24
equal32 galaxy_mergers/losses.py ran Apache-2.0 (permissive) · 892496844acc7df6 · report fixture: signature x:EagerTensor/1/float, y:EagerTensor/1/float · returned EagerTensor · level recorded 2026-09-24
mse_loss in 73 papers
census: 8 implementations from 12 papers, 6 distinct outputs across 4 buckets, one shared input per bucket
galaxy_mergers/losses.py ran fingerprinted Apache-2.0 (permissive) · b914b7fa073cd865 · report fixture: signature predicted:Tensor/2/float, targets:Tensor/2/float · returned Tensor · level recorded 2026-09-24
normalize_regression_loss galaxy_mergers/losses.py ran fingerprinted Apache-2.0 (permissive) · f8ad297adc94df7d · report fixture: signature regression_loss:Tensor/2/float, predictions:Tensor/2/float · returned Tensor · level recorded 2026-09-24
relative_shift enformer/attention_module.py ran; the contract check could not run (RAISES) fingerprinted Apache-2.0 (permissive) · cb4b6e4277150f01 · report fixture: signature x:EagerTensor/4/float · returned EagerTensor · level recorded 2026-09-24
bias_variable in 24 papers alphafold_casp13/two_dim_convnet.py unverified Apache-2.0 (permissive) · 3bf8634c88f6bebc · report
get_positional_feature_function enformer/attention_module.py unverified Apache-2.0 (permissive) · 6ee8170a2950ea7c · report
positional_features_all enformer/attention_module.py unverified Apache-2.0 (permissive) · 6a7819159276d4e5 · report
weight_variable in 29 papers alphafold_casp13/two_dim_convnet.py unverified Apache-2.0 (permissive) · 7d7dfab4bbd647b3 · report

Tasks

Graph Neural NetworkNumerical IntegrationPhysical Simulations

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Physical Simulations Deformable Plate HCMT Rollout RMSE-all [1e3] Position 7.67±0.42 #1 of 1 Archive leaderboard report
Physical Simulations Deforming Plate HCMT Rollout RMSE-all [1e3] Position 7.49±0.07 #1 of 1 Archive leaderboard report
Physical Simulations Deforming Plate HCMT Rollout RMSE-all [1e3] Stress 4535956±49937 #1 of 1 Archive leaderboard report
Physical Simulations Impact Plate HCMT Rollout RMSE-all [1e3] Position 20.71±0.57 #1 of 1 Archive leaderboard report
Physical Simulations Impact Plate HCMT Rollout RMSE-all [1e3] Stress 14742±502 #1 of 1 Archive leaderboard report
Physical Simulations Sphere Simple HCMT Rollout RMSE-all [1e3] Position 30.41±1.71 #1 of 1 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutGraph Neural NetworkLabel 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