[pgrouting-dev] GSoC projects and next steps

[Razequl Islam]

Hi Steve,
Thanks for providing the links. I was about to provide that.

I wish to continue work when I get time. For next step, I would like to
check the integrity of the current implementation. So I need your guideline
to check the memory status and find possible memory leak. I also need to
improve the error and exception handling to pass any negative testing.

As for distance matrix calculation, I think pgRouting already has single
source shortest path implementation. I was wondering if we can make use of
those. May be it is possible to create another API on the core solution to
get result in the desired format.

I appreciate your review on the VRP API itself. Specially in the result
format. If you have any suggestion regarding the current API, please let me
know. I will be happy to implement those.

There are still some space for improving the core algorithm itself. I
already have some idea of improving the Tabu Search. I will gradually
implement those also. Any suggestion regarding this is also welcome.

Thanks for all your support and inspiration. I really enjoy to work in the
community.

- Razequl



On Tue, Oct 1, 2013 at 7:43 PM, Stephen Woodbridge
<woodbri at swoodbridge.com>wrote:

> Hi all,
>
> I have had a couple of requests for more information on what our Google
> Summer of Code students developed this summer. The following pages give a
> pretty good overview of their projects and how to use them.
>
> Mukul added this:
>
> https://github.com/pgRouting/**pgrouting/wiki/Details-and-**
> how-to-use-guide-<https://github.com/pgRouting/pgrouting/wiki/Details-and-how-to-use-guide->
> .
>
> it is located in git on branch "gsoc-partition" in src/partition/
> directory. Look at the test directory for examples.
>
> Razequl added this:
>
> https://github.com/pgRouting/**pgrouting/wiki/GSoc-2013-**
> Project-Information<https://github.com/pgRouting/pgrouting/wiki/GSoc-2013-Project-Information>
>
> it is located in git on branch "gsoc-vrp" in src/vrp_basic/ directory.
> Look in the test directory for examples.
>
> If you have questions, feel free to ask, Mukul and Razequl will probably
> be on the lists for a while before they have to start tackling their next
> years course work. And Daniel and I can also field questions on these.
>
> -Steve
>
>
> On 10/1/2013 9:13 AM, Dave Potts wrote:
>
>> On 30/09/13 15:23, Stephen Woodbridge wrote:
>> Hi
>>
>> Is it possible to have summary of the features that Mukul and Razequl
>> work adds to pgrouting?
>> regards
>> Dave.
>>
>>> Mukul and Razequl,
>>>
>>> Congratulations on your successful completion of GSoC!
>>> I'm sorry that Daniel and I have been very busy with our own projects
>>> of the recent past and have not been engaging more with you guys.
>>> Please make sure you complete the final code submission and
>>> requirements for Google so you will get paid for all your hard work.
>>>
>>> For next steps, I see Daniel has merged the the develop branch into
>>> the vrp branch. This will make it easier to eventually merge your code
>>> back into the develop branch for our 2.1 release in the future. I
>>> think we need to add some methods to generate the distance matrix
>>> based on a list of locations. We can write a simple Euclidean distance
>>> generator for fast demos and write a separate function that uses
>>> one-to-many Dijkstra function to generate the distance matrix.
>>>
>>> Daniel, any thoughts on this? Did you have any specific plans with this?
>>>
>>> I want to do some testing on the partition projects, and look at
>>> performance and memory usage on large graphs. Mukul is going to look
>>> at creating a trsp-partition branch to see if he can integrate the
>>> partition model into TRSP.
>>>
>>> For both these projects, I want to review at the APIs and see if I can
>>> make them consistent with our new module of reusable generic types or
>>> extent the types as needed. I also want to review them for usability
>>> changes like removing fixed table or column names, etc.
>>>
>>> From my point of view, these tasks will have to wait for some free
>>> time which will be at least 2-3 weeks out if then.
>>>
>>> I'm glad you both had a good summer with GSoC and that you will have
>>> time and interest in continuing to expand you projects and support
>>> pgRouting even if it is at a lower effort level because of class work
>>> again.
>>>
>>> Thanks again for your efforts and significant contributions.
>>>
>>> -Steve
>>> ______________________________**_________________
>>> pgrouting-dev mailing list
>>> pgrouting-dev at lists.osgeo.org
>>> http://lists.osgeo.org/**mailman/listinfo/pgrouting-dev<http://lists.osgeo.org/mailman/listinfo/pgrouting-dev>
>>>
>>
>> ______________________________**_________________
>> pgrouting-dev mailing list
>> pgrouting-dev at lists.osgeo.org
>> http://lists.osgeo.org/**mailman/listinfo/pgrouting-dev<http://lists.osgeo.org/mailman/listinfo/pgrouting-dev>
>>
>
> ______________________________**_________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/pgrouting-dev<http://lists.osgeo.org/mailman/listinfo/pgrouting-dev>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20131002/2916c233/attachment.html>