Skip to content

[HOLD] Evaluate spline initial guesses at collocation points - #1077

Draft
mickaelbegon wants to merge 1 commit into
pyomeca:masterfrom
mickaelbegon:codex/fix-521-collocation-spline-init
Draft

[HOLD] Evaluate spline initial guesses at collocation points#1077
mickaelbegon wants to merge 1 commit into
pyomeca:masterfrom
mickaelbegon:codex/fix-521-collocation-spline-init

Conversation

@mickaelbegon

@mickaelbegon mickaelbegon commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • retain the collocation sub-node index when evaluating spline initial guesses
  • account for the number of collocation points in spline time normalization
  • include the spline time origin instead of assuming it starts at zero
  • add a focused regression test with six distinct values across two intervals

Root cause

Spline initial guesses were accepted for collocation, but all intermediate points within an interval were collapsed onto one shooting-node time. PathCondition.evaluate_at also ignored repeat and the spline time offset.

Validation

  • focused spline unit tests
  • existing collocation/SPLINE OCP regression
  • 3 passed

Progress toward #521.


This change is Reviewable

@mickaelbegon mickaelbegon changed the title Evaluate spline initial guesses at collocation points [HOLD] Evaluate spline initial guesses at collocation points Jul 22, 2026
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.

1 participant