Well, it got past that other problem, but now apparently it is looking for a non-existent point...
******** Serious Problem. Could not find an Element in the Mesh ******** that contains the Point (x,y,z)=( 6.33227, 0, 0) [0] src/utils/point_locator_tree.C, line 208, compiled May 27 2010 at 17:32:10 terminate called after throwing an instance of 'libMesh::LogicError' what(): Error in libMesh internal logic and traceback Stack frames: 10 0: print_trace(std::ostream&) 1: PointLocatorTree::operator()(Point const&) const 2: PeriodicBoundaries::neighbor(unsigned int, MeshBase const&, Elem const*, unsigned int) 3: FEBase::compute_periodic_constraints(DofConstraints&, DofMap&, PeriodicBoundaries&, MeshBase const&, unsigned int, Elem const*) 4: FEInterface::compute_periodic_constraints(DofConstraints&, DofMap&, PeriodicBoundaries&, MeshBase const&, unsigned int, Elem const*) 5: (anonymous namespace)::ComputeConstraints::operator()(StoredRange<MeshBase::const_element_iterator, Elem const*> const&) const 6: void Threads::parallel_for<StoredRange<MeshBase::const_element_iterator, Elem const*>, (anonymous namespace)::ComputeConstraints>(StoredRange<MeshBase::const_element_iterator, Elem const*> const&, (anonymous namespace)::ComputeConstraints const&) 7: DofMap::create_dof_constraints(MeshBase const&) 8: System::init_data() 9: ExplicitSystem::init_data() I'm creating the mesh with MeshTools::Generation::build_square (mesh, x_elem, y_elem, xmin, xmax, ymin, ymax, QUAD4); and then my translation vectors are: boundary_translation2(xmax-xmin,0.,0.); boundary_translation1(0.,ymax-ymin,0.); where (currently) xmax = ymax = 6.283184 and xmin=ymin = 0. Am I defining the translation boundaries incorrectly? Thanks! Andrea On Thu, May 27, 2010 at 5:24 PM, Roy Stogner <royst...@ices.utexas.edu> wrote: > > On Thu, 27 May 2010, Andrea Hawkins wrote: > >> I'm wondering though, does the inflow_ID and ouflow_ID correspond to >> the same numbers as the edges of an element are numbered? i.e. 0 for >> the bottom, 1 for the right side, 2 for the top, and 3 for the left >> side? > > The PeriodicBoundary ids are the same as the BoundaryInfo IDs. If you > generated your domain with build_square, build_cube, etc. then I > believe our convention is to use the same ordering as for a single > element's sides. > >> I've tried the code above and get the following error: >> >> Assertion `!_b' failed. >> [0] >> /h1/ahawkins/LIBRARIES/LIBMESH/libmesh-r3801/include/parallel/threads.h, >> line 64, compiled Apr 29 2010 at 12:08:34 >> terminate called after throwing an instance of 'libMesh::LogicError' >> what(): Error in libMesh internal logic >> >> where the traceback is: >> Stack frames: 10 >> 0: print_trace(std::ostream&) >> 1: _ZN7Threads11BoolAcquireC9ERb >> 2: Threads::BoolAcquire::BoolAcquire(bool&) >> 3: void >> Threads::parallel_reduce<StoredRange<MeshBase::const_node_iterator, >> Node const*>, (anonymous >> namespace)::FindBBox>(StoredRange<MeshBase::const_node_iterator, Node >> const*> const&, (anonymous namespace)::FindBBox&) >> 4: MeshTools::bounding_box(MeshBase const&) >> 5: PointLocatorTree::init(Trees::BuildType) >> 6: _ZN16PointLocatorTreeC9ERK8MeshBasePK16PointLocatorBase >> 7: PointLocatorTree::PointLocatorTree(MeshBase const&, PointLocatorBase >> const*) >> 8: PointLocatorBase::build(MeshEnums::PointLocatorType, MeshBase >> const&, PointLocatorBase const*) >> 9: MeshBase::point_locator() const > > Damn; this is a bug whose correct fix I worked out but never found > time to implement or test. Would you mind testing it for me? The fix > should be in the SVN head (r3822) now. > --- > Roy > ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
