[petsc-users] Strange behavior of MatLUFactorNumeric()

[Matthew Knepley]

On Tue, Aug 14, 2012 at 5:26 PM, Jinquan Zhong <jzhong at scsolutions.com>wrote:

>   Dear PETSc folks,****
>
> ** **
>
> I have a strange observation on using MatLUFactorNumeric() for dense
> matrices at different order N.  Here is the situation I have:****
>
> ** **
>
> **1.       **I use ./src/mat/tests/ex137.c as an example to direct PETSc
> in selecting superLU-dist and mumps.  The calling sequence is ****
>
> MatGetOrdering(A,…)****
>
> MatGetFactor(A,…)****
>
> MatLUFactorSymbolic(F, A,…)****
>
> *MatLUFactorNumeric*(F, A,…)****
>
> MatSolve(F,b,x)****
>
> **2.       **I have three dense matrices A at three different dimensions:
> N=75, 2028 and 21180.  ****
>
> **3.       **The calling sequence works for N=75 and 2028.  But when
> N=21180, the program hanged up when calling *MatLUFactorNumeric*(…).
> Seemed to be a segmentation fault with the following error message:****
>
> ** **
>
> [1]PETSC ERROR: --------------------- Error Message
> ------------------------------------****
>
> [1]PETSC ERROR: Signal received!
>

ALWAYS send the entire error message. How can we tell anything from a small
snippet?

Since you have [1], this was run in parallel, so you need 3rd party
packages. But you do
not seem to be checking return values. Check them to make sure those
packages are installed
correctly.

   Matt


> Does anybody have similar experience on that?****
>
> ** **
>
> Thanks a lot!****
>
> ** **
>
> Jinquan****
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120814/d7a413d7/attachment.html>