Open
Conversation
Author
|
I realized that the user generated trajectory was not actually generated as a spline over the entire input points. |
Adding the updated version of the generate_sim which fixes the bugs and added comments explaining the lm_edge data structure
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
generate_sim.m was not producing correct data which rendered user data after generating custom trajectory to be used by main_simulation.
Update:
As the user defines a trajectory in the GUI, the necessary variables are stored in the data folder as 'my_simulation.mat' which produces no errors when used by main_simulation.
There might still be some bugs in the way I am handling the trajectory generation due to incorrect index association, but I haven't found anything critical as of yet.