-
Notifications
You must be signed in to change notification settings - Fork 56
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
Question about metadata #8
Comments
Thank you for your interests in our work.
|
Thank you very much. One more question with respect to TopDownTransformation. For the provided example the corresponding matrix is 3x4: 47.41009728,11.82066487,0., 182.75689221 According to your previous answer, 3rd element of 3rd row shouldn't be 1 instead of 0? Moreover 4th column corresponds to some kind of transalation or something else? |
Oh, yes. The fourth column is the translation which I forgot to mention. Basically the equation is xR(x - t). Indeed, the 3rd element of the 3rd row should be the scaling factor. But here the way we dealt with the z-axis is a bit messy. Since we didn't save the transformation matrix properly (missing the scaling factor for z-axis) and later we wanted to apply the same scaling factor to all axes, we decompose the transformation to use only the rotation and translation part and re-compute the scaling factor. Please see the code here for details. Thanks for bringing up this issue! |
Hello again. During more thorough investigation of the code I realized that scale of the data to 0-1 is actually happened within the following code snippet. Is this correct? Lines 310 to 320 in e7bd879
Then what is the purpose of the previous scaling, encoded within the globalTransformation matrix? For your example the scaling factor is 48.86149243. Is there a reason why you have to scale data from meters (as the mesh in tango obj is)? I can't get it because as far as I am concerned data at this scale are never used, because they are immediately re-scaled to 0-1. Nevertheless if I omit such strange scale (by decomposing the matrix) and putting scale=1 to all dimensions, the prediction of the network does not contain any walls (resulting to key error within a dictionary in your code). The same happens for data which I have obtained on my own. Thanks in advance. |
Where can we find the definitions of 'topDownTransformation', 'topDownViewAngle', 'videoOrientation' included in "metadata.t7", so that we could attempt to run FloorNet on data that we acquire on our own?
The text was updated successfully, but these errors were encountered: