Skip to content

Added polyline interpolation (in the new lane_helpers sub-package)#29

Open
RmSchaffert wants to merge 1 commit into
NVIDIA:mainfrom
RmSchaffert:lane_helpers_polyline
Open

Added polyline interpolation (in the new lane_helpers sub-package)#29
RmSchaffert wants to merge 1 commit into
NVIDIA:mainfrom
RmSchaffert:lane_helpers_polyline

Conversation

@RmSchaffert

@RmSchaffert RmSchaffert commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

Description

Added a new lane_helpers package with polyline interpolation as the first contained functionality

Type of Change

Please select (at least one):

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation / examples / tutorials / demos
  • Supporting functionality change (fix or feature in documentation generation, helper scripts, ...)
  • Refactoring / internal change
  • Other (please describe):

Testing

Checklist for testing:

  • Tests added or updated if/as needed
  • Repository test runner executed: scripts/run_tests.sh

Optionally, add a brief description.

Documentation, Examples, Tutorials, Demos

Checklist for documentation:

  • User-facing documentation updated if/as needed (including API docs)
  • Examples / tutorials / demos updated or added (if relevant)
  • Limitations and constraints documented (if relevant)
  • Performance documented (if relevant)
  • Documentation building successful & checks outlined in the Documentation Checks section of the Contribution Guide are performed

Optionally, add a brief description.

Code Quality

Checklist for dependencies:

  • Dependencies updated in the relevant pyproject.toml if/as needed
  • Code formatted according to the Code Formatting Guide

Optionally, add a brief description.

Related Issues / Context

If applicable, link related issues, discussions etc.


DCO / Sign-Off

Please refer to the section on Signing Your Work & Developer Certificate of Origin (DCO)
in the Contribution Guide before submitting your contribution.

References

For additional details, please refer to the Contribution Guide.
The following guides are available (referenced in the Contribution Guide for further details):

Please also refer to the summary checklist in the Contribution Guide,
which is a guideline for what to consider when submitting your contribution and covers the same topics as the checklists above.

@RmSchaffert

Copy link
Copy Markdown
Collaborator Author

/build

@RmSchaffert RmSchaffert force-pushed the lane_helpers_polyline branch from f5f64ed to c78240b Compare June 10, 2026 07:54
@RmSchaffert

Copy link
Copy Markdown
Collaborator Author

/build

Signed-off-by: Roman Schaffert <rschaffert@nvidia.com>
@RmSchaffert RmSchaffert force-pushed the lane_helpers_polyline branch from c78240b to b04b055 Compare June 11, 2026 03:09
@RmSchaffert

Copy link
Copy Markdown
Collaborator Author

/build

1 similar comment
@RmSchaffert

Copy link
Copy Markdown
Collaborator Author

/build

@RmSchaffert RmSchaffert marked this pull request as ready for review June 15, 2026 09:51
@RmSchaffert RmSchaffert requested a review from xupinjie June 16, 2026 02:00
Comment on lines +23 to +26
if (err != cudaSuccess) { \
fprintf(stderr, "CUDA error: '%s' in '%s' at line %d\n Description: %s\n", \
cudaGetErrorName(err), __FILE__, __LINE__, cudaGetErrorString(err)); \
exit(err); \

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Exiting directly is dangerous. The caller should catch the exception in Python.

Comment on lines +32 to +35
if (err != cudaSuccess) { \
fprintf(stderr, "CUDA error: '%s' in '%s' at line %d\n Description: %s\n", \
cudaGetErrorName(err), __FILE__, __LINE__, cudaGetErrorString(err)); \
exit(err); \

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

same as above

Comment on lines +47 to +66
AT_ASSERTM(tensor.is_cpu() || tensor.is_cuda(), description, " must be on CPU or CUDA");
}

inline void check_contiguous(const at::Tensor& tensor, const char* description) {
AT_ASSERTM(tensor.is_contiguous(), description, " must be contiguous");
}

inline void check_type(const at::Tensor& tensor, const char* description) {
if (tensor.is_cuda()) {
AT_ASSERTM(tensor.scalar_type() == torch::kFloat32 || tensor.scalar_type() == torch::kFloat64 ||
tensor.scalar_type() == torch::kFloat16 || tensor.scalar_type() == torch::kBFloat16,
description, " must have dtype float16, float32, float64, or bfloat16 on CUDA");
} else {
AT_ASSERTM(tensor.scalar_type() == torch::kFloat32 || tensor.scalar_type() == torch::kFloat64,
description, " must have dtype float32 or float64 on CPU");
}
}

inline void check_same_device(const at::Tensor& lhs, const at::Tensor& rhs, const char* message) {
AT_ASSERTM(lhs.device() == rhs.device(), message);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

pytorch/pytorch#20287
AT_ASSERTM looks like a error usage.

@RmSchaffert RmSchaffert mentioned this pull request Jun 23, 2026
16 tasks
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.

2 participants