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
ensure everyone who currently has access, has access after the move too (need to open OSPO ticket w/ John Hawley, @ayerofieiev-tt to finalize list of people)
move the actual repo (need to open OSPO ticket w/ John Hawley)
On a completely fresh python virtual environment, I can successfully install ttnn from the github direct whl link and other requirements from pytorch2.0_ttnn requirements.txt. I can import ttnn successfully from here.
However, the tests do depend on tests.ttnn.utils_for_testing module which isn't in the release whl from github. I'm not sure if I can remove this dependency since many of the unit tests from tt-metal/ttnn also uses the functions from that module.
I will include a dev version of requirements.txt which won't install the whl and rely on the user creating the python virtual env with ./create_venv.sh from tt-metal. That creates an egg link to the ttnn source directory which makes development easier.
I can push the changes to requirements.txt to main, but I am still not sure how to address the issue with the tests module from the first point.
@tt-rkim @ayerofieiev-tt has finished shifting the pytorch repo to the TT org and current members are ported over to have same access.
Would be prudent to start planning VM consolidation soon
Introduction
We are putting all relevant issues + action items for supporting https://github.com/tenstorrent-metal/pytorch2.0_ttnn/ and related infrastructure issues here.
cc: @ayerofieiev-tt @TT-billteng @ttmchiou
The text was updated successfully, but these errors were encountered: