Skip to content

Conversation

@MariusWiggert
Copy link

Besides the reach avoid formulation (which is more general), there's another way of dealing with obstacles.
It is quite simple: setting the Hamiltonian to zero inside the obstacle grid points. For comparison of the results of the different methods to account for constraints, I implemented it and thought I'll contribute it back as it might be useful for others.

Plus: updated the readme

@MariusWiggert MariusWiggert changed the title Implemented a second way of dealing with static obstacles & readme update Implemented a second way of dealing with static obstacles & readme update & runningCost possibility Jul 16, 2021
@MariusWiggert
Copy link
Author

Added the functionality of having a running cost function in the dynSys which is then visible to a) optCtrl and optDistr and b) to genericHam, which use it to a) subset the respective u, d and b) add the running cost term.

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

Successfully merging this pull request may close these issues.

1 participant