MultiEigenStepperLoop returns position not on surface while components are

[andiwand]

Taking about cylinders... with curved surfaces the MultiEigenStepperLoop can end up reporting being on surface while the position is not because we average in global coordinates which pulls you a bit off surface.

This confuses the navigation and in #3437 results in endlessly trying to target a boundary we are actually sitting on.

I think @asalzburger suggested once to average the components on the surface and then transform to global. Is that possible @benjaminhuth?

Alternatively I can also increase the near limit for now so those intersection would not be seen by the navigator. But ultimately this problem cannot be solved by the navigator itself in my opinion.

[andiwand]

The problem can be observed here #3442

[github-actions]

This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.

[AJPfleger]

Let's recheck if this is fixed. @andiwand @benjaminhuth

[github-actions]

This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.