Remove meshes not used in regression tests #11
Merged
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.
I did a scan of the meshes we are not using for regression tests in the exawind-driver or nalu-wind. It is the majority of the repo. I'd like to give people a few days to comment and weigh in on if we should be keeping any of these, or if we should have tests using these meshes that are not there.
Our mesh repo is really a bottle neck for cloning and other issues though because it is so big. I would suggest that if we want a repo of meshes for historical purposes or verification tests we fork this one prior to this commit and don't submodule it in our codes. I'd like to keep the one paired to the actual codes as slim as possible.
Using
du -shc
this PR alone drops the mesh repo size from 1GB to 519MB