Neither of these tickets seem to refer to the current version of the tsp, are these the right ticket number or just proof that I do not known how to look at closed tickets?
If work is being done on the TSP interface, it would be nice if distance matrix version
1 Returned a defined data results, something like pgr_costResult instead of just a list
2. Return the cost between nodes
Dave.
Hi All,
If you are interested in TSP functions, I just made some big changes. Look at issues #127 and #156 for details.
I have replaced one function with plpgsql functions, updated the documentation and test. This probably need some testing and reviewing.
Neither of these tickets seem to refer to the current version of the
tsp, are these the right ticket number or just proof that I do not known
how to look at closed tickets?
If work is being done on the TSP interface, it would be nice if distance
matrix version
1 Returned a defined data results, something like pgr_costResult instead
of just a list
2. Return the cost between nodes
The new functions does this:
pgr_costResult pgr_tsp(sql text, start_id integer);
pgr_costResult pgr_tsp(sql text, start_id integer, end_id integer);
Look at the plpgsql for this, it is not trivial to manage renumbering of ids to indexes and back again. I'll take another look at the tsp matrix function.
-Steve
Dave.
Hi All,
If you are interested in TSP functions, I just made some big changes.
Look at issues #127 and #156 for details.
I have replaced one function with plpgsql functions, updated the
documentation and test. This probably need some testing and reviewing.
Neither of these tickets seem to refer to the current version of the
tsp, are these the right ticket number or just proof that I do not known
how to look at closed tickets?
If work is being done on the TSP interface, it would be nice if distance
matrix version
1 Returned a defined data results, something like pgr_costResult instead
of just a list
2. Return the cost between nodes
The new functions does this:
pgr_costResult pgr_tsp(sql text, start_id integer);
pgr_costResult pgr_tsp(sql text, start_id integer, end_id integer);
Look at the plpgsql for this, it is not trivial to manage renumbering of ids to indexes and back again. I’ll take another look at the tsp matrix function.
-Steve
Dave.
Hi All,
If you are interested in TSP functions, I just made some big changes.
Look at issues #127 and #156 for details.
I have replaced one function with plpgsql functions, updated the
documentation and test. This probably need some testing and reviewing.
@steve: it’s very easy to update. From your build directory just run
git checkout gh-pages && rm -Rf dev && cp -r build/html dev && git add dev && cp build/index.html .
git commit -m “updated to commit […]” . && git push origin gh-pages
It does a checkout of the “Github pages” branch, then replaces the current “dev” directory with the contents of the “build/html” directory and pushes the changes back Github.
When the content of the “gh-pages” branch is updated, then the docs are also the latest ones.
Just creating release documentation involves a few more manual edits.
Neither of these tickets seem to refer to the current version of the
tsp, are these the right ticket number or just proof that I do not known
how to look at closed tickets?
If work is being done on the TSP interface, it would be nice if distance
matrix version
1 Returned a defined data results, something like pgr_costResult instead
of just a list
2. Return the cost between nodes
The new functions does this:
pgr_costResult pgr_tsp(sql text, start_id integer);
pgr_costResult pgr_tsp(sql text, start_id integer, end_id integer);
Look at the plpgsql for this, it is not trivial to manage renumbering of ids to indexes and back again. I’ll take another look at the tsp matrix function.
-Steve
Dave.
Hi All,
If you are interested in TSP functions, I just made some big changes.
Look at issues #127 and #156 for details.
I have replaced one function with plpgsql functions, updated the
documentation and test. This probably need some testing and reviewing.