Damn... looks like it's a problem with the Exodus reader somehow. If I use build_cube() instead... it all works fine. Any ideas on where to start looking?
Derek On Mon, Jun 2, 2008 at 3:18 PM, Derek Gaston <[EMAIL PROTECTED]> wrote: > Trying to add a bit of adaptivity to my JFNK diffusion problem I've hit a > snag. All I did was add the normal loop around solve() and then the > following code (out of ex0): > > ###### > ErrorVector error; > KellyErrorEstimator error_estimator; > > std::cout<<"Estimating Error"<<std::endl; > error_estimator.estimate_error(system, error); > > std::cout<<"Flagging Elements"<<std::endl; > mesh_refinement.flag_elements_by_error_fraction (error); > > std::cout<<"Refining Elements"<<std::endl; > mesh_refinement.refine_and_coarsen_elements(); > > std::cout<<"Reiniting"<<std::endl; > equation_systems.reinit(); > ####### > > And then I end up with a run that looks like: > > ####### > NL step 0, |residual|_2 = 1.698356e+02 > NL step 1, |residual|_2 = 1.433372e-03 > NL step 2, |residual|_2 = 1.238651e-08 > Estimating Error > Flagging Elements > Refining Elements > Reiniting > [0] /Users/gastdr/projects/libmesh/include/geom/remote_elem.h, line 91, > compiled Jun 2 2008 at 15:01:29 > terminate called after throwing an instance of 'libMesh::LogicError' > what(): Error in libMesh internal logic > p0_19037: p4_error: interrupt SIGx: 6 > ####### > > > This is running a "devel" compiled binary in serial. In parallel I get a > different message: > > > ######## > NL step 0, |residual|_2 = 1.698356e+02 > NL step 1, |residual|_2 = 1.434226e-03 > NL step 2, |residual|_2 = 1.239177e-08 > Estimating Error > Flagging Elements > Refining Elements > Assertion `global_index_map.count(neighbor)' failed. > [2] src/partitioning/metis_partitioner.C, line 173, compiled Jun 2 2008 at > 15:02:41 > Assertion `global_index_map.count(neighbor)' failed. > ########## > > Any ideas? > > If it helps at all I'm reading an Exodus mesh from file. I've looked at > both of the lines... and can't see what's going wrong... it almost looks as > if the mesh is corrupt somehow. > > Is there something I've forgotten? > > Thanks! > Derek > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
