Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=128351&projectId=155
Build statistics:
State: Failed
Previous State: Ok
Started at: Fri 5 Dec 2008 18:46:48 -0800
Finished at: Fri 5 Dec 2008 18:49:07 -0800
Total time: 2m 18s
Build Trigger: Schedule
Build Numb
On Fri, Dec 5, 2008 at 8:02 AM, Ingmar Kliche
<[EMAIL PROTECTED]> wrote:
> Rahul,
>
> the latest SCXML WD [1] describes a set of system variables which are
> read-only for the application. See section 5.5 [2]: "The Data Module
> maintains a protected portion of the data model containing information
Ted Dunning a écrit :
> Is there really any point in separating out the QRSolver? Is it because we
> expect multiple QR decomposition implementations that could share the same
> solving code?
>
> If that is really necessary, why not just have AbstractQRDecomposition that
> has a solve method?
>
Is there really any point in separating out the QRSolver? Is it because we
expect multiple QR decomposition implementations that could share the same
solving code?
If that is really necessary, why not just have AbstractQRDecomposition that
has a solve method?
Then the user sees this:
RealVecto
FWIW, I like the calling pattern with the static DecompositionSolver
too...
RealVector solution =
DecompositionSolver.solve(constant, new QRDecompositionImpl(matrix));
-sujit
On Fri, 2008-12-05 at 10:37 +0100, [EMAIL PROTECTED] wrote:
> - "Phil Steitz" <[EMAIL PROTECTED]> a écrit :
>
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 [EMAIL PROTECTED]
Project commons-jelly-tags-define has an issue affecting its community
integration.
This
Rahul,
the latest SCXML WD [1] describes a set of system variables which are
read-only for the application. See section 5.5 [2]: "The Data Module
maintains a protected portion of the data model containing information that
may be useful to applications"
This could be implemented in commons-scx
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 [EMAIL PROTECTED]
Project commons-jelly-tags-define-test has an issue affecting its community
integration.
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 [EMAIL PROTECTED]
Project commons-jelly-tags-ant 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 [EMAIL PROTECTED]
Project commons-jelly-tags-bsf 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 [EMAIL PROTECTED]
Project commons-jelly-tags-beanshell has an issue affecting its community
integration.
T
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 [EMAIL PROTECTED]
Project commons-jelly-test has an issue affecting its community integration.
This issue a
- "luc maisonobe" <[EMAIL PROTECTED]> a écrit :
> - "Phil Steitz" <[EMAIL PROTECTED]> a écrit :
>
>
> > Looks good. Just one last question / suggestion. In the
> > DecompositionSolver, why to we keep the argumentless decompose()
> > methods
> > and the matrix as an instance variabl
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 [EMAIL PROTECTED]
Project commons-configuration-test has an issue affecting its community
integration.
Thi
- "Phil Steitz" <[EMAIL PROTECTED]> a écrit :
> Looks good. Just one last question / suggestion. In the
> DecompositionSolver, why to we keep the argumentless decompose()
> methods
> and the matrix as an instance variable? The argumentless methods just
>
> delegate to the ones that ta
15 matches
Mail list logo