Closed wangyida closed 1 year ago
Hi! It seems that this new up_est_method rotates the average camera up direction to +z. May I ask how this is different from up_est_method == 'camera'
?
Hi Benny, the difference is that when camera is not positioned evenly surrouding the central object, e.g. the distance is not the same, camera
setup will make the object tilted against z axis. the new axis-z
setup will still position the object straight up along z axis.
I see. Could you keep the config files unchanged and only modify the dataset? Also, is there an example scene illustrating the difference between the two methods so that I can test (for example some scene in Mip-NeRF360 dataset)?
Sure I can do it on bonsai scene
When ground is included, the new up direction option axis-z
behaves similarly with ground
. BTW you may need a light github theme to view this figure, the captions are with transparent background.
Sorry I totally forgot about this PR 😂 Thank you very much for the newly added features, and I'll look into the code soon.
Guess a naive implementation for point
center should be conditioned on points of sparse MVS reconstruction instead of cameras @bennyguo
@bennyguo there are some new functions added, you mind review a bit further to see which of these modules are useful?
Adding a new up_est_method
z-axis
, so that the normalized poses could be always with an averaged up-direction of [0,0,1] as mentioned by nerf2mesh, even when ground is missing in the training data. Suchz-axis
behaves similarly withground
when ground is included in the training data.z-axis
up-directionz-axis
test for - ✅ mipnerf360 ✅ synthetic nerfz-axis
with - ✅ camera ✅ point ✅ lookatExtensions