Skip to content

docs: add Graph artifacts appendix - #755

Open
loukikjoshi06-ops wants to merge 3 commits into
mllam:mainfrom
loukikjoshi06-ops:docs/graph-artifacts-appendix
Open

loukikjoshi06-ops wants to merge 3 commits into
mllam:mainfrom
loukikjoshi06-ops:docs/graph-artifacts-appendix

Conversation

@loukikjoshi06-ops

@loukikjoshi06-ops loukikjoshi06-ops commented Sep 20, 2026 •

Copy link
Copy Markdown

changes

Added a concise 'Graph artifacts' appendix in docs/graph_debugging.md documenting the role of each *.pt graph file (g2m, m2m, m2g, up/down vertical edges, static node and edge features), what len and vdiff features represent, and troubleshooting steps for graph-related runtime errors. Linked to the appendix from the README.md graph format section.

Issue

Closes #535

Type of change

  • 📖 Documentation (Addition or improvements to documentation)

Checklist

  • My branch is up-to-date with the target branch
  • I have performed a self-review of my code
  • I have updated the README to cover introduced code changes
  • I have given the PR a name that clearly describes the change, written in imperative form.

loukikjoshi06-ops and others added 3 commits September 20, 2026 16:13
Added a short appendix in docs/graph_debugging.md to explain graph artifact files and debugging steps. Linked from README.md. Resolves mllam#535.

Co-authored-by: Gemini 3.1 Pro <noreply@google.com>
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.

[Docs] Short “Graph artifacts” appendix: what each graph/*.pt file means when debugging

1 participant