-
Notifications
You must be signed in to change notification settings - Fork 71
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
How to choose the variacne of 2D Mip Filter ? #18
Comments
In case anyone's interested, here are benchmarks with kernel size = 0.1 vs 0.3 0.1 is a clear winner on synthetic, but much less on real data benchmark_nerf_synthetic_ours_mtmt: Multi-scale Training and Multi-scale Testing on the Mip-NeRF 360 dataset PSNR:
SSIM:
LPIPS:
Count:
benchmark_nerf_synthetic_ours_stmt: Single-scale Training and Multi-scale Testing on the Mip-NeRF 360 dataset PSNR:
SSIM:
LPIPS:
Count:
benchmark_360v2_ours: Multi-scale Training and Multi-scale Testing on the the Blender dataset PSNR:
SSIM:
LPIPS:
Count:
benchmark_360v2_ours_stmt: Single-scale Training and Multi-scale Testing on the the Blender dataset PSNR:
SSIM:
LPIPS:
Count:
|
Thanks for your great work! I understand more about 3dgs from your work!
In 6.1 Implementation,
We choose the variance of our 2D Mip filter as 0.1, approximating a single pixel
My questions:
How to deduce from
a single pixel
to0.1
value?By the way, what is the unit of
0.1
?In my understande:
$(x_0, x_1)$ plane of ray space occupies a aingle pixel?
In computeCov2D function, cov[0][0] += kernel_size; means the scale (or unit) of kernel_size and cov should be the same, because they can add together.
cov
is the covariance in ray space. So the unit of 0.1 should be the unit in ray space. But why 0.1 inFrom Fig. 8 ray space. of EWA Splatting
Thanks!
The text was updated successfully, but these errors were encountered: