-
Notifications
You must be signed in to change notification settings - Fork 18
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
Features to Add: Code Execution #58
Comments
This was referenced Jun 1, 2020
Closed
caseyfleeter
changed the title
Features to Add re:Code Execution
Features to Add: Code Execution
Jun 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These are features we should add for the future.
Graceful failures with incorrect input files ("Fail Gracefully" when providing incorrect input file #19). Include error message and exits the code (without a segmentation fault) when the user provides an invalid input file.
Improve File I/O (For the future: File I/O #24). Writing out the data seems to be a bottleneck in the code runtime, so improvements to this could speed up simulations. Additionally, the VTK outputs could be converted from ascii to binary to produce smaller output files.
Clean up printed output (Clean Up Output of OneDSolver #26). Many lines are printed to the screen - we should decide what is necessary and what should be put into an output.txt file instead.
The text was updated successfully, but these errors were encountered: