Re-implementing the mesh input to enable multiple file types #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The netcdf-ugrid file type offers a benefit in terms of file size and parallel I/O capability via parallel netcdf, but should not replace the existing .obj mesh files which are useful for their flexibility, particularly where mesh size is not an issue (for non-geographical assets for example).
This PR enables mesh objects to be read from mutiple file sources. This is achieved by moving the mesh file implementation into the mesh module, and altering the interface provided by the wavefront fs module. This interface is copied by the new ugrid fs module and both are used by the new mesh-file implementation.
Unit tests have been added.