Things to do for PyRaysum

[paudetseis]

• [x] Remove un-necessary Fortran IO - deep clean up
• [x] Put all prs run-time arguments in trace headers
• [x] Optimize wiggle module
• [x] Prepare proper Jupiter notebooks
• [ ] Add tests
• [ ] Add more examples in module API
• [ ] Add more examples of usage in documentation
• [x] Make public and setup Travis and Code-coverage
• [ ] Add module to deal with arbitrary elastic tensors

[wasjabloch]

With respect to: Remove un-necessary Fortran IO - deep clean up

When fraysum builds are stable (I think they are), run_frs() could be renamed run_prs(). The only problem is, that run_frs() at the moment requires a Geometry object, that also comes handy when reshaping the fortran arrays.

Either, run_frs() could get the exact same API as run_prs() and then eventually replace it.

Or, run_prs() accepts the Geometry object, instead of baz and slow, but this would require modifying scripts that rely on the current API.