[pgrouting-users] pgr_maxFlow

[Daniel Kastl]

>
>
> Thanks for the prompt reply
> So its a workable function, but there may be bugs in it!
>

Like in every other function, too ;-)


>
> From a look at the source code, it seems that most of work is done by the
> boost library and any possible errors would be in the calling interface
> which is a mixture of C/C++
>

That's right.
Vicky also added a Boost logo on every function's documentation site, if it
makes use of Boost Library:
http://docs.pgrouting.org/latest/en/pgr_maxFlow.html#pgr-maxflow


>
> There is no support for this code, if I find any bugs you would be
> interested in any solutions, but otherwise I am on my own
>

Like with every function, there is support by wwriting to the list or
reporting a bug on Github.
There is no guaranteed time until a bug gets fix, but it depends on the
case and how easy/difficult it is.

If support or bug fixes are important for you, and if you're in the lucky
situation to be able to afford commercial support, then you are definitely
not on your own. ;-)

Best regards,
Daniel



>
>
> Dave
>
> On 25 September 2017 at 09:28, Dave Potts <mrdapotts at gmail.com> wrote:
>
>> HiSo its a workable function, but there may be bugs in it!
>>
>> From a look at the source code, it seems that most of work is done by the
>> boost library and any possible errors would be in the calling interface
>> which is a mixture of C/C++
>>
>> On 25 September 2017 at 09:21, Daniel Kastl <daniel at georepublic.de>
>> wrote:
>>
>>> Hi Dave,
>>>
>>> The function is listed as "stable proposed", and the info box on top
>>> explains a bit, what we mean with this:
>>> http://docs.pgrouting.org/latest/en/proposed.html#stable
>>>
>>> Often those functions are ready, but they are missing some extra work on
>>> tests or documentation for example.
>>> Or they have been developed during GSoC, and we hope to get some
>>> feedback from real-world use cases.
>>> Maybe by "hiding" these functions a bit, only few people find and try
>>> them. But feedback is actually what we hope for.
>>>
>>> pgr_maxFlow falls into the GSoC category, and some feedback would be
>>> great!
>>>
>>> Best regards,
>>> Daniel
>>>
>>>
>>>
>>> On Mon, Sep 25, 2017 at 4:27 PM, Dave Potts <mrdapotts at gmail.com> wrote:
>>>
>>>> Hi
>>>>
>>>> Great news on getting version 2.5 out
>>>>
>>>> Looking around the documentation I have noticed the function
>>>> pgr_maxFlow, its only listed as a proposed function.
>>>>
>>>> Just how stable is it ?  Was it ever finished ?  Does it work?
>>>>
>>>>
>>>> regards
>>>>
>>>>
>>>> Dave.
>>>>
>>>> _______________________________________________
>>>> Pgrouting-users mailing list
>>>> Pgrouting-users at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/pgrouting-users
>>>>
>>>
>>>
>>>
>>> --
>>> Georepublic UG & Georepublic Japan
>>> eMail: daniel.kastl at georepublic.de
>>> Web: https://georepublic.info
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Pgrouting-users mailing list
>>> Pgrouting-users at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/pgrouting-users
>>>
>>
>>
>
> _______________________________________________
> Pgrouting-users mailing list
> Pgrouting-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pgrouting-users
>



-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: https://georepublic.info
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20170925/6b19138f/attachment.html>