Open cmanszew opened 7 months ago
Hi, I will check these codes in these several days. The problem may cause by data preprocessing, or caused by pose inaccuracy problem, since inaccurate poses would deteriorate the results significantly.
One problem that I find out is the weight for the 3D object detection. Since this weight is trained on synthetic data. It would be better to use the detection model from the IM3D repository, which is also used by myself to generate detection results on real images such as images from SUNRGBD.
So I managed to correct few issues - those suspicious multiplications turn out to be the culprit. I still wonder how your original code, that multiplies the intrinsic camera matrix and box feats by 2, works. With those removed from my code the output looks closer to what I'd expect.
After that I tried to use the detection model from IM3D repository but unfortunately the weights are not compatible with your implementation. So one would need to use the code from IM3D and that's where I got stuck, since Im3D processes the output data quite differently.
Hi, I will release my code for im3d inference later.
I have already checked my code using im3d for inferencing, it should be quite the same as the original Im3D code which is here You can check if this can yield correct results. The config file is in ./configs/test_detection.yaml. And remember to modify the weight to the weight downloaded from the IM3D repository. You should be able to obtain good results if the 2D detections are correct. The intrinsic needs to be diviede by 2 only for 3D-Front dataset, because the image in the downsampled image in 3D Future are downsampled by half compared to the original image. It is not neccessary for SUNRGBD dataset. However, if you are using web image, you should need to make sure to input the correct intrinsic of the camera (depending on the camera device). Also, in the dataloader, the intrinsic needs to be scaled to so align with the scaled image (175 line in sunrgbd_dataset.py).
If more information is needed, please feel free to contact me.
Hi! I was working some time to create a demo mode, for reconstruction from arbitrary image similar to Total3D and Implicit3D. I followed your data pre-processing code but unfortunately it's not always clear, it seems to rely on pre-processed data. I've got something working, but the end result is not correct, or at least the object pose/scene layout is wrong.
The code I wrote is in: https://github.com/cmanszew/InstPIFu/tree/rgb-demo
To run it with 1st demo input from Implicit3D, just run:
python experiments.py
using the same environment as for the rest of your code.Below is the comparison of InstPIFu vs Implicit3D from raw RGB input:![Screenshot from 2024-01-21 19-35-49](https://github.com/GAP-LAB-CUHK-SZ/InstPIFu/assets/26208674/b66cd516-18f0-48eb-909a-34deda1547d1)
For this input:![img](https://github.com/GAP-LAB-CUHK-SZ/InstPIFu/assets/26208674/e643751a-3eea-4b58-9578-f56f942f8b93)
The issue probably lies somwhere in the way I:
Like I said, this code tries to follow your code, but sometimes there was scaling and other operations perfomed on already pre-processed data, not raw input. I would appreciate any help on this. Perhaps also we could merge this to your repo with my issue fixed after I add bg reconstruction to it =)