Skip to content

Carry metadata across vertex trees - #225

Merged
webdevred merged 5 commits into
masterfrom
carry-metadata-across-vertex-trees
Aug 13, 2026
Merged

Carry metadata across vertex trees#225
webdevred merged 5 commits into
masterfrom
carry-metadata-across-vertex-trees

Conversation

@webdevred

Copy link
Copy Markdown
Owner

No description provided.

A metadata row ahead of the first vertex reaches only that vertex when the
surrounding names alternate prefixes, and compareAV sorts on aMeta before
the Y band, so the vertex ends up last in its group while its mirror on the
other side stays in front. The fixture needs alternating nl/nr names of its
own because frame.jbeam calls both sides rl_f and keeps them in one chunk.
Threading the resulting metadata from the previous vertex tree when creating a
new vertex tree.
@webdevred webdevred linked an issue Aug 13, 2026 that may be closed by this pull request
The metadata threading resolved the reordering and the dropped selfCollision
row, so the marker no longer describes what fails. What remains is the
// support comment on rlsm, which breakVertices hands to the next tree because
extractPreviousAssocCmt only inspects the head of the accumulator.
@webdevred
webdevred merged commit 1a16d46 into master Aug 13, 2026
13 checks passed
@webdevred
webdevred deleted the carry-metadata-across-vertex-trees branch August 13, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Node metadata is not carried across vertex tree boundaries

1 participant