-
Notifications
You must be signed in to change notification settings - Fork 94
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
Deciding on SPACE_SIZE and SPACE_CENTER #10
Comments
It depends on the calibration results. The basic idea is to calculate a 3D bounding box which covers the whole motion space. Then SPACE_CENTER denotes the center coordinate of the box and SPACE_SIZE denotes the lengths of the box. |
I see thank you. In that case making this box a little bit bigger than it needs to be should not degrade the performance right? |
That's right. But you may need to consider the size of each voxel (which depends on the box size and number of voxels) as that affects the quantization error. |
hi, @egeozsoy .What's your trainsets and testsets? Your custom datasets or open-source datasets? Did you implement the cross-datasets evaluation. |
I am also facing the same issue with a custom datasets?
|
I have a custom dataset that I want to apply voxelpose to. But there is no explanation for how the values SPACE_SIZE and SPACE_CENTER were selected for the 3 datasets, therefore it is not clear to me what to set them to for my custom dataset
The text was updated successfully, but these errors were encountered: