I use MatNorm and VecNorm on A and b before I call kspsolve, and both
of them are finite. Then I use fp_trap to catch where the nan comes
from. However, it traces down to unlikely place pthread_join. The gdb
where information is given below. Can you give me some help? Thanks.
0x7faeb6d8cbe5 i
On Wed, Dec 14, 2011 at 4:07 PM, Xiangdong Liang wrote:
> I use MatNorm and VecNorm on A and b before I call kspsolve, and both
> of them are finite. Then I use fp_trap to catch where the nan comes
> from. However, it traces down to unlikely place pthread_join. The gdb
> where information is give
On Tue, Dec 13, 2011 at 9:49 PM, Xiangdong Liang wrote:
> Hello everyone,
>
> I am solving complex Ax=b with PaStix on 20 processors successfully
> but failed on 24 processors. The relatively error indicated by
> mat_pastix_verbose becomes "nan" for 24 processors. Where could be
> wrong? Can som
Hello everyone,
I am solving complex Ax=b with PaStix on 20 processors successfully
but failed on 24 processors. The relatively error indicated by
mat_pastix_verbose becomes "nan" for 24 processors. Where could be
wrong? Can someone give me some hints on how I can debug? Thanks.
Xiangdong
