{"action":"created","issue":{"url":"https://api.github.com/repos/BVLC/caffe/issues/2682","labels_url":"https://api.github.com/repos/BVLC/caffe/issues/2682/labels{/name}","comments_url":"https://api.github.com/repos/BVLC/caffe/issues/2682/comments","events_url":"https://api.github.com/repos/BVLC/caffe/issues/2682/events","html_url":"https://github.com/BVLC/caffe/issues/2682","id":92734296,"number":2682,"title":"cuDNN errors when input < kernel <= padded input?","user":{"login":"waldol1","id":2991780,"avatar_url":"https://avatars.githubusercontent.com/u/2991780?v=3","gravatar_id":"","url":"https://api.github.com/users/waldol1","html_url":"https://github.com/waldol1","followers_url":"https://api.github.com/users/waldol1/followers","following_url":"https://api.github.com/users/waldol1/following{/other_user}","gists_url":"https://api.github.com/users/waldol1/gists{/gist_id}","starred_url":"https://api.github.com/users/waldol1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/waldol1/subscriptions","organizations_url":"https://api.github.com/users/waldol1/orgs","repos_url":"https://api.github.com/users/waldol1/repos","events_url":"https://api.github.com/users/waldol1/events{/privacy}","received_events_url":"https://api.github.com/users/waldol1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-07-02T20:59:08Z","updated_at":"2015-07-15T15:37:05Z","closed_at":null,"body":"This is a follow up on #2235, where a CUDNN_STATUS_BAD_PARAM error code is returned when attempting to do convolution with a kernel bigger than the input, *even if the padding specified would make it a valid operation*.\r\n\r\nMy example of failure is a 4x4 input with a 5x5 kernel with padding=1.  This causes the error when using Engine=CUDNN, but *not* with Engine=CAFFE.  Using a kernel size of 4x4 on a 4x4 input with no padding works just fine with CUDNN.\r\n\r\nHere is the prototxt I am using to trigger the failure:\r\n\r\n```\r\nname: \"Padding_Issue_Test\"\r\nlayer {\r\n  name: \"data\"\r\n  type: \"Data\"\r\n  top: \"data\"\r\n  transform_param {\r\n    crop_size: 4\r\n  }\r\n  data_param {\r\n    source: \"...\"\r\n    batch_size: 1\r\n    backend: LMDB\r\n  }\r\n}\r\nlayer {\r\n  name: \"conv1\"\r\n  type: \"Convolution\"\r\n  bottom: \"data\"\r\n  top: \"conv1\"\r\n  convolution_param {\r\n    num_output: 1\r\n    kernel_size: 5\r\n    stride: 1\r\n    pad: 1\r\n    engine: CUDNN\r\n  }\r\n}\r\n```\r\n\r\nThis may be a problem with CUDNN v2 itself, but I don't know enough to tell."},"comment":{"url":"https://api.github.com/repos/BVLC/caffe/issues/comments/121654580","html_url":"https://github.com/BVLC/caffe/issues/2682#issuecomment-121654580","issue_url":"https://api.github.com/repos/BVLC/caffe/issues/2682","id":121654580,"user":{"login":"slayton58","id":4992598,"avatar_url":"https://avatars.githubusercontent.com/u/4992598?v=3","gravatar_id":"","url":"https://api.github.com/users/slayton58","html_url":"https://github.com/slayton58","followers_url":"https://api.github.com/users/slayton58/followers","following_url":"https://api.github.com/users/slayton58/following{/other_user}","gists_url":"https://api.github.com/users/slayton58/gists{/gist_id}","starred_url":"https://api.github.com/users/slayton58/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/slayton58/subscriptions","organizations_url":"https://api.github.com/users/slayton58/orgs","repos_url":"https://api.github.com/users/slayton58/repos","events_url":"https://api.github.com/users/slayton58/events{/privacy}","received_events_url":"https://api.github.com/users/slayton58/received_events","type":"User","site_admin":false},"created_at":"2015-07-15T15:37:05Z","updated_at":"2015-07-15T15:37:05Z","body":"Thanks @waldol1, @zashani those test cases were very helpful!\r\n\r\nI agree that cuDNN is not handling this case as of v2 - I think my LD_LIBRARY_PATH was pulling in a more recent version of the library as opposed to v2, causing my tests to originally work. Starting from scratch I can confirm I see the same issue as both of you.\r\n\r\nI can also confirm that this is fixed in the upcoming cuDNN v3 release."}}