-
Notifications
You must be signed in to change notification settings - Fork 9
Added disturbance forces and torques #46
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
Open
kurtgeebelen
wants to merge
28
commits into
ghorn:master
Choose a base branch
from
kurtgeebelen:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
If you want to use disturbance forces and torques, set the configuration parameter 'useDisturbanceForcesAndTorques' to true. They are added to the aero forces and torques. If you wish to do MHE with these disturbances, it is not possible, because the IMU_acceleration measurement function depends on these forces (and you cannot depend on both states and controls). Therefore, I added 3 dummy control inputs u_a1, u_a2 and u_a3. Enable them by setting 'useDummyAccelerationControls' to true. Now you can do a trick: In stead of doing: minize norm( h(x,u)-y ) which is not allowed, you can do in stead minimuze norm( u_a ) subject to h(x,u) - u_a == 0 which is allowed.
And also the dummy control inputs
They are added as states, with derivative set to 0, such that they act as a parameter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I added disturbance forces and torques ( if 'useDisturbanceForcesAndTorques' is True and present in conf). They are added as control inputs and added to the aero forces and torques.
I also added 3 'dummy' control inputs (if 'useDummyAccelerationControls' is True and present in conf). They can be used if you want to do MHE using the disturbance forces, because with these disturbance forces, IMU_acceleration now depends on both states and controls. Using extra control inputs, and setting these equal to IMU_acceleration via a constraint, is a trick to have measurement functions depending on both x and u.