Repository navigation
Fix hoverslam controller for singular guidance - #2339
Merged
Merged
Conversation
Inside the RK problem the guidance becomes singular right at the end of it, which results in lots of CPU utilization and throwing on launch when things go wrong. Also be more careful about entering the propagator past the event and cleanup the remaining landing analytically. Cuts several successful tests down to <10ms from ~100ms as well, so this module should be less of a CPU hog.
Contributor
✅ Build Artifact 🚀MechJeb2-e9fc903.zip (built from 4a59f74) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Inside the RK problem the guidance becomes singular right at the end of it, which results in lots of CPU utilization and throwing on launch when things go wrong.
Also be more careful about entering the propagator past the event and cleanup the remaining landing analytically.
Cuts several successful tests down to <10ms from ~100ms as well, so this module should be less of a CPU hog.