Skip to content

Send FourPost bar rates only to the rig bars that exist - #154

Merged
raorjun merged 1 commit into
fix/runner-overridesfrom
fix/fourpost-bar-rates
Oct 29, 2026
Merged

raorjun merged 1 commit into
fix/runner-overridesfrom
fix/fourpost-bar-rates

Conversation

@raorjun

@raorjun raorjun commented Oct 25, 2026 •

Copy link
Copy Markdown
Member

What

FourPost sent each bar rate to both pFrStabar.barRate and pVehicle.pFrStabar.barRate. The rig binds only pFrStabar. A run without the pVehicle override is bit-identical. FourPost also sent a rate for an axle with no bar, which the stricter runner (PR 2 of this stack) would reject.

Changes

FourPost sends the rig bar rate only, and only for an axle that has a bar.

How to check

A new test in tests/test_kinematics.py. Robert's spring-curve test still passes.

Notes

Stack

3 of 7.

FourPost sent each bar rate twice, to pFrStabar.barRate and to
pVehicle.pFrStabar.barRate. The rig binds only pFrStabar. The executable
logs the pVehicle override as applied, but it changes no output: a run
without it gives bit-identical results. It also sent a rate of 0 for an
axle with no bar, where the template value is already 0.

Now FourPost sends the rig bar rate only, and only for an axle that has
a bar in the vehicle file.
@raorjun
raorjun added this pull request to stack #159 October 25, 2026 00:43
@raorjun
raorjun requested a review from rhorvath02 October 25, 2026 02:44
@raorjun
raorjun merged commit 0b96c31 into main Oct 29, 2026
5 of 6 checks passed
@raorjun
raorjun deleted the fix/fourpost-bar-rates branch October 29, 2026 22:20
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