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

Cleanup tensor mechanics deprecated tests #14007

Merged
merged 1 commit into from Sep 16, 2019

Conversation

gambka
Copy link
Contributor

@gambka gambka commented Sep 6, 2019

Cleans up deprecated tests fails associated with new addVariable API and MeshGenerators.

Refs #13909.

@gambka gambka changed the base branch from devel to next September 6, 2019 20:20
@gambka
Copy link
Contributor Author

gambka commented Sep 6, 2019

@lindsayad

@moosebuild
Copy link
Contributor

moosebuild commented Sep 6, 2019

Job Documentation on b766ab5 wanted to post the following:

View the site here

This comment will be updated on new commits.

@gambka
Copy link
Contributor Author

gambka commented Sep 12, 2019

The failing test, which is also the last test to fail the deprecated target is failing because of a fundamental difference in the behavior of the MeshExtruder mesh modifier and the MeshExtruderGenerator mesh generator. The original test is simple, containing a file mesh and the MeshExtruder modifier. Thus, the new non-deprecated version of the test should contain a FileMeshGenerator and MeshExtruderGenerator nested inside the mesh block. Making that simple change causes the test to fail with a missing bottom boundary.

The input file mesh is a 2D mesh with bottom, top, left, and right sidesets defined. The extruder defines two new sidesets back and front. In the old way that is now deprecated, the resulting mesh after the modification consists of all the sidesets (bottom, top, left, right, back and front). Using the MeshGenerator approach yields a resulting mesh containing only the back and front sidesets causing the existing BCs and Postprocessors executing on the bottom boundary to not find that sideset.

One idea I can think of to fix this is add additional MeshGenerators to the new version of the test that add back in the lost subdomains. However, I do not think the MeshExtruderGenerator should be throwing away the existing sidesets in the mesh read in from the FileMeshGenerator. Shouldn't MeshExtruderGenerator behave exactly the same as the previous MeshExtruder?

@gambka
Copy link
Contributor Author

gambka commented Sep 12, 2019

An update on the failing test. The new approach does not delete the subdomains but rather the subdomain names. If the input is updated to use the subodmainID everything works. I prefer the old behavior that maintains the subdomain names after extrusion.

Copy link
Member

@lindsayad lindsayad left a comment

Choose a reason for hiding this comment

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

@gambka Thanks a ton for this hefty PR! Nice sleuthing on the failing test. Can you open a ticket for the MeshGenerator behavior you want changed or is that already done?

@lindsayad lindsayad merged commit 8ff9758 into idaholab:next Sep 16, 2019
@permcody
Copy link
Member

Definitely a bug that names are lost. I'll take a look.

@gambka
Copy link
Contributor Author

gambka commented Sep 16, 2019

Definitely a bug that names are lost. I'll take a look.

I've made an issue here: #14037

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants