Skip to content

fix: handle zero-blend trapezoidal velocity boundary - #934

Open
tandede wants to merge 1 commit into
petercorke:mainfrom
tandede:fix/trapezoidal-zero-blend
Open

tandede wants to merge 1 commit into
petercorke:mainfrom
tandede:fix/trapezoidal-zero-blend

Conversation

@tandede

@tandede tandede commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Summary

  • treat the accepted lower velocity boundary as a constant-velocity zero-blend profile
  • add forward and reverse regression coverage

Behaviour change

The accepted zero-blend velocity boundary now returns finite position, velocity and acceleration values instead of NaN/inf. Public signatures are unchanged.

Fixes #924.

Testing

  • Focused trajectory tests: 3 passed, 6 subtests passed
  • Ruff formatting and focused lint checks on the changed files
  • git diff --check

Prepared with substantial assistance from OpenAI Codex (GPT-5); I reviewed and ran the change.

Co-Authored-By: OpenAI Codex (GPT-5) <noreply@openai.com>
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

This branch has not been deployed

No deployments
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.

trapezoidal accepts the zero-blend velocity boundary but returns NaN at the initial sample

1 participant