[pgrouting-dev] Vechile routine problem

pgRouting pgrouting-dev
1

Hi,

I seem to recall that somebody was looking at the VRP last year, did
anything happen about this?

regards

Dave.

2

On 7/21/2014 10:31 AM, dave.potts@pinan.co.uk wrote:

Hi,

I seem to recall that somebody was looking at the VRP last year, did
anything happen about this?

The current VRP solution has been added to the develop branch. It basically only generates an initial valid solution but that does not get optimized. We have a GSoC student, Mukul, that is working on writing an optimizer for it. We also have another student writing code for VRP Pickup and Delivery with Time Windows (VRPDP-TW) solver.

And I have been writing my own variant of the VRPDP-TW which will likely go into pgRouting also.

At some point in the future I plan to revisit the basic VRP and see if I can improve on that also.

So there is activity in this area, but probably nothing will get added to the development branch until this fall when I will be able to review the GSoC changes and merge them. The current GSoC efforts are all running in standalone test programs and not ready to be merged into postgresql until later.

-Steve

3

Thanks

For all goes well with the GSoC, vrp would be useful to have.

Dave.

On 7/21/2014 10:31 AM, dave.potts@pinan.co.uk wrote:

Hi,

I seem to recall that somebody was looking at the VRP last year, did
anything happen about this?

The current VRP solution has been added to the develop branch. It
basically only generates an initial valid solution but that does not get
optimized. We have a GSoC student, Mukul, that is working on writing an
optimizer for it. We also have another student writing code for VRP
Pickup and Delivery with Time Windows (VRPDP-TW) solver.

And I have been writing my own variant of the VRPDP-TW which will likely
go into pgRouting also.

At some point in the future I plan to revisit the basic VRP and see if I
can improve on that also.

So there is activity in this area, but probably nothing will get added
to the development branch until this fall when I will be able to review
the GSoC changes and merge them. The current GSoC efforts are all
running in standalone test programs and not ready to be merged into
postgresql until later.

-Steve

_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev

4

Also you might be interested in our wiki page for collecting VRP related stuff:

https://github.com/pgRouting/pgrouting/wiki/VRP-Algorithms

-Steve

On 7/21/2014 11:13 AM, dave.potts@pinan.co.uk wrote:

Thanks

For all goes well with the GSoC, vrp would be useful to have.

Dave.

On 7/21/2014 10:31 AM, dave.potts@pinan.co.uk wrote:

Hi,

I seem to recall that somebody was looking at the VRP last year, did
anything happen about this?

The current VRP solution has been added to the develop branch. It
basically only generates an initial valid solution but that does not get
optimized. We have a GSoC student, Mukul, that is working on writing an
optimizer for it. We also have another student writing code for VRP
Pickup and Delivery with Time Windows (VRPDP-TW) solver.

And I have been writing my own variant of the VRPDP-TW which will likely
go into pgRouting also.

At some point in the future I plan to revisit the basic VRP and see if I
can improve on that also.

So there is activity in this area, but probably nothing will get added
to the development branch until this fall when I will be able to review
the GSoC changes and merge them. The current GSoC efforts are all
running in standalone test programs and not ready to be merged into
postgresql until later.

-Steve

_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev

_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev