Henri Drake

Posting this workaround that I came up with, which builds off of existing metadata parsers and doesn't really require anything new. The idea is to read in the fully labeled...

Note: this still only works work for rectilinear grids

Maybe just `BackgroundFieldDefinition`?

Thanks for your interest! What do you think is the best way of organizing this? Should we make a simplEarth organization and have `simplEarth.py` and `simplEarth.jl`?

E.g. one reason to separate them is that it makes the environment set-up faster, which is especially important for binder.

I've got a proof-of-concept of this working at https://github.com/hdrake/MARGO.jl/tree/documenting, following the step-by-step [Documenter.jl guide](https://juliadocs.github.io/Documenter.jl/stable/man/guide/), but haven't yet deployed it as a standalone github page.

Planning on adding the bare minimum of documentation to https://github.com/hdrake/ClimateMARGO.jl/pull/28 before releasing v0.1.0. - [x] Landing page - [x] Installation instructions - [x] A basic example - [ ] Guide...

Added some auto-generating docs in https://github.com/hdrake/ClimateMARGO.jl/pull/33 with [Literate.jl](https://github.com/fredrikekre/Literate.jl), which turns a basic `.jl` julia script fill with special comment formatting into a beautiful `.md` document with code cells and ouputs...

Need to be updated to be consistent with the published version of the model! Edit: As of v0.3.2, the documentation is once again consistent with the model.

> It is a "mock version" of Plots.jl that allows packages to define their own plots using `plot` commands, but they only work if the user installs `Plots` themselves. Will...