<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Steve, t<span id="result_box" class="short_text" lang="en"><span
class="hps alt-edited">hank you</span> <span class="hps">for
your help</span></span>.<br>
<br>
I've created issues with mentioned bugs on GitHub.<br>
<br>
W dniu 2012-03-05 19:52, Stephen Woodbridge pisze:
<blockquote cite="mid:4F550B83.9090104@swoodbridge.com" type="cite">On
3/5/2012 1:43 PM, Dariusz Górski wrote:
<br>
<blockquote type="cite">If I do not include the start node in the
list of stops, I'll get an error:
<br>
" The connection to the server was lost. Attempting reset:
Failed."
<br>
</blockquote>
<br>
Ok, that is not good. Please write a bug ticket for this and a
separate bug for the fact that it does not create a loop.
<br>
<br>
In the short term you can work around the loop problem knowing
that you do not have a closed loop and issuing a separate request
from the last point to the start point, but this should not be
required in my opinion.
<br>
<br>
</blockquote>
<div dir="ltr" style="zoom:1"><span id="result_box"
class="short_text" lang="en"><span class="hps">Looking at the</span>
<span class="hps">results of TSP function,</span></span><span
id="result_box" class="short_text" lang="en"><span class="hps">
I do not think that order of visited points </span></span><span
id="result_box" class="short_text" lang="en"><span class="hps
alt-edited">is correct</span> <span class="hps">to make</span>
<span class="hps">of them</span> <span class="hps">a closed
loop. In my opinion TSP solver </span></span>does not assume
that the source_id for the start is also the end<span
id="result_box" class="short_text" lang="en"><span class="hps"></span></span>.<br>
<span id="result_box" class="" lang="en"><span class="hps">I hope
that</span> <span class="hps">someone will be</span> <span
class="hps">able to solve this</span> <span class="hps">problem.<br>
<br>
Best regards,<br>
Darek<br>
</span></span></div>
<blockquote cite="mid:4F550B83.9090104@swoodbridge.com" type="cite">
<blockquote type="cite">I'm using Ubuntu Server 11.10, PostgreSQL
9.1.3, Postgis 1.5.3,
<br>
pgrouting 1.05 with patch
<br>
<a class="moz-txt-link-freetext" href="https://github.com/sanak/pgrouting/commit/6ec1672f79f7070c60fb6095342d7d0b55cf2659">https://github.com/sanak/pgrouting/commit/6ec1672f79f7070c60fb6095342d7d0b55cf2659</a>
<br>
<br>
<br>
Inside TSP warappers I've changed "tsp_test" to " ' ||
<br>
quote_ident(geom_table) || ' " in order to get them to work.
<br>
</blockquote>
<br>
Please write this up as another bug. Hopefully if we have tickets
on this stuff we can clean up a lot of these issues in the next
release when ever that happens.
<br>
<br>
Thanks,
<br>
-Steve
<br>
<br>
<blockquote type="cite">Darek
<br>
<br>
W dniu 2012-03-05 19:03, Stephen Woodbridge pisze:
<br>
<blockquote type="cite">What happens if you do not include the
the start node in the list of
<br>
stops? For example:
<br>
<br>
SELECT * FROM tsp_dijkstra('ways','552,169,784,1567,314',272);
<br>
<br>
I have not used this function in pgRouting so I don't know
what to
<br>
expect.
<br>
<br>
-Steve
<br>
<br>
On 3/5/2012 12:56 PM, Dariusz Górski wrote:
<br>
<blockquote type="cite">W dniu 2012-03-05 15:15, Stephen
Woodbridge pisze:
<br>
<blockquote type="cite">On 3/5/2012 6:00 AM, Dariusz Gorski
wrote:
<br>
<blockquote type="cite">Hello List,
<br>
<br>
First of all I'd like to say thanks to the pgrouting
Team for this
<br>
great project.
<br>
<br>
I've build pgrouting with patch:
<br>
<a class="moz-txt-link-freetext" href="https://github.com/pgRouting/pgrouting/pull/49">https://github.com/pgRouting/pgrouting/pull/49</a>
<br>
<br>
It works fine, but only in case when source and
destination are
<br>
different points.
<br>
<br>
My aim is to solve TSP problem, when start and end point
are the same.
<br>
<br>
Any help would be appreciated.
<br>
</blockquote>
<br>
The patch was for specifying a separate end point. But
according to
<br>
the thread on the link above, just leave off the last
parameter and it
<br>
should work as before. where you give it a list of ids
that you want
<br>
it to visit and the source_id for the start which is also
the end.
<br>
<br>
-Steve
<br>
_______________________________________________
<br>
Pgrouting-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:Pgrouting-users@lists.osgeo.org"><mailto:Pgrouting-users@lists.osgeo.org></a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a>
<br>
<br>
</blockquote>
Steve, thanks for your reply.
<br>
I've tried it before, but even when I use standard TSP
functions,
<br>
e.g. SELECT * FROM
tsp_dijkstra('ways','552,272,169,784,1567,314',272);
<br>
I don't get the loops (attached image).
<br>
This is the reason why I thought that in TSP functions only
starting
<br>
point is fixed, but endpoint calculates TSP solver.
<br>
According to your hint, where source = destination, I would
expect to
<br>
receive loop.
<br>
In my case it does not work in this way.
<br>
What am I doing wrong or what am I missing?
<br>
<br>
Darek
<br>
<br>
<br>
_______________________________________________
<br>
Pgrouting-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
Pgrouting-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a>
<br>
<br>
</blockquote>
<br>
_______________________________________________
<br>
Pgrouting-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
Pgrouting-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>