ayaanzhaque / instruct-nerf2nerf

Instruct-NeRF2NeRF: Editing 3D Scenes with Instructions (ICCV 2023)
https://instruct-nerf2nerf.github.io/
MIT License
769 stars 64 forks source link

ns-train in2n error; loaded pretrained model results bad. #92

Open chkmook opened 4 months ago

chkmook commented 4 months ago

It seems that the Instruct-nerf2nerf pipeline is not properly loading the pre-trained nerfacto model.

The first image is the result of ns-viewer with pre-trained nerfacto model. The second image is the rendered image before training “ns-train in2n” with pre-trained nerfacto model.

A few weeks ago, I confirmed that it was working properly with same script file, but after downloading the repo again and checking, I cannot see the same results as before.

When looking at the results of the viewer(upper image), it seems that nerfacto has been trained well, but when looking at the initial nerf rendered image of in2n(below image), it seems that the pre-trained nerfacto model is not being properly loaded. Is there anything missing or something I should check?

The setup follows the Torch 2.1.2 with CUDA 11.8 settings from https://docs.nerf.studio/quickstart/installation.html. After installing nerfstudio, I downloaded the instruct-nerf2nerf repo again to ensure that in2n could function properly.\

Screenshot 2024-02-22 at 12 15 47 AM Screenshot 2024-02-22 at 12 14 05 AM
ayaanzhaque commented 4 months ago

So the issue here is that once you train nerfacto and then render it after loading it, the results look worse here?

chkmook commented 4 months ago

Yes. From the results rendered in the viewer, I think there are no issues in the pretraining process of Nerfacto model. But, the results look worse when loaded at in2n pipeline.

ayaanzhaque commented 4 months ago

That is super odd. Is this after some iterations of in2n have been run or no?

chkmook commented 4 months ago

Yes. This is the result from right after starting.

ayaanzhaque commented 4 months ago

have u tried it after letting it train for some time? not sure why this would be the case, but maybe the first few iterations of in2n updates kinda mess things up. You can also launch with pausing the training or in inference mode so that you can see before any in2n steps are done

chkmook commented 4 months ago

I'll try pausing the initial iterations of training and use it later. Thank you for answering!