-
Notifications
You must be signed in to change notification settings - Fork 25
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
Large files are accidentally Git-tracked? #217
Comments
Look for |
You can use Possible ways to handle that:
|
The plan is to replace the infinite medium 361-group problem with an infinite medium few-group problem (probably the 7 group c5g7 data). |
The largest memory seems to come from
Now I'm less sure if the ~4 MB 361-group data is actually the culprit. |
So,,,
|
Now the However, the next step is:
Any thoughts? |
We may be able to reduce the size further when we remove the SHEM361 test problems and examples. I'll rerun the repo cleaner. Nevertheless, we still need to think about the final step of the cleaning I mentioned in the previous comment. |
Currently looking into whether we need to use the cleanup function or whether we can just delete these files. |
Can we use this to remove unwanted files accidentally tracked in the git history?
The text was updated successfully, but these errors were encountered: