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

Start moving Sim(3) functionality into Python wrapper #700

Closed
wants to merge 1 commit into from

Conversation

johnwlambert
Copy link
Contributor

  • Sim(3) may be useful to us in GTSFM. Exposing some of its functionality to the wrapper.

@johnwlambert
Copy link
Contributor Author

Hi @dellaert , is there a particular bug that is keeping Sim(3) from being moved out of gtsam_unstable into the gtsam directory?

@johnwlambert
Copy link
Contributor Author

Hi @dellaert , is there a particular bug that is keeping Sim(3) from being moved out of gtsam_unstable into the gtsam directory?

@dellaert a gentle reminder to take a look at this when you get a moment. Thanks!

Copy link
Contributor

@akshay-krishnan akshay-krishnan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this if #702 is submitted?

Comment on lines +171 to +172
Similarity3(const Matrix& R, const Vector& t, double s);
Similarity3(const Matrix& T);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these constructors check the size of the matrix?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They don't. In the whole gtsam.i file actually only Matrix & T or Vector & t is used, and Matrix3 etc throws a compilation error

@johnwlambert
Copy link
Contributor Author

Do we need this if #702 is submitted?

702 is a work in-progress...currently broken. Was just trying to make some small PRs to slowly get it integrated

@akshay-krishnan
Copy link
Contributor

We may not need to wrap it in unstable if we can move it outside. Unless that will take time and we need this quick.

@varunagrawal
Copy link
Collaborator

Is this PR still needed given #702?

@johnwlambert
Copy link
Contributor Author

Is this PR still needed given #702?

No, I'll close it.

@varunagrawal varunagrawal deleted the sim3-constructors-wrapper branch October 22, 2023 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants