-
Notifications
You must be signed in to change notification settings - Fork 17
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
WIP-mobile-robot-unicycle #354
Conversation
@@ -57,7 +57,7 @@ concrete_system = concrete_problem.system; | |||
|
|||
# Definition of the grid of the state-space on which the abstraction is based (origin `x0` and state-space discretization `h`): | |||
x0 = SVector(0.0, 0.0, 0.0); | |||
h = SVector(0.2, 0.2, 0.2); | |||
h = SVector(0.1, 0.1, 0.2); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@johnaoga cc my e-mail, just revert if you want to go back to the coarser abstraction
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! No worries!
…:dionysos-dev/Dionysos.jl into WIP-mobile-robot-unicycle-antoine-girard
The failure should be fixed by JuliaIntervals/IntervalLinearAlgebra.jl#135 |
You can rebase on master to fix the documentation build so that we can see the preview |
We can see now that the controller says that it succeeded but there is not trajectory displayed at the end: |
Thank you @adrienbanse for the investigation. But, That's exactly what surprises me, since the starting point is set to be (0.5, -1.5), I would have expected to have at least 2 points in the trajectory, the starting point and the point (0.5, 0.5). @adrienbanse @blegat But from your perspective do you think its answer is okay or it maybe a bug from the algorithm? In which case I could explore that direction |
@johnaoga The initial state is in the target set so the controller directly stops |
@blegat @JulienCalbert Any idea why the example throws |
The example probably fails because of the self-loops in the automation. To mitigate this, let's try
|
@johnaoga The example is fixed, let's try to clean as much as possible the code and the presentation before merging |
thank you @adrienbanse, i will clean (if still necessary) and add comments |
I'm closing it now. But the problem I'm trying to solve here is a bit different from the one in the master. Here, I have a stage cost, a terminal cost (i.e, an explicit definition of the time horizon) and a terminal constraint sets. I'll open a new PR whenever these capacities are available in Dionysos. |
This is a new benchmark inspired by this work of Antoine Girard
Preview https://dionysos-dev.github.io/Dionysos.jl/previews/PR354