Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/mesh/mesh_base.C
Original file line number Diff line number Diff line change
Expand Up @@ -1159,7 +1159,7 @@ std::string MeshBase::get_info(const unsigned int verbosity /* = 0 */, const boo
if (verbosity > 1)
{
this->comm().min(info.bbox.min());
this->comm().min(info.bbox.max());
this->comm().max(info.bbox.max());
}
}

Expand Down
5 changes: 4 additions & 1 deletion src/mesh/poly2tri_triangulator.C
Original file line number Diff line number Diff line change
Expand Up @@ -292,9 +292,12 @@ void Poly2TriTriangulator::triangulate_current_points()
std::vector<p2t::Point> outer_boundary_points;
std::vector<std::vector<p2t::Point>> inner_hole_points(n_holes);

dof_id_type nn = _mesh.max_node_id();
libmesh_error_msg_if
(!nn, "Poly2TriTriangulator cannot triangulate an empty mesh!");

// Unless we're using an explicit segments list, we assume node ids
// are contiguous here.
dof_id_type nn = _mesh.max_node_id();
if (this->segments.empty())
libmesh_error_msg_if
(_mesh.n_nodes() != nn,
Expand Down
13 changes: 11 additions & 2 deletions src/mesh/unstructured_mesh.C
Original file line number Diff line number Diff line change
Expand Up @@ -1773,6 +1773,11 @@ void UnstructuredMesh::stitching_helper (const MeshBase * other_mesh,
bool enforce_all_nodes_match_on_boundaries,
bool skip_find_neighbors)
{
#ifdef DEBUG
// We rely on neighbor links here
MeshTools::libmesh_assert_valid_neighbors(*this);
#endif

// FIXME: make distributed mesh support efficient.
// Yes, we currently suck.
MeshSerializer serialize(*this);
Expand Down Expand Up @@ -1935,9 +1940,13 @@ void UnstructuredMesh::stitching_helper (const MeshBase * other_mesh,
{
libMesh::out << "In UnstructuredMesh::stitch_meshes:\n"
<< "This mesh has " << this_boundary_node_ids.size()
<< " nodes on boundary " << this_mesh_boundary_id << ".\n"
<< " nodes on boundary `"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is using a backtick for the opening apostrophe standard practice?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's common; not sure if I'd call it standard. I probably picked it up from some system where it was actually a necessary way of clarifying nested quotations-within-quotations, and it's overkill here, but I don't think it's hurting anything.

<< this->get_boundary_info().get_sideset_name(this_mesh_boundary_id)
<< "' (" << this_mesh_boundary_id << ").\n"
<< "Other mesh has " << other_boundary_node_ids.size()
<< " nodes on boundary " << other_mesh_boundary_id << ".\n";
<< " nodes on boundary `"
<< this->get_boundary_info().get_sideset_name(other_mesh_boundary_id)
<< "' (" << other_mesh_boundary_id << ").\n";

if (h_min_updated)
{
Expand Down