Implemented a second way of dealing with static obstacles & readme update & runningCost possibility #27
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.
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