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

[FIX] fold with non-zero padding #32

Merged
merged 4 commits into from
Jan 10, 2024
Merged

[FIX] fold with non-zero padding #32

merged 4 commits into from
Jan 10, 2024

Conversation

f-dangel
Copy link
Owner

Fixes #30.

This should fix #30.

The problem was in the creation of the tensor that maps the patch values
back to the positions in the original image. The code was using `unfold`
with non-zero padding, which would lead to a lot of patch values being
assigned to location 0. The fix is to deal with padding explicitly so
that the `unfold` operation uses `padding=0`. Then the index tensor is
correct, and after scattering we have to un-pad the image to obtain the
output.
Github actions keep failing for unknown reasonds.
The error is:
```
coveralls.exception.CoverallsException: Could not submit coverage: 422 Client Error: Unprocessable Entity for url: https://coveralls.io/api/v1/jobs
```
Deciding to remove coverage uploads to coveralls.
@f-dangel f-dangel merged commit f6cb681 into main Jan 10, 2024
23 checks passed
@f-dangel f-dangel deleted the bug30-fold-with-padding branch January 10, 2024 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Padding !=0 leads to inconsistent results for fold
1 participant