verbosity control and mesh generation imprv.

[krober10nd]

• all modules have verbosity controls (0 for silent, 1 for start and end, 2 for all the details). 1 is default.
• the mesh generation module is getting some ports from SeismicMesh developments namely faster unique edge calculations. No parallel yet (not necessary).

[codecov-io]

Codecov Report

Merging #15 (b9483b0) into master (c9322ab) will increase coverage by 1.75%.
The diff coverage is 81.93%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
+ Coverage   85.40%   87.15%   +1.75%     
==========================================
  Files           9        9              
  Lines         877      942      +65     
==========================================
+ Hits          749      821      +72     
+ Misses        128      121       -7     

Impacted Files	Coverage Δ
oceanmesh/edgefx.py	53.84% <42.85%> (-46.16%)	⬇️
oceanmesh/grid.py	83.06% <72.41%> (-4.44%)	⬇️
oceanmesh/clean.py	96.37% <88.23%> (+7.58%)	⬆️
oceanmesh/geodata.py	91.69% <92.10%> (+4.38%)	⬆️
oceanmesh/mesh_generator.py	89.02% <96.55%> (+1.84%)	⬆️
oceanmesh/__init__.py	100.00% <100.00%> (ø)
oceanmesh/signed_distance_function.py	100.00% <100.00%> (+25.80%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c9322ab...b9483b0. Read the comment docs.

[krober10nd]

okay @WPringle this is ready to be merged. any input?

[krober10nd]

I would like to keep the generator as simple as possible and instead make the mesh size function and domain classes take on the complexity for example to support multiscale mesh generation in a more general way. As you can see the mesh generator just takes a domain and an edge_length function. The both can be simple functions that take points and returns a size and signed distance etc.

[WPringle]

I like that change to inputting max allowable spacing of shoreline and edgefx in meters rather than degrees. At present we do just the divide by 111e3 to convert to degrees for the shoreline. I suppose that be fine. Another way we could use the haversine formula inside the interpm routine to make it more precise.

[WPringle]

The other comment I have is on the make traversable. Let's change dj_cutoff to something more useful like minimum_allowable_mesh_segment_area or just min_disconnected_area

[WPringle]

Similarly hmin could change that to min_edge_length

[krober10nd]

I think putting Haversine function is a good idea and agree about the name changes in the API.

[krober10nd]

Alright, I changed h0 to min_edge_length in the mesh generator API and dj_cutoff -> min_disconnected_area

I also added a test for the README code. Eventually, we should move over to tox to handle testing on different versions of Python and to separate out testing deps with the main installation deps as the average user won't be testing.

I think the Haversine thing should come in later versions.

[krober10nd]

#16