[HIGH]: validate 2D pde examples

[mathematicalmichael]

• runs from command line, from anywhere
• generates its own files, a drop-in replacement to your thesis
• all figures checked for clarity, filenames
• runs with normal or beta (uniform = beta(1,1))
  • change formatting for beta so it replaces periods with dashes or something cleaner than dots in directory names
  • for speed, use 100 samples
• change param_ref to -3 to align with the domain. (poissonProblem class setter needs to change, as does the model, and all other references to "3"
• rethink current syntax * ... should it be dimension-specific variants with all the default options?
  • Can I sneak it into a run_with_default method that accomplishes this?
  • should I do the better thing and migrate argument parsing to the pde.py and ode.py files, with a shared set of options available for inheritance from a method in helpers.py perhaps? Then link console-scripts to their specific files? This would probably replace the entirety of the current runner.py unless an effort was made to support it (but why?).

* mud_examples -v --example pde --alt --bayes --num-trials 20 -m 20 100 250 500 -t 0.1 $@

[mathematicalmichael]

• handle reading "default" files a lot better. make them centrally loadable instead of the shenanigans that happen now with path-guessing.
• small (~900KB) or large (4MB) data files? 100 or 1000 sensors?