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

Difference pose between gt and render images #43

Closed
Gaaaavin opened this issue Aug 8, 2024 · 1 comment
Closed

Difference pose between gt and render images #43

Gaaaavin opened this issue Aug 8, 2024 · 1 comment

Comments

@Gaaaavin
Copy link

Gaaaavin commented Aug 8, 2024

I was able to train the model smoothly with my own data. But I have a problem when I tried to render the images from the trained model.
I tried to run the following code:

python render_hierarchy.py -s ${DATASET_DIR} --model_path ${DATASET_DIR}/output --hierarchy ${DATASET_DIR}/output/merged.hier --out_dir ${DATASET_DIR}/output/renders --scaffold_file ${DATASET_DIR}/output/scaffold/point_cloud/iteration_30000

The is the same as that from the bottom of the readme, except that without the --eval flag. I changed this because I didn't use the --eval flag when training and I don't have the test.txt file.

However, I find that the rendered images and the gt images have a different pose. For example, the following two images are the first image in my data.
imageimage

Please let me know what is the code that I should modify.

@Gaaaavin
Copy link
Author

Gaaaavin commented Aug 8, 2024

It turns out the problem was introduced by using the pose before reorientation (i.e. from the rectified folder, instead of the aligned folder).
To successfully run the hierarchical rendering for the whole scene, you need to have images and sparse folder under DATASET_DIR, which doesn't exist if you follow the data preparation procedure.
My solution is to create symbolic links to the folder. Go to your DATASET_DIR and run

ln -s camera_calibration/aligned/sparse/ sparse
ln -s camera_calibration/rectified/images/ images

This should solve the problem.

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

1 participant