Skip to content

Conversation

pajotarthur
Copy link

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- .

@ezyang
Copy link
Contributor

ezyang commented Mar 1, 2018

@pajotarthur If you fix the merge conflicts I'll run this on CI for you.

@ezyang
Copy link
Contributor

ezyang commented Mar 7, 2018

@pytorchbot test this please

1 similar comment
@zou3519
Copy link
Contributor

zou3519 commented Mar 12, 2018

@pytorchbot test this please

@@ -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.

@ezyang
Copy link
Contributor

ezyang commented Mar 13, 2018

What's going on with the pybind11 submodule update?

@pajotarthur
Copy link
Author

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.

@ezyang
Copy link
Contributor

ezyang commented Mar 23, 2018

@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:

  1. git reset HEAD~
  2. git submodule update
  3. git commit -C $oldcommithash

Another way is to manually checkout the submodule to the correct commit, and then do a git commit --amend.

@ezyang
Copy link
Contributor

ezyang commented Mar 27, 2018

@pytorchbot test this please

@ezyang
Copy link
Contributor

ezyang commented Mar 27, 2018

The submodule still looks updated to me

@ezyang
Copy link
Contributor

ezyang commented Mar 27, 2018

BTW, you can check locally if you've done the fix properly by running git diff origin/master and seeing if the submodule update shows up there.

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.

@ezyang
Copy link
Contributor

ezyang commented Apr 16, 2018

@pajotarthur Did @emited do a math check on the two kernel implementations?

@pajotarthur
Copy link
Author

Absolutely. Do you need the maths in writing ?

Copy link
Contributor

@ezyang ezyang left a 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.

@ezyang
Copy link
Contributor

ezyang commented Apr 26, 2018

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)

@pajotarthur
Copy link
Author

I messed up my commit, I'll correct it soon.

@ezyang
Copy link
Contributor

ezyang commented May 15, 2018

Needs rebasing :(

@pajotarthur pajotarthur reopened this May 15, 2018
add gaussian sampler

fix kernel_std

add init
# 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
@ezyang
Copy link
Contributor

ezyang commented May 15, 2018

@pytorchbot retest this please

@weiyangfb
Copy link
Contributor

@pajotarthur needs another rebasing now

@weiyangfb weiyangfb added the awaiting response (this tag is deprecated) This tag is deprecated while we figure out what to do with it label Aug 21, 2018
@zdevito zdevito removed their request for review February 13, 2019 01:23
@gchanan gchanan removed their request for review February 28, 2019 16:28
@stathius
Copy link

stathius commented Jun 5, 2019

Hey fellas, where is this standing right now?

Copy link
Contributor

@ezyang ezyang left a 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 :(

@zou3519 zou3519 added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jun 7, 2019
@jamesr66a jamesr66a removed their request for review November 20, 2019 19:20
Copy link
Contributor

@anderspapitto anderspapitto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.

MengeTM pushed a commit to MengeTM/pytorch that referenced this pull request Feb 15, 2022
Added gaussian mode for grid_sampler cuda
@github-actions
Copy link
Contributor

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
Stale pull requests will automatically be closed 30 days after being marked Stale

@github-actions github-actions bot added the Stale label Mar 23, 2022
@facebook-github-bot
Copy link
Contributor

Hi @pajotarthur!

Thank you for your pull request and welcome to our community.

Action Required

In 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.

Process

In 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 CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@github-actions github-actions bot removed the Stale label Mar 29, 2022
@github-actions
Copy link
Contributor

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the Stale label May 28, 2022
@github-actions github-actions bot closed this Jun 27, 2022
@xming521
Copy link

Anything new?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting response (this tag is deprecated) This tag is deprecated while we figure out what to do with it open source Stale triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants