Le 03/02/2012 08:14, Sébastien Brisard a écrit :
Hi,
Hi Sébastien,
as rightly pointed out by Christian, the bug reported in MATH-718 is
in fact a result of the current implementation of the incomplete beta
function I(x, a, b), which is inaccurate when a and/or b are
large-ish. I think this
Hi Luc,
Hi Sébastien,
as rightly pointed out by Christian, the bug reported in MATH-718 is
in fact a result of the current implementation of the incomplete beta
function I(x, a, b), which is inaccurate when a and/or b are
large-ish. I think this is a very interesting issue, but also one
Am 03.02.2012 08:14, schrieb Sébastien Brisard:
Hi,
as rightly pointed out by Christian, the bug reported in MATH-718 is
in fact a result of the current implementation of the incomplete beta
function I(x, a, b), which is inaccurate when a and/or b are
large-ish. I think this is a very
Sorry, I miss-clicked... wanted to send that mail to your e-mail address
directly since the mailing list rejects attachments...
For what ever reason answer to sender has the same effect as anwser
to list in Thunderbird.
I'll send it again to your address :-)
Regards,
Benedikt
Am 03.02.2012
Hello,
On 01/02/2012 17:39, Simone Tripodi wrote:
Hi Gary!!! :)
I don't see any issue on adding the BST algorithms you need in
[graph], even if you have to reuse the minimum amount of codebase,
packages don't usually interact each other very much, unless some
DFS/BFS or shortest path is needed
I completely agree with Simone. I see [graph] as the right place not
only for well-known algorithms but also for state-of-the-art results,
where graphs are either support structures for computation or actual
main data structures fitting the user domain.
P.S.: with this I am not saying that
On 02/02/2012 11:57 AM, Gilles Sadowski wrote:
On Thu, Feb 02, 2012 at 12:40:14AM +, Continuum@vmbuild wrote:
The failure is unrelated to the commit, but has to do with this issue:
https://issues.apache.org/jira/browse/MATH-588
I don't know whether the test tolerance is too stringent
Hi.
The failure is unrelated to the commit, but has to do with this issue:
https://issues.apache.org/jira/browse/MATH-588
I don't know whether the test tolerance is too stringent or there really is
a bug. Could someone have a look?
Hi,
I have looked into this issue, and imo
Hi,
We have been using sanselan incubator 0.97 release which has performance issues
on .tif format. I hope that the next 1.0 release version contains fixes around
performance. When this big-bang release is scheduled?
Also I checked the trunk source code and it seems that performance
On Fri, Feb 3, 2012 at 4:10 PM, Shashank Gupta shgu...@adobe.com wrote:
Hi,
We have been using sanselan incubator 0.97 release which has performance
issues on .tif format. I hope that the next 1.0 release version contains
fixes around performance. When this big-bang release is scheduled?
There is also the project renaming/repackaging to [imaging] that needs to
be done before 1.0.
See http://permalink.gmane.org/gmane.comp.jakarta.commons.devel/126548
Gary
On Fri, Feb 3, 2012 at 10:45 AM, Damjan Jovanovic damjan@gmail.comwrote:
On Fri, Feb 3, 2012 at 4:10 PM, Shashank Gupta
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=18236projectId=97
Build statistics:
State: Failed
Previous State: Ok
Started at: Fri 3 Feb 2012 18:21:26 +
Finished at: Fri 3 Feb 2012 18:22:39 +
Total time: 1m 12s
Build Trigger: Schedule
Build
Hi,
I have been working on the exceptions in the stat.inference package and
have seen that all classes in this package follow the same scheme:
- Interface for a statistical test
- Implementation of this single interface
e.g.
ChiSquareTest
ChiSquareTestImpl
There was some effort in other
On Fri, Feb 03, 2012 at 08:33:44PM +0100, Thomas Neidhart wrote:
Hi,
I have been working on the exceptions in the stat.inference package and
have seen that all classes in this package follow the same scheme:
- Interface for a statistical test
- Implementation of this single interface
14 matches
Mail list logo
