Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kill when we have degenerate thruster setup #252

Open
DSsoto opened this issue May 15, 2017 · 0 comments
Open

Kill when we have degenerate thruster setup #252

DSsoto opened this issue May 15, 2017 · 0 comments
Assignees

Comments

@DSsoto
Copy link
Member

DSsoto commented May 15, 2017

TLDR: We should kill the sub when losing second thruster leaves us with a singular B-matrix.

Right now we only kill if we lose a third thruster, only giving warnings when the first two are lost. However this is not always safe as there are multiple ways of losing a second thruster that leave us without full state control.

This should be easy to check: (code should live in thruster mapper)

  • Compose the B-matrix out of the thrusters left
  • Check the determinant of the matrix is non-zero
  • If it is zero, raise the thruster-kill alarm

This will help us avoid problems like what happened on May 14 which waste a lot of time and are potentially dangerous for the sub.

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

No branches or pull requests

2 participants