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

Add PyTorch backends: first pass #821

merged 3 commits into from Aug 30, 2019

Add PyTorch backends: first pass #821

merged 3 commits into from Aug 30, 2019


Copy link

@lewfish lewfish commented Aug 30, 2019

This PR adds chip classification and semantic segmentation backends based on PyTorch and fastai, along with a lot of infrastructure to simultaneously support the existing TF backends. Initially, I tried to create a single Docker image containing everything, but that approach was problematic. The existing version of Tensorflow in RV wasn't compatible with the latest PyTorch/Fastai because of a conflict in the versions of numpy and cuda. I could have tried to upgrade the three backends to use the latest version of Tensorflow, but I thought that was risky and not worth the effort if we're sunsetting the TF backends. So, I decided to just have separate images, which was quite a bit of work in and of itself.


A subsequent PR will add the following:

  • a lengthy changelog entry
  • integration tests for PyTorch backends
  • change the name of the backends from Fastai* to Pytorch* since we might end up going the pure pytorch route in the future
  • update docs

Related PRs: azavea/raster-vision-aws#26 and azavea/raster-vision-examples#66

@lewfish lewfish force-pushed the lf/fastai-backends2 branch from abbd91d to 5234606 Aug 30, 2019
@lewfish lewfish changed the title WIP: add pytorch backends Add PyTorch backends Aug 30, 2019
@lewfish lewfish changed the title Add PyTorch backends Add PyTorch backends: first pass Aug 30, 2019
@lewfish lewfish merged commit 1720647 into master Aug 30, 2019
1 check passed
@lewfish lewfish deleted the lf/fastai-backends2 branch Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant