This sort of thing would definitely compute the inverse.
And it is definitely to be avoided.
How about you give some specifics so I can say what should be done?
On Sun, Oct 4, 2015 at 7:31 PM, go canal wrote:
> Thank you all, the solver is something like this, am
On Sun, Oct 4, 2015 at 10:32 PM, go canal wrote:
> in fact i need to support both double and complex double for either
> distributed memory based or out-of-core.
Ahh...
Well Mahout doesn't support complex anything. So this isn't going to help
you.
I will be more than interested to extend to complex double, when the solver is
ready for double data type. thanks, canal
On Monday, October 5, 2015 2:02 PM, Ted Dunning
wrote:
On Sun, Oct 4, 2015 at 10:32 PM, go canal wrote:
>
That isn't enough detail.
How do you mean to compute degrees of freedom? WHy do you need the inverse
to do this?
Where did you get this algorithm?
Is this even appropriate at large scale?
Is this a stable computation?
On Sun, Oct 4, 2015 at 11:18 PM, go canal