You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Watcher log currently shows logical and virtual coordinates.
The thinking is that physical coordinates are needed for power users (runtime team) and that we can expose them in the watcher log if an env var is set (say, TT_METAL_WATCHER_SHOW_PHYSICAL_COORDS).
We wanted to avoid potentially showing an example of extracting and using physical coords, so plan is to add a cluster api to get physical coord from logical, which includes a (disable-able by non-default argument) warning to not use physical coords.
Watcher log currently shows logical and virtual coordinates.
The thinking is that physical coordinates are needed for power users (runtime team) and that we can expose them in the watcher log if an env var is set (say, TT_METAL_WATCHER_SHOW_PHYSICAL_COORDS).
We wanted to avoid potentially showing an example of extracting and using physical coords, so plan is to add a cluster api to get physical coord from logical, which includes a (disable-able by non-default argument) warning to not use physical coords.
FYI @pgkeller @tt-asaigal
The text was updated successfully, but these errors were encountered: