Skip to content
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

relinking after changing route parameters #58

Merged
merged 3 commits into from
Aug 16, 2021
Merged

Conversation

jadenvc
Copy link
Contributor

@jadenvc jadenvc commented Jun 24, 2021

No description provided.

Copy link
Owner

@k2shah k2shah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see my comments inline. also add .DS_Store to gitignore.

Can you write a unit test that checks the behavior of the relinking after the parameters have changed

wadl/solver/prac.py Outdated Show resolved Hide resolved
wadl/solver/solver.py Outdated Show resolved Hide resolved
wadl/solver/solver.py Outdated Show resolved Hide resolved
wadl/survey.py Outdated
for task, maze in self.tasks.items():
self.solver.setup(maze.graph)
try:
solTime = self.solver.solve(routeSet=maze.routeSet)
maze.solTime = solTime
# store copy of paths
self.solvers[maze] = self.solver.copy
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can just create a new Solver instance

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little unsure what you mean here. Wouldn't I lose track of the subPaths and other info then?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not if you initialize the solver object in the right spot.

self.solver = LinkSolver() is being called on the survey init so you can move that to addTask so that when a task is added a solver for that task/maze is also created in self.solvers

@k2shah k2shah merged commit 7d6e31e into k2shah:devel Aug 16, 2021
k2shah added a commit that referenced this pull request Aug 8, 2022
* Mission takeoff fix (#46)

* patch for takeoff wp write error

* Path tree (#50)

* added pathTree subclass

* working integrated pathTree

* Or export (#51)

* exporting some data for OR tools

* added at method to survey

* clean up on metaTree creation

* added timeouut for cvx

* switched smt to sat, thanks MK

* Kml (#53)

* added kml parser to Areas class

* Priority Point (#55)

* Queue sort (#56)

* simple queue sort to avoid islands

* syntax shooogar

* K2shah patch 1 (#57)

* Update python-app.yml

* hard coded values are bad

* relinking after changing route parameters (#58)

* relinking after changing route parameters

* guard against small graphs

* fixed view with new solver api

Co-authored-by: jadenvc <60724399+jadenvc@users.noreply.github.com>
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.

2 participants