ModEM requires rebuilding to handle different input/output file types

[MiCurry]

Currently, ModEM requires rebuilding to handle different Input and output file types. Ideally, ModEM should be able to perform IO to all supported file types without needing to rebuild.

Here is a list of supported and unsupported file types for ModEM:

• Supported IO Formats
  • ASCII
    • WSINV3DMT
    • Winglink/Mackie Format
  • Binary Format
  • HDF5
• Not Supported
  • NetCDF

We should update ModEM so that it can handle all IO formats and allow the user to specifically select the file types for both input and output. The user should be allow to mix and match, so they could input with ASCII and output with HDF5/NetCDF/Binary.

We would have to modify the code to first build interfaces for all formats, and have perhaps make a ModEM_IO abstraction module that handles calling specific interfaces depending on the IO selection.

If the user builds ModEM with HDF5 or NetCDF, they should have the ability to specify those file types. If the user does not build with HDF5 or NetCDF, and tries to write with such a file type, an error should be produced.

We would also need to add a way for the user to specify their desired input/output filetypes, this could be done in forward or inversion control files, or perhaps we could add Fortran Namelist to also handle this.

Regardless, this issue can serve as a place to discuss possible implementations or prototypes.