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

Accelerating and testing point cloud building #519

Merged
merged 10 commits into from
Aug 27, 2024

Conversation

livaage
Copy link
Contributor

@livaage livaage commented Aug 21, 2024

closes #518

feat: Reducing point cloud build runtime by 3x
feat: Added more testing for point cloud building
chore: Removed coverage tests since it conflicted with pycharm's debugger (might solve and add back later)

dependabot bot and others added 4 commits August 19, 2024 09:13
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 4.4.1 to 4.5.0.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@v4.4.1...v4.5.0)

---
updated-dependencies:
- dependency-name: codecov/codecov-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@livaage livaage changed the title Timing studies small update Accelerating point cloud building and adding more testing Aug 22, 2024
@livaage livaage changed the title Accelerating point cloud building and adding more testing Accelerating point and testing cloud building Aug 22, 2024
@livaage livaage changed the title Accelerating point and testing cloud building Accelerating and testing point cloud building Aug 23, 2024
Copy link
Member

@klieret klieret left a comment

Choose a reason for hiding this comment

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

Awesome, congrats to your first PR, great to speed this up!

Small clarification for the truth edge building though: This is of course only part of the training dataset (need it to speed up the loss functions); it will not influence inference time.

@@ -38,7 +38,3 @@ jobs:
- name: Test with pytest
run: |
pytest
- name: Explicitly convert coverage to xml
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this can possible conflict with the pycharm debugger (but yeah, removing it from the pyproject.toml might be required).

@@ -1,6 +1,6 @@
[tool.pytest.ini_options]
minversion = "6.0"
addopts = ["--cov=gnn_tracking", "-ra", "--strict-markers", "--strict-config"]
Copy link
Member

Choose a reason for hiding this comment

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

You could also do this instead: https://stackoverflow.com/questions/45597357/pycharm-intellij-shows-0-coverage-for-pytest-even-though-coverage-was-generated (I think that's what I did before I switched to vscode)

@livaage livaage merged commit 06d9a41 into gnn-tracking:main Aug 27, 2024
2 of 3 checks passed
livaage added a commit to livaage/gnn_tracking that referenced this pull request Aug 28, 2024
Merge pull request gnn-tracking#519 from livaage/timing_studies
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.

Improving point cloud testing
2 participants