Thanks for the reply. The error message shows [0]PETSC ERROR: Invalid argument [0]PETSC ERROR: Scalar value must be same on all processes, argument # 3 [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html for trouble shooting. [0]PETSC ERROR: Petsc Release Version 3.6.1, Jul, 22, 2015 [0]PETSC ERROR: ./main on a arch-linux2-cxx-debug named soumya-OptiPlex-9010 by soumya Mon Nov 30 12:30:28 2015 [0]PETSC ERROR: Configure options --with-cc=gcc --with-fc=gfortran --with-cxx=g++ --with-clanguage=cxx --download-fblaslapack --download-mpich --with-scalar-type=complex [0]PETSC ERROR: #1016 BVScaleColumn() line 380 in /home/soumya/slepc-3.6.0/src/sys/classes/bv/interface/bvops.c [0]PETSC ERROR: #1017 EPSBasicArnoldi() line 65 in /home/soumya/slepc-3.6.0/src/eps/impls/krylov/epskrylov.c [0]PETSC ERROR: #1018 EPSSolve_KrylovSchur_Default() line 201 in /home/soumya/slepc-3.6.0/src/eps/impls/krylov/krylovschur/krylovschur.c [0]PETSC ERROR: #1019 EPSSolve() line 101 in /home/soumya/slepc-3.6.0/src/eps/interface/epssolve.c [0]PETSC ERROR: --------------------- Error Message -------------------------------------------------------------- [0]PETSC ERROR: Object is in wrong state [0]PETSC ERROR: Must call EPSSolve() first: Parameter #1 [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html for trouble shooting. [0]PETSC ERROR: Petsc Release Version 3.6.1, Jul, 22, 2015 [0]PETSC ERROR: ./main on a arch-linux2-cxx-debug named soumya-OptiPlex-9010 by soumya Mon Nov 30 12:30:28 2015 [0]PETSC ERROR: Configure options --with-cc=gcc --with-fc=gfortran --with-cxx=g++ --with-clanguage=cxx --download-fblaslapack --download-mpich --with-scalar-type=complex [0]PETSC ERROR: #1020 EPSGetConverged() line 236 in /home/soumya/slepc-3.6.0/src/eps/interface/epssolve.c [0]PETSC ERROR: --------------------- Error Message -------------------------------------------------------------- [0]PETSC ERROR: Object is in wrong state [0]PETSC ERROR: Must call EPSSolve() first: Parameter #1 [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html for trouble shooting. [0]PETSC ERROR: Petsc Release Version 3.6.1, Jul, 22, 2015 [0]PETSC ERROR: ./main on a arch-linux2-cxx-debug named soumya-OptiPlex-9010 by soumya Mon Nov 30 12:30:28 2015 [0]PETSC ERROR: Configure options --with-cc=gcc --with-fc=gfortran --with-cxx=g++ --with-clanguage=cxx --download-fblaslapack --download-mpich --with-scalar-type=complex [0]PETSC ERROR: #1021 EPSGetEigenpair() line 378 in /home/soumya/slepc-3.6.0/src/eps/interface/epssolve.c [0]PETSC ERROR: --------------------- Error Message -------------------------------------------------------------- [0]PETSC ERROR: Object is in wrong state [0]PETSC ERROR: Must call EPSSolve() first: Parameter #1 [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html for trouble shooting. [0]PETSC ERROR: Petsc Release Version 3.6.1, Jul, 22, 2015 [0]PETSC ERROR: ./main on a arch-linux2-cxx-debug named soumya-OptiPlex-9010 by soumya Mon Nov 30 12:30:28 2015 [0]PETSC ERROR: Configure options --with-cc=gcc --with-fc=gfortran --with-cxx=g++ --with-clanguage=cxx --download-fblaslapack --download-mpich --with-scalar-type=complex [0]PETSC ERROR: #1022 EPSGetEigenpair() line 378 in /home/soumya/slepc-3.6.0/src/eps/interface/epssolve.c
On Mon, Nov 30, 2015 at 9:08 AM, Matthew Knepley <knep...@gmail.com> wrote: > On Mon, Nov 30, 2015 at 7:59 AM, Soumya Mukherjee < > soumyamechan...@gmail.com> wrote: > >> It is a PETSc error. And I just wanted to know if runs without an error >> in your machine. >> > This is not a PETSc error, as such. PETSc installs a signal handler so > that we can try and get more > information about signals. However, it is likely that you have a Floating > Point Exception, like a divide > by zero, in your user code. > > Thanks, > > Matt > >> On Nov 30, 2015 4:34 AM, "Jose E. Roman" <jro...@dsic.upv.es> wrote: >> > >> > I am not going to run your code. We are not a free debugging service. >> You have to debug the code yourself, and let us know only if the issue is >> related to the SLEPc library. Start adding error checking code with the >> CHKERRQ macro to all PETSc/SLEPc calls. This will catch most errors. It no >> errors are detected, then run with a debugger such as gdb or valgrind to >> determine the exact point where the program fails. >> > >> > Jose >> > >> > > > > -- > 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 >
