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.

Sign up for GitHub

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

Jump to bottom

Add support for pytorch>=1.0 #2

Open
arpanmangal opened this issue May 13, 2020 · 3 comments
Open

Add support for pytorch>=1.0 #2

arpanmangal opened this issue May 13, 2020 · 3 comments

Comments

@arpanmangal
Copy link
Owner

Present code requires pytorch0.3 and CUDA<=8.0. The code needs to be updated to support pytorch>1.0. The main reason for using pytorch0.3 is compatibility with trained CheXNet model.
@arpanmangal
Copy link
Owner Author

Continuing discussing from #1

@SuryaKalia FYI

@arpanmangal arpanmangal mentioned this issue May 13, 2020
Closed
@arpanmangal
Copy link
Owner Author

@bartmch
Yes keeping num_batches_tracked as the default value of zero tensors is the best which could be done imo.
Further the keys not only differ in a module. string, but are also renamed like one has ...conv1, while other version has ...conv.1. Print the keys and compare to see all such variations.

@Mayur6999
Copy link

transfer.py code is not working plz check ASAP
There is a problem loading pytorch 0.3.0 and torchvision 0.2.0 plz add support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arpanmangal @Mayur6999