Skip to content
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? transPoseFwd #1

Closed
maxpy opened this issue Aug 27, 2015 · 6 comments
Closed

error? transPoseFwd #1

maxpy opened this issue Aug 27, 2015 · 6 comments
Labels

Comments

@maxpy
Copy link

maxpy commented Aug 27, 2015

Error using transPoseFwd (line 14)
length(T) must be the same as size(oldPose,1)!

what's wrong?

@zhusz
Copy link
Owner

zhusz commented Aug 27, 2015

Never reproduced
Could you provide more details like the call stack info etc

@zhusz zhusz closed this as completed Aug 27, 2015
@zhusz
Copy link
Owner

zhusz commented Sep 1, 2015

First, at my side I never observe such error and hence I cannot give explicit explanation to the problem.
Since I have received more than two bug reports on the same issue in function getTransViaMerge, I believe there might be something wrong in it. Currently I did some modification to the function and I believe the problem might be solved.

@maxpy
Copy link
Author

maxpy commented Sep 1, 2015

Thank you to answer my question , I solve the problem with matlabpool;
Thanks

@zhusz
Copy link
Owner

zhusz commented Sep 1, 2015

Yes! That is precisely the cause! Thank you very much for the discovery.
The problem is due to our very old version of codes (without using parpool) that output row vector of transform objects rather than a column vector, a standard form we apply in our subsequent implementations. Hence, other functions would prompt error if they find the size of the first dim of transformation objects is not equal to the number of samples.
Since we always use matlabpool enabled environment all later, we didn't find the problem until now.
So, to force all Ts in getTransViaMerge to be column vector seems to be the fastest way of solving the problem.
Sincerely thanks to your discovery!

@maxpy
Copy link
Author

maxpy commented Sep 1, 2015

You're welcome. BTW ,Thanks to your open source code. Great job!

@zhusz
Copy link
Owner

zhusz commented Sep 1, 2015

Thanks for you appreciation! :)
We are so glad to find that our codes can provide help to this area.

@zhusz zhusz added the bug label Jan 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants