Lindsey Heagy

doi via zenodo?

6

Would folks be supportive of archiving this repository on [zenodo](http://zenodo.org)? This would provide a doi which would be helpful when citing it. Thoughts?

[Ch 6] Adding discussion on Jupyter Book

6

Jupyter-Book is a resource that we should mention! There are two potential place, it could fit in [Chapter 5](https://github.com/jupyter4edu/jupyter-edu-book/blob/master/05-jupyter-ecosystem.md#resources-for-authoring-jupyter-notebooks) or [Chapter 6](https://github.com/jupyter4edu/jupyter-edu-book/blob/master/06-getting-your-class-going-with-jupyter.md#distribution-and-collection-of-materials). The resource in Chapter 5 are more about...

Bounded Float / Int text defaults

4

When providing only one bound to either a float or int text widget, I intuitively expect the other bound to be open e.g. if I want a variable to be...

Currently, the implementations of utils for refining tree meshes are inconsistent with the default value for `finalize` `utils.refine_tree_xyz` has a default value of `False` https://github.com/simpeg/discretize/blob/c6ea5eb7f9b634a74f4b7d5a2337eb65cede93ce/discretize/utils/mesh_utils.py#L556-L565 whereas `mesh.refine_ball` has a default...

mesh.get_slice() for Tree meshes?

1

The [`__plot_slice_tree` method](https://github.com/simpeg/discretize/blob/a0cdf1d81d65f1664d1b2893f1184e91539283d4/discretize/mixins/mpl_mod.py#L2049-L2065) has a lot of logic for grabbing the correct values to plot in a plotslice. When generating plots with additional layers (e.g. [a quiver plot for MVI](http://docs.simpeg.xyz/content/examples/03-magnetics/plot_inv_mag_MVI_Sparse_TreeMesh.html#inversion-mesh))...

In `cell_levels_by_index`, if you request a cell that is outside of the mesh, we don't yet have error handling to catch this, so it just kills the kernel 

string formatting in print(mesh)

3

We should likely use `e` formatting rather than floats for printing the mesh (e.g. here we are printing a time-mesh which has cells on the order of 1e-6) 

User Guide

2

In #134, we restructured the docs and created a section that is a "User Guide" which is meant to be a collection of tutorials for getting users up and running...

mesh.reference_system --> mesh.coordinate_system?

1

"reference" is a bit generic in this context. What do folks think of renaming to `coordinate_system` (e.g. `coordinate_system in ['cartesian', 'cylindrical', 'spherical']) cc @banesullivan

To load a mesh, we should allow either a filename of a mesh that has been serialized and saved to json or just a python dict of the serialized mesh....