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

Epipolar #114

Open
wants to merge 14 commits into
base: main
Choose a base branch
from
Open

Epipolar #114

wants to merge 14 commits into from

Conversation

mirkoklukas
Copy link
Collaborator

No description provided.

@mirkoklukas
Copy link
Collaborator Author

@mugamma can we try and merge this?

u_ = x * fx / z + cx
v_ = y * fy / z + cy

# TODO: What is the right way of doing this? Returning infs?
Copy link

Choose a reason for hiding this comment

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

I would cull to near and far instead of inf

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@mugamma I am indifferent here. I wanted a value that indicates out-of-bounds explicitly, e.g. when a point is behind the camera, I don't want to lift it to the near plane.

@georgematheos
Copy link
Collaborator

@mirkoklukas Do you know why this PR is changing so many of the imports in the test files? (Maybe is this a fork off of a different branch than the current main, and the new linting tool on main changed the order of the imports on main, so this commit is currently trying to revert this?)

@mirkoklukas
Copy link
Collaborator Author

@georgematheos I have no clue, I can rebase and see if that changes anything

@georgematheos
Copy link
Collaborator

georgematheos commented Aug 22, 2024

@mirkoklukas thanks for checking that!
I would rather align this with the linting rules being checked by the github bot (see above) before merging this.

@mirkoklukas have you switched to the new workflow that @eightysteele set up? This has been resulting in a CLI tool automatically fixing linting issues in the codebase when I commit things.

If it is hard even with this to get the linting fixed we can ask Aaron for help. (I don't know if this tool fixes files not in the current commit which have gotten out of sync with the lint rules.)

@georgematheos
Copy link
Collaborator

@mirkoklukas also, can we please run the tests and make sure they all pass before merging?

@mirkoklukas
Copy link
Collaborator Author

@georgematheos Where is this workflow described?

@mirkoklukas
Copy link
Collaborator Author

I ran the ruff linter locally

@georgematheos
Copy link
Collaborator

@mirkoklukas for the new workflow, see the notion page linked here.

@eightysteele
Copy link
Collaborator

👋 @mirkoklukas let me know if any questions about the workflow—happy to share a screen or give context!

@mirkoklukas
Copy link
Collaborator Author

@eightysteele thanks! I will have a look at the doc first, and see if anything is unclear or I am running into trouble.

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