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

Resizing DCT #16

Open
saitarslanboun opened this issue Nov 16, 2020 · 1 comment
Open

Resizing DCT #16

saitarslanboun opened this issue Nov 16, 2020 · 1 comment

Comments

@saitarslanboun
Copy link

saitarslanboun commented Nov 16, 2020

Hi!

Thanks for such a cool work!

I use your library for my Pytorch based model. I use fixed-size images, transform them to DCT format using your library, and stream them using data iterator.

Now, I would like to change my data iterator. Instead of using fixed image inputs, I would like to dynamically change the image size at every iteration, not epoch.

Is applying bilinear interpolation directly on DCT output equivalent to applying bilinear interpolation to images, and afterwards applying DCT?

If there is no big difference, I would like to go for the 1st one, as doing it is very simple. If I have to go for 2nd, I have to spend more time.

Thanks,

@DLumi
Copy link

DLumi commented Apr 9, 2024

Hi, @saitarslanboun

Not sure you need this, like, 4 years later, but maybe this would help to someone later on. Generally speaking, any upsampling operations you do in frequency domain (DCT coefficients specifically) do not translate to ones done in spatial domain. So if you need pixel manipulation of any kind, you i-DCT, do your manupulations, and then DCT again.

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