Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coordinate systems docs #223

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

pjanevskiTT
Copy link
Contributor

Write a doc about coordinate systems. Base for this document is open-umd document which explains all coordinate systems we have

Note for reviews

Feel free to suggest any naming conventions for these coordinate systems. Naming from the initial doc is going to be followed for now, just because it seems that this is mostly accepted across different tenstorrent products (syseng tools, tt-metal, tt-umd)

@pjanevskiTT pjanevskiTT self-assigned this Oct 28, 2024
@pjanevskiTT
Copy link
Contributor Author

Comment from original harvesting PR #202 (comment)

@pjanevskiTT
Copy link
Contributor Author

One more comment from original PR #202 (comment)

@pjanevskiTT pjanevskiTT mentioned this pull request Oct 28, 2024
15 tasks
@alewycky-tenstorrent
Copy link

Suggestion on naming:

  • Physical: actual chip layout, not used by SW
  • NOC post-translate: the burned-in NOC coordinates (currently "Physical")
  • NOC pre-translate: NOC translation LUT input coordinates (currently "HW translated")
  • Virtualized: no change (virtualized is the coord space that makes NOC pre-translate look like a chip without translation at all)
  • Logical: no change (logical is the coord space with just tensixes based at 0-0?)

Also I suggest addressing them in this order (or the reverse) because that's how they are layered.

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.

2 participants