| 
      
      
      From: Roy S. <roy...@ic...> - 2006-06-22 20:05:31
      
     | 
| On Thu, 22 Jun 2006, Derek Gaston wrote: > #1 0x00002afe1d47fd5a in FE<2u, > (libMeshEnums::FEFamily)0>::inverse_map (elem=0xed52b0, > physical_point=@0xfe4db0, tolerance=0.0001, secure=true) at > fe_map.C:1364 > #2 0x00002afe1d45b565 in FEInterface::inverse_map (dim=2, > fe_t=@0xeec470, elem=0xed52b0, p=@0xfe4db0, tolerance=0.0001, > secure=true) at fe_interface.C:1186 > #3 0x00002afe1d5f7d6c in MeshFunction::operator() > (this=0x7fffffc8b2d0, p=@0xfe4db0, output=@0x7fffffc8b080) at > mesh_function.C:190 > #4 0x00002afe1d5f7c2c in MeshFunction::operator() > (this=0x7fffffc8b2d0, p=@0xfe4db0, time=0) at mesh_function.C:157 > #5 0x000000000044a155 in main (argc=5, argv=0x7fffffc8ba68) at ex10.C:461 > ############ > > The "problem" appears to be happening when mesh_function is looking > for the mapped_point. I don't know enough about this stuff to > interpret though. It looks like the failing call to inverse_map occurs after mesh_function thinks it's already found the element containing p. So, the first thing we should do is check and make sure that's true. Would you give us the x/y coordinates of p and of every node (in local order) of elem? --- Roy |