Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Using open source tools to refactor geoscience...

Using open source tools to refactor geoscience education

How do we communicate fundamental concepts in a reproducible, actionable form? How do we put numerical simulation tools in the hands of undergraduate students? These are questions we have been exploring in the development of GeoSci.xyz, a web-based resource in geophysics that leverages the geophysical software package SimPEG, Sphinx documentation, Jupyter notebooks and Binders to make examples and explanations that are reproducible and interactive.

Talk available at: https://www.youtube.com/watch?v=IW2LDsevvDk

Lindsey Heagy

July 14, 2016
Tweet

More Decks by Lindsey Heagy

Other Decks in Science

Transcript

  1. learn some things my story write a thesis?! electromagnetics archive

    go on tour (not me) geophysics textbook introductory course SimPEG me
  2. • Bugs • Reviewed by ~2 people • No discussion

    / issue board? • How did they make that figure? • Is it Current? out of date? • Limited input / feedback • Reuse is limited ◦ copy paste writing ◦ licensing restrictions • Roadmap? Is there one? • Who do I ask? are there stewards of this work? • Limited collaboration opportunities ◦ 1 or 2 (the good ones have 2) • Diff? What changed in this version? ◦ version 1 is in the used book store and is $100 cheaper. What changed? - only question order? currently
  3. learn some things our story write a thesis?! electromagnetics archive

    go on tour (not me) geophysics textbook introductory course SimPEG me
  4. • iterate in place • versioned • reproducible • tested

    • collaborative • track issues • continuous peer review • feedback • interoperable • extensible • multiple media types • ... wouldn’t it be nice capture share
  5. practices forking testing deployment licensing versioning issue tracking peer review

    pull requests tools Travis CI PyPi licenses Google App Engine git Github Sphinx Read the Docs organize refactoring
  6. practices forking testing deployment licensing versioning issue tracking peer review

    pull requests tools Travis CI PyPi licenses Google App Engine git Github Sphinx Read the Docs organize refactoring
  7. • iterate in place • versioned • reproducible • tested

    • collaborative • track issues • continuous peer review • feedback • interoperable • extensible • multiple media types • ... wouldn’t it be nice capture share
  8. (end) Except where noted, this work is licensed under a

    Creative Commons Attribution 4.0 International License