Features to Add: Code Execution

[caseyfleeter]

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.