Skip to content

[float32] CG/Newton solver terminates early due to improvement overshoots #2313

Open
@n3b

Description

@n3b

Intro

My setup

What's happening? What did you expect?

I believe an abs() is missing here

mjtNum improvement = scale * (oldcost - ctx.cost);

There are serious stability issues otherwise that can be seen in cases like throwing 10+ perfectly aligned cubes on top of each other.

Steps for reproduction

Minimal model for reproduction

No response

Code required for reproduction

No response

Confirmations

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions