Closed miguelriemoliveira closed 2 years ago
How did I not obtain that?
Maybe you improved your datasets and they are different?
Maybe you improved your datasets and they are different?
That might be it! I spent some time on dataset reviewer for both train and test dataset
rosrun atom_evaluation icp_calibration.py -j $ATOM_DATASETS/larcc_sim/train_dataset/dataset_corrected.json -ss depth_camera_1 -st lidar_2 -nig 0.1 0.1 -seed 2
yeah, maybe that's difference :/
rosrun atom_evaluation lidar_to_depth_evaluation -train_json $ATOM_DATASETS/larcc_sim/train_dataset/ICPCalibration_average_depth_camera_1_lidar_2.json -test_json $ATOM_DATASETS/larcc_real/test_dataset/dataset.json -ld lidar_2 -cs depth_camera_1
You were comparing a simulation calibration with a real test dataset! That might be it!
Again, that was a me coping the wrong command...
If you want, I can do it!
If you want, I can do it!
I know you have a lot to do... I just don't understand why the values are so different between you and me. It doesn't make sense to put this on the paper if I'm doing it wrong
I just don't understand why the values are so different between you and me
Neither do I.
It doesn't make sense to put this on the paper if I'm doing it wrong
Then I can do it. It's only three calibration procedures!
I just don't understand why the values are so different between you and me
Neither do I.
I'm sure I must be doing something wrong.
It doesn't make sense to put this on the paper if I'm doing it wrong
Then I can do it. It's only three calibration procedures!
It's actually 6... 3 for simulation and 3 for real.
Thanks to both. If you need help let me know.
Thanks Manuel. Looks good.
On Sun, May 22, 2022, 20:44 Manuel Gomes @.***> wrote:
Hello! I corrected the bug and added some suggestions:
- Now manual alignment is a flag from argparse -ma, which only runs if called. This results in only 2 calibrations being saved now, the average and the best one. If no -ma flag is presented, it uses the initial estimate. If it is present, manual alignment takes place and that is used as a starting point
- The subsampling is now a flag from argparse -ssd, where the user can define the subsampling it wants, due to the demanding computational capacity needed to run with all the points generated by the depth image
- The function depthToPointArray has been renamed to depthToNPArray, and no longer has the full_image input. It now demands the indexes to be converted as an input
- All functions are in camelCase (#475 https://github.com/lardemua/atom/issues/475)
- Better comments
I believe this is it. Tommorow I will take some results!
— Reply to this email directly, view it on GitHub https://github.com/lardemua/atom/issues/463#issuecomment-1133960925, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWTHVTQVRBMGPACTUHXIH3VLKFDHANCNFSM5WITGVUA . You are receiving this because you were mentioned.Message ID: @.***>
For the same initial estimate, this was the result. It's bad, but not as bad as yours. Let me try it with manual alignment.