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

Is It Resizing or Just Fusion at Corresponding Positions? #38

Open
Lne27 opened this issue Mar 23, 2024 · 1 comment
Open

Is It Resizing or Just Fusion at Corresponding Positions? #38

Lne27 opened this issue Mar 23, 2024 · 1 comment

Comments

@Lne27
Copy link

Lne27 commented Mar 23, 2024

I'd like to ask, during the stage of regional latent space fusion in different areas, is this method really resizing to the corresponding positions? Looking at the code, it seems that only the latent spaces of the corresponding positions in each regional image are fused, which is quite confusing?

@CyrilSterling
Copy link

Yes, I have the same question. The latent feature of the sub-region is directly cropped and not resized.

out = out[:,int(latent_h*drow.start) + addout:int(latent_h*drow.end),
int(latent_w*dcell.start) + addin:int(latent_w*dcell.end),:]

Then, the cropped features are fused with the corresponding positions of the base latent features.
if self.usebase :
# outb_t = outb[:,:,int(latent_w*drow.start):int(latent_w*drow.end),:].clone()
outb_t = outb[:,int(latent_h*drow.start) + addout:int(latent_h*drow.end),
int(latent_w*dcell.start) + addin:int(latent_w*dcell.end),:].clone()
out = out * (1 - dcell.base) + outb_t * dcell.base

It seems not resized as the paper say. And I'd like to know why this is done, is it because resize doesn't make sense?

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

No branches or pull requests

2 participants