Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make various MeshModifiers work with ParallelMesh #2129

Closed
jwpeterson opened this issue Feb 14, 2014 · 3 comments
Closed

Make various MeshModifiers work with ParallelMesh #2129

jwpeterson opened this issue Feb 14, 2014 · 3 comments
Labels
C: Framework P: minor A defect that does not affect the accuracy of results. T: task An enhancement to the software.

Comments

@jwpeterson
Copy link
Member

The following MeshModifiers input files don't work in parallel with ParallelMesh enabled:

tests/mesh_modifiers/add_all_side_sets/less_simple.i
tests/mesh_modifiers/add_all_side_sets/simple.i
tests/mesh_modifiers/add_extra_nodeset/extra_nodeset_test.i
tests/mesh_modifiers/add_side_sets/cylinder_normals.i
tests/mesh_modifiers/add_side_sets/cylinder_normals_fixed.i
tests/mesh_modifiers/add_side_sets/cylinder_points.i

A typical cause for the error is calling an invalid function, such as n_sides(), on a RemoteElem, which looks like this:

[./include/libmesh/remote_elem.h, line 115, compiled Jul 30 2013 at 14:06:23

These could probably be fixed up, for example, flooding has to stop if it reaches a RemoteElem:

  if (elem == NULL || (_visited[side_id](0]).find(elem) != _visited[side_id].end()) || elem->is_remote())
    return;

Then there also needs to be some kind of communication step to sync up the MooseMesh::boundary_map object that is used by a lot of the MeshModifiers.

@ghost ghost assigned jwpeterson Feb 14, 2014
@jwpeterson
Copy link
Member Author

In c1a7def:

Tests using MeshModifiers are restricted to using SerialMesh.
For more information, see #2129.

Refs #2105.
Refs #2129.

jwpeterson pushed a commit that referenced this issue Feb 14, 2014
@jwpeterson jwpeterson removed their assignment Apr 14, 2014
jwpeterson pushed a commit to jwpeterson/moose that referenced this issue May 13, 2014
jwpeterson pushed a commit to jwpeterson/moose that referenced this issue May 13, 2014
The algorithm doesn't use flood().

Refs idaholab#2129.
jwpeterson pushed a commit to jwpeterson/moose that referenced this issue May 13, 2014
The algorithm doesn't use flood().

Refs idaholab#2129.
aeslaughter pushed a commit to aeslaughter/moose that referenced this issue May 14, 2014
The algorithm doesn't use flood().

Refs idaholab#2129.
novasr pushed a commit to novasr/moose that referenced this issue May 14, 2014
The algorithm doesn't use flood().

Refs idaholab#2129.
aeslaughter pushed a commit to aeslaughter/moose that referenced this issue May 15, 2014
The algorithm doesn't use flood().

Refs idaholab#2129.
@amjokisaari
Copy link
Contributor

Bump. I just ran into the issue today with AddExtraNodeset and parallel mesh. Error message: "Unable to locate the following point within the domain, please check its coordinates: (x,y,z)=(0, 0, 0)". This point does exist, and the error does not occur running with serial mesh.

@permcody
Copy link
Member

Most of the MeshModifiers work with ParallelMesh DistributedMesh now, the rest have been properly restricted. I'm going to close this blanket issue. We'll open new specific issues as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Framework P: minor A defect that does not affect the accuracy of results. T: task An enhancement to the software.
Projects
None yet
Development

No branches or pull requests

3 participants