Sorry about that. I'll just print the stack here. Should I be worried about the PARMETIS error? I'll also try using 0.9.4-rc2.
It looks like the scalars are different in VecSet for the 2 processes. I will look into that problem, it looks like a problem with my code. #0 0x0000003ceec32625 in raise () from /lib64/libc.so.6 #1 0x0000003ceec33e05 in abort () from /lib64/libc.so.6 #2 0x00002ad6d8c04102 in PetscAbortErrorHandler () from /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 #3 0x00002ad6d8c0200b in PetscError () from /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 #4 0x00002ad6d8aea8eb in VecSet () from /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 #5 0x00002ad6d7a0e106 in libMesh::PetscVector<libMesh::Real>::zero (this=0x7fffac4ba128) at ./include/libmesh/petsc_vector.h:1023 #6 0x00002ad6d2114ecf in NonlinearPoissonFEM::do_my_assemble (this=0x28977a0, x=..., residual=0x7fffac4ba128, jacobian=0x0) at NonlinearPoissonFEM.cpp:139 #7 0x00002ad6d2161d6a in NonlinearPoisson::my_assemble_residual (x=..., r=..., s=...) at NonlinearPoisson.cpp:952 #8 0x00002ad6d7bc14ba in libMesh::__libmesh_petsc_snes_residual (snes=0x32f2330, x=0x26aed70, r=0x26d7ca0, ctx=0x2df4470) at src/solvers/petsc_nonlinear_solver.C:138 #9 0x00002ad6d827f726 in SNESComputeFunction () from /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 #10 0x00002ad6d82cdc66 in SNESSolve_NEWTONTR(_p_SNES*) () from /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 #11 0x00002ad6d8280942 in SNESSolve () from /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 #12 0x00002ad6d7bc3ac2 in libMesh::PetscNonlinearSolver<libMesh::Number>::solve (this=0x2df4470, jac_in=..., x_in=..., r_in=...) at src/solvers/petsc_nonlinear_solver.C:537 #13 0x00002ad6d7c4d382 in libMesh::NonlinearImplicitSystem::solve (this=0x2dfcdb0) at src/systems/nonlinear_implicit_system.C:178 #14 0x00002ad6d216c083 in NonlinearPoisson::execute_solver (this=0x28977a0) at NonlinearPoisson.cpp:798 #15 0x00002ad6d214ee88 in NonlinearPoisson::do_solve (this=0x28977a0) at NonlinearPoisson.cpp:676 #16 0x00002ad6d27beb23 in Simulation::solve (this=0x28977a0) at Simulation.cpp:734 #17 0x00002ad6d26d5ff9 in Nemo::run_simulations (this=0x66ce80) at Nemo.cpp:1143 #18 0x000000000040cf99 in main (argc=3, argv=0x7fffac4bbd08) at main.cpp:443 On Tue, Feb 17, 2015 at 3:20 PM, John Peterson <[email protected]> wrote: > > > On Tue, Feb 17, 2015 at 11:34 AM, Harshad Sahasrabudhe < > [email protected]> wrote: > >> Hi, >> >> I'm trying to run my code in parallel using parmesh and it crashes. The >> code runs properly when run in serial. While partitioning the mesh I get >> the following error from PARMETIS: >> >> PARMETIS ERROR: The sum of tpwgts for constraint #0 is not 1.0 >> >> Does this have anything to do with the crash? I have attached the stack >> trace. I have compiled LibMesh 0.9.3 using Intel compilers with Intel MPI >> 5, PETSc 3.4.3 and SLEPc 3.4.3. >> > > Your stack trace attachment was eaten by the mailing list filter. Please > either share it as a google doc link or send it to me directly. > > Libmesh 0.9.3 was tagged almost exactly 1 year ago... a lot has changed > since then. Would you mind also trying your application with the latest > 0.9.4 release candidate ( > https://github.com/libMesh/libmesh/releases/tag/v0.9.4-rc2) as well? > That may simply "fix" the problem. > > -- > John > ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
