-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Add a gaussian sampler #5487
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 a gaussian sampler #5487
Conversation
@pajotarthur If you fix the merge conflicts I'll run this on CI for you. |
@pytorchbot test this please |
1 similar comment
@pytorchbot test this please |
.jenkins/macos-build-test.sh
Outdated
@@ -18,7 +18,7 @@ export MACOSX_DEPLOYMENT_TARGET=10.9 | |||
export CXX=clang++ | |||
export CC=clang | |||
# If we run too many parallel jobs, we will OOM | |||
export MAX_JOBS=2 | |||
export MAX_JOBS=3 |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
What's going on with the pybind11 submodule update? |
I'm not really sure, I pulled from https://github.com/pybind/pybind11 manually by mistake a long time ago, I can checkout to the correct commit, but when I git submodule update, it reverts to the wrong one. Is there a workaround ? It doesn't seems to break anything though. |
@pajotarthur The main reason to not update it here is to let a pybind11 submodule be its own commit, so that's easier to notice if you're reading the commit stream. An easy way to fix the problem is to "redo" your commit:
Another way is to manually checkout the submodule to the correct commit, and then do a |
@pytorchbot test this please |
The submodule still looks updated to me |
BTW, you can check locally if you've done the fix properly by running |
test/test_nn.py
Outdated
grid_cpu = Variable(torch.randn(D, N, H, W, 3).transpose(0, 1), requires_grad=True) | ||
out_cpu = F.grid_sample(input_cpu, grid_cpu, padding_mode=padding_mode) | ||
self.assertTrue(out_cpu.size() == torch.Size([N, C, D, H, W])) | ||
def test_cpu_against_cuda(N, C, D, H, W, padding_mode): |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
@pajotarthur Did @emited do a math check on the two kernel implementations? |
Absolutely. Do you need the maths in writing ? |
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.
Nope, that's good enough for me.
Looks like there is some sort of submodule update disaster. https://stackoverflow.com/questions/7718780/how-to-undo-git-submodule-update?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa can tell you how to fix it (you'll have to find the correct hashes) |
I messed up my commit, I'll correct it soon. |
Needs rebasing :( |
add gaussian sampler fix kernel_std add init
# Conflicts: # test/test_nn.py
# This is the 1st commit message: add gaussian sampler add gaussian sampler fix kernel_std add init # The commit message pytorch#2 will be skipped: # add init
@pytorchbot retest this please |
@pajotarthur needs another rebasing now |
Hey fellas, where is this standing right now? |
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.
Unfortunately, due to our negligence, this PR has severely bitrotten. Probably the best thing to do is for someone to redo it in ATen (c.f. https://github.com/pytorch/pytorch/wiki/TH-to-ATen-porting-guide) and resubmit. Sorry :(
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.
.
Added gaussian mode for grid_sampler cuda
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
Hi @pajotarthur! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
Anything new? |
With @emited, adding a C and CUDA functions for a gaussian grid sampler, similar with the one described in https://openreview.net/pdf?id=SkZXoGZC- .