-
Notifications
You must be signed in to change notification settings - Fork 26
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
Does unpatchify average between overlapping patches? #11
Comments
Hi @ritulahoti it won't do average. If the patches are overlapped, patchify will de-overlapping and recover the original image if this condition holds |
Hi, thanks for a quick response. |
No, the overlapped patches will be de-overlapped. E.g. for the 1d case, the original image is [a,b,c], patchily with step size 1 produces two patches. patch 1 is [a,b] and patch 2 is [b, c], then the patch 2 will be trimmed to [c] only when doing unpatchify. Then it will be concatenated with [a,b] to recover the original [a,b,c] image.
Weiyuan Wu | Ph.D. Student @sfu-db
a: 8888 University Dr., Burnaby, BC, CA
***@***.*** w: wooya.me
…On Jun 5, 2021, 10:30 PM -0700, Ritu Lahoti ***@***.***>, wrote:
Hi, thanks for a quick response.
I'm trying to patchify an image and unpatchify the segmentation maps of the generated patches. So, for given two overlapping patches with varying probability values within, what values does the overlapping section get? (Conditions are being met)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Alright, I got it. Also, any help on how can I average the overlapping regions value? |
This must be a bug if the result is shifted. Would you mind providing your image size and the step size/patch size you used? For averaging the overlapping values, unfortunately, I think you need to change the code in the |
Sure. |
How do the unpatchify works for overlapping patches?
Does it average the values in overlapped area or it takes the value of the next patch as it is?
Thanks.
The text was updated successfully, but these errors were encountered: