-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support run trainer locally #111
base: main
Are you sure you want to change the base?
Conversation
I usually run a model locally like this:
Is this insufficient for your use case? |
Yes, this should also work. The thing is that I saw many permission issues when run train.py directly. This just helps to run in a container. |
@@ -61,7 +61,8 @@ def buildpush( | |||
_run( | |||
f"{sudo_cmd} docker tag {docker_tag} {docker_url}", | |||
) | |||
_run(f"{sudo_cmd} docker push {docker_url}") | |||
if torchprime_docker_tag != "local_run": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This introduces a magical constant. I think it's simpler if we add a "push=True" function argument, and have the other file call this with push=False
Support to run train.py locally:
Or
This makes it easier to debug model code.
Currently it is still using the torch_xla from the base docker image. In the future, we may want to give the option to run with local build torch_xla.