-
Notifications
You must be signed in to change notification settings - Fork 228
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
Error while running the run_demo.py
file for a novel object (model based)
#83
Comments
Is it recommended to edit the dictionary Note: the mentioned dictionary can be found here in the |
I was thinking about the error message, could it be attributed to the mask's file format. The This solved the error, but the tracking was not accurate, I will be sharing the sample video. |
Update: @wenbowen123 I am able to run the model for the novel object (red wooden block), however it is not able ot calculate the 6D pose as well as the Mustard Bottle Demo. The Issue #44 as a reference was really helpful. I have attached the link to the detection and tracking video file as a Google Drive File for your kind reference. |
Hi, your gdrive link is not accessible. |
In args, can you set the debug level to 3 and share the logged debug folder? This will save more running details and I can help check further. |
Thank you for the response. |
demo.py
file on for a novel object errorrun_demo.py
file for a novel object (model based)
From the bbox viz, it seems like your depth could be wrong. However, the zip file does not contain all the debugging info, disallowing me to check further. There should be other things such as scene**.ply files, model_tf.obj, viz_refine.png, viz_score.png, etc. |
The name of the mask should be consistent with the name of the first frame of your rgb image. |
__
The current file used to call the demo is
I have uploaded the new demo Remarks:
Additionally, It would be great if you could guide me to get all the debugging info (and even the __
(DONE) |
@KomputerMaster64 the debugging info are saved in the debug_dir Line 23 in fce37c8
If you didn't change it, by default it is under the repo (where you cloned) dir. |
something wrong is going on, cause even the first frame is not correct. So it's probably not tracking drift, but setup issue. Send the debug folder so I can know better. |
__
Thanks for for the response. __
I have uploaded the new The |
check your ob_mask.png in the debug dir, which seems not aligned with your rgb. It is also skewed. You might have done some unsuitable operation. |
__
Thank you for pointing that out. I changed the scipt for the binary masks generation, the mask now looks more accurate. I have uploaded the new The Remarks: The estimation and tracking are really well for the first few hundred frames, i.e. till image __ __ |
the bottom two images show a significant jump which is not very suitable for tracking. You can increase the camera frame rate if possible. Otherwise, you can also try with higher iter Line 21 in fce37c8
|
Hi @wenbowen123 I am sorry for the delayed response. Regards, __ Remarks: For the shown case, the tracking failure happends towards the end of the samples. The tracking is optimal till image Additional Remarks: This is an improvement it to the first case where I have uploaded the new Question/Note: The total size of the debugging directories for the 49 experiments is 7 GB. It would be great if you could confirm if it is required to share all of the experiments' files. __ |
The
run_demo.py
file was modified for the novel red wooden block object.I have referred to the #44 Issue here which was helpful, however I require further guidance.
I provided respective files for the subdirectories in
rgb
,depth
,mask
, andmesh
. Additionally provided thecam_K.txt
file. I also changed the parser arguments accordingly.I have added the reference files to the Google Drive Folder Here:
run_demo_red_block.py
,cam_K.txt
, AND the other files inrgb
,depth
,mask
, andmesh
have been added.Note: Updated K matrix corresponding to the Intel RealSense Camera by using the command
rostopic echo /camera/color/camera_info
.I am getting the main error as:
I am using an NVIDIA RTX A4500 and an Intel Xeon Silver CPU (details about the hardware have been mentioned at the very end)
Note: Given below are the outputs for
run_demo_red_block.py
command, and the following commands:conda info
,conda list
,g++ --version
,nvcc --version
,lscpu
, andnvidia-smi
.Here is the output for the command
python run_demo_red_block.py
:This is the fulll output of the
python run_demo_red_block.py
file.Here is the output for the command
conda info
:Here is the output for the command
conda list
:Here is the output for the command
g++ --version
:Here is the output for the command
nvcc --version
:Information about the CPU
Intel CPU Information
Information about the GPU
NVIDIA GPU Information
The text was updated successfully, but these errors were encountered: