Skip to content

Conversation

@j-c-c
Copy link
Collaborator

@j-c-c j-c-c commented May 14, 2024

Port of the D2 common-lines algorithm for orientation estimation.

@j-c-c j-c-c added the enhancement New feature or request label May 14, 2024
@j-c-c j-c-c self-assigned this May 14, 2024
@j-c-c j-c-c force-pushed the D2_cl branch 2 times, most recently from 265394c to becf281 Compare June 5, 2024 18:57
@j-c-c j-c-c force-pushed the D2_cl branch 2 times, most recently from 09c400d to 86cf378 Compare June 17, 2024 17:17
@j-c-c j-c-c requested a review from garrettwrong June 17, 2024 18:23
Copy link
Collaborator

@garrettwrong garrettwrong left a comment

Choose a reason for hiding this comment

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

Thanks for putting this together. I understand you had success validating against MATLAB, which is great. This looks like a rough but workable initial python port. There is still quite a bit of code cleanup to do here. I highlighted places that stuck out to me. Because of the verbosity of the code and the amount of changes needed I didn't really dig in too deeply yet.

My advice would be to codify any additional (repro) tests you have, even if it isn't part of the PR, then begin cleaning up the minor/benign/reshape sort of changes before moving on to the more complicated broadcasts... checking you still repro along the way. I think you will find the volume of code can be reduced quite a bit. Let me know if you have any questions about the vectorizing hints.

@j-c-c
Copy link
Collaborator Author

j-c-c commented Aug 27, 2024

@garrettwrong this is ready for you to take another look. I've addressed all of your comments. There are a couple changes that I've refrained from making to maintain exact outputs for this first set of changes (I've noted where this is the case).

@garrettwrong
Copy link
Collaborator

Awesome! I'll start working on it next after I get the sync3n back to Joakim.

Copy link
Collaborator

@garrettwrong garrettwrong left a comment

Choose a reason for hiding this comment

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

Okay, just couple stragglers and a few items that are marked to fix at the end of the review process.

I'm guessing you want to go through the Joakim review process before making changes that might cause differences from the MATLAB repro?

@j-c-c
Copy link
Collaborator Author

j-c-c commented Sep 5, 2024

@garrettwrong I reverted the search radius to r=2 since it was breaking a test. I'll have to take a closer look after lunch

@j-c-c
Copy link
Collaborator Author

j-c-c commented Sep 10, 2024

@garrettwrong I reverted the search radius to r=2 since it was breaking a test. I'll have to take a closer look after lunch

Turns out it wasn't this search radius breaking the test. Put this back to what we discussed, ie. np.ceil(2 * n_theta / 360).

@j-c-c j-c-c requested a review from garrettwrong September 11, 2024 12:58
garrettwrong
garrettwrong previously approved these changes Sep 11, 2024
@j-c-c j-c-c marked this pull request as ready for review September 11, 2024 14:07
@j-c-c j-c-c requested a review from janden as a code owner September 11, 2024 14:07
Copy link
Collaborator

@janden janden left a comment

Choose a reason for hiding this comment

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

Congratulations on putting this together! I can't say that I'm able to follow all the details, but here are a couple of questions and comments. Nothing big here.

janden
janden previously approved these changes Sep 19, 2024
@j-c-c j-c-c merged commit f31d317 into develop Sep 20, 2024
@garrettwrong
Copy link
Collaborator

🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants