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

A few clarifications regarding the function lf_reparam_tf #1

Open
asprasan opened this issue Jun 1, 2019 · 2 comments
Open

A few clarifications regarding the function lf_reparam_tf #1

asprasan opened this issue Jun 1, 2019 · 2 comments

Comments

@asprasan
Copy link

asprasan commented Jun 1, 2019

I read your paper and then tried to implement your code. I was going through the function lf_reparam_tfand I got stuck trying to figure out what exactly is going on. The first question that I have is that why are you multiplying the plane co-ordinates u and v with the camera parameter aperture_res while reparameterizing the light field? What exactly does the parameter aperture_res signify?

Also, in the paper, while generating the blurred image, the plane co-ordinates x and y are not reparameterized. However, in the code, I see that x and y are also getting reparameterized along with u and v. Why is it so?

@NagatoYukisan
Copy link

Have you solved this problem? I have the same question?

I read your paper and then tried to implement your code. I was going through the function lf_reparam_tfand I got stuck trying to figure out what exactly is going on. The first question that I have is that why are you multiplying the plane co-ordinates u and v with the camera parameter aperture_res while reparameterizing the light field? What exactly does the parameter aperture_res signify?

Also, in the paper, while generating the blurred image, the plane co-ordinates x and y are not reparameterized. However, in the code, I see that x and y are also getting reparameterized along with u and v. Why is it so?

@asprasan
Copy link
Author

asprasan commented May 8, 2021

Sorry. I did not figure this issue out.

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