Ice elastic deformation #17
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In parallel with ice viscous flow, I work on another project on the elastic deformation of ice that I started a couple of years ago. In this PR I brought code I worked on two years ago based on MASTODON.
I now improved this code mainly by defining the trigger area directly within MOOSE and refine the mesh on the zone of interest and surroundings. Until now I had some python code where I was using the feval library to create a mesh containing a block for the trigger area, which meant one mesh per setup/simulation.
Now everything happens in the input file, with a generic mesh.
Closes #18