To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-dbcp has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-dbcp2 has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-email has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-chain2 has an issue affecting its community integration.
This issu
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-dbutils has an issue affecting its community integration.
This iss
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-vfs2-sandbox has an issue affecting its community integration.
Thi
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-sql has an issue affecting its community integration.
T
Dear All,
I'm currently working on accuracy improvements of the incomplete beta
function, based on the NSWC library [1]. It's quite a long work, but it
looks promising, since the implementation of the Gamma function they
propose (I had to work first on Gamma before starting the actual work on
Beta)
Le 15/08/2012 16:58, Sébastien Brisard a écrit :
> Dear All,
> I'm currently working on accuracy improvements of the incomplete beta
> function, based on the NSWC library [1]. It's quite a long work, but it
> looks promising, since the implementation of the Gamma function they
> propose (I had to w
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-exec-test has an issue affecting its community integration.
This i
Sebb, Gilles and I would like to start a discussion about the use of
assert in CM code.
This started by comments in a JIRA ticket
(https://issues.apache.org/jira/browse/MATH-845), I rewrite below a
summary:
Gilles, commenting on my code:
"assert" statements should be replaced by precondition c
On Wed, Aug 15, 2012 at 10:46:06PM +0200, matic wrote:
> Sebb, Gilles and I would like to start a discussion [...]
It was not that "Sebb" who commented on MATH-845... ;-)
> [...]
>
> @Gilles: sometimes assertion are a form of comments on steroid ->
> they will bark at you if you did not r
On Wed, Aug 15, 2012 at 04:58:39PM +0200, Sébastien Brisard wrote:
> Dear All,
> I'm currently working on accuracy improvements of the incomplete beta
> function, based on the NSWC library [1]. It's quite a long work, but it
> looks promising, since the implementation of the Gamma function they
> p
Hi.
This is in relation to that other thread (with subject "spinning
BOBYQAOptimizerTest"): http://markmail.org/message/2u6lmkuqqv6jxkgk
In fact the code doesn't run "forever", but it takes a very long time to
finish. On my machine:
---CUT---
Running org.apache.commons.math3.optimization.direct.C
On 8/15/12 4:28 PM, Gilles Sadowski wrote:
> Hi.
>
> This is in relation to that other thread (with subject "spinning
> BOBYQAOptimizerTest"): http://markmail.org/message/2u6lmkuqqv6jxkgk
>
> In fact the code doesn't run "forever", but it takes a very long time to
> finish. On my machine:
> ---CUT-
Just a quick observation: at Google the Java practices guide says
assert == "//". Assertions can be disabled, so you should never rely
on it to crash if something is seriously wrong and you should never
rely on side-effects of the assert expression.
On Wed, Aug 15, 2012 at 4:02 PM, Gilles Sadowski
Asserts can be handy to inject additional checking into execution inside
private areas of a class during unit tests but it should be assumed that
they are disabled any other time (and the unit test should do real
assertion checking redundantly)
On Wed, Aug 15, 2012 at 9:33 PM, James Ring wrote:
20 matches
Mail list logo
