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

Suggestions asking for inputting data #9

Open
RoveFlemington opened this issue Oct 25, 2024 · 2 comments
Open

Suggestions asking for inputting data #9

RoveFlemington opened this issue Oct 25, 2024 · 2 comments

Comments

@RoveFlemington
Copy link

RoveFlemington commented Oct 25, 2024

Are there any special suggestions for inputting burst images, such as should the camera movement/tremor avoid being too large?? Actually, in my testing, significant optical flow changes make my reconstructed background image blurry.

@RoveFlemington
Copy link
Author

test_result

@Ilya-Muromets
Copy link
Contributor

Absolutely, I kind of go over this in the supplemental section of the paper: https://light.princeton.edu/wp-content/uploads/2023/12/neural-spline-fields.pdf

But the gist of it is that NSF is a very simple stochastic optimization model, you're kind of relying on it falling into a local optima (separating the occlusion from the transmission) based on millions of small updates. If that optimum is too far away from the initialization (e.g., your camera moves a lot), then there's a good chance the model will never find it.

As a rule of thumb, it seems to do fairly well when the motion is on the scale of the occlusion (e.g., if you have a fence that's X pixels wide, then during the burst it should ideally move between X and 3X pixels up/down/left/right to be well reconstructed).

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