We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, 我想请教一下如何生成ObjectNeRF场景编辑时,所需的bbox.json文件,或者能解释一下bbox.json里面各个数值的含义吗? 下面是bbox.json的内容 "labels": [ { "id": "1", "data": { "position": [ 2.2837844942793737, 0.6488003671313685, 6.001685665511459 ], "rotation": [ 1.8946632971215467, -0.1095624676165341, 0.553559251247026 ], "quaternion": [ 0.771054293372373, -0.2522670140662573, 0.11654286129474664, 0.5729348931312866 ], "scale": [ 3.9938567122761546, 1.853964693824193, 1.8692240780858735 ] } },
"labels": [ { "id": "1", "data": { "position": [ 2.2837844942793737, 0.6488003671313685, 6.001685665511459 ], "rotation": [ 1.8946632971215467, -0.1095624676165341, 0.553559251247026 ], "quaternion": [ 0.771054293372373, -0.2522670140662573, 0.11654286129474664, 0.5729348931312866 ], "scale": [ 3.9938567122761546, 1.853964693824193, 1.8692240780858735 ] } },
The text was updated successfully, but these errors were encountered:
这里是一个描述当前物体在3D空间中对于该物体的3D Bounding Box的一些信息:id代表第几个物体,position代表这个3D bbox的中心,scale表示3D bbox的3个方向的边长(长/宽/高),rotation和quaternion表示这个3D Bbox的旋转。
这些量应该可以用一些3D位姿估计的方法得到,例如PVNet或者Onepose++等。具体方法的选择可以尝试下不同的方案。
Sorry, something went wrong.
您好,感谢您的解答。 有几个问题想请教您。 我现在通过人工标注,可以得到在相机坐标系下的3D bbox的信息,但是不知道怎么转换成bbox.json的形式。
Hi,
No branches or pull requests
Hi,
我想请教一下如何生成ObjectNeRF场景编辑时,所需的bbox.json文件,或者能解释一下bbox.json里面各个数值的含义吗?
下面是bbox.json的内容
"labels": [ { "id": "1", "data": { "position": [ 2.2837844942793737, 0.6488003671313685, 6.001685665511459 ], "rotation": [ 1.8946632971215467, -0.1095624676165341, 0.553559251247026 ], "quaternion": [ 0.771054293372373, -0.2522670140662573, 0.11654286129474664, 0.5729348931312866 ], "scale": [ 3.9938567122761546, 1.853964693824193, 1.8692240780858735 ] } },
The text was updated successfully, but these errors were encountered: