Slide 1

Slide 1 text

Interactive Geophysics Lindsey Heagy, Rowan Cockett & GeoSci Team SciPy July 13, 2017 @lindsey_jh, @rowancockett

Slide 2

Slide 2 text

● Signal processing ● Numerical simulations ● Finite volume ● Optimization ● Regularization Geophysics? Interactive?

Slide 3

Slide 3 text

last year... Working towards all of the geophysics - but backwards Using open source tools to refactor geoscience education

Slide 4

Slide 4 text

last year... http://geosci.xyz

Slide 5

Slide 5 text

so, as we were saying...

Slide 6

Slide 6 text

Goals ● Inspire ○ See variety of applications through case histories ● Build a foundation ○ Basic principles of EM ○ Set realistic expectations of EM ● Promote development of an EM community Dr. Doug Oldenburg http://disc2017.geosci.xyz

Slide 7

Slide 7 text

Audience ● Industry professionals ○ Geologists ○ Geophysicists ○ Engineers ● Researchers ● Graduate students Dr. Doug Oldenburg, http://disc2017.geosci.xyz

Slide 8

Slide 8 text

for example Jump in here (~1.5 hrs into course) intro

Slide 9

Slide 9 text

Applications intro for example mineral exploration Water inflow into mine groundwater

Slide 10

Slide 10 text

for example http://notebooks.azure.com/library/em_apps ● DC_Cylinder_2D.ipynb

Slide 11

Slide 11 text

DC Resistivity for concept in geophysics: app(concept) Frequency Domain EM Natural Sources Time Domain EM https://notebooks.azure.com/library/em_apps

Slide 12

Slide 12 text

education stack after @jakevdp

Slide 13

Slide 13 text

education stack after @jakevdp

Slide 14

Slide 14 text

http://disc2017.geosci.xyz view from the top Doug Oldenburg Seogi Kang Taipei, Taiwan Doug Oldenburg Denver, CO

Slide 15

Slide 15 text

digging deeper http://em.geosci.xyz

Slide 16

Slide 16 text

view from the base http://simpeg.xyz

Slide 17

Slide 17 text

view from the base (looking up)

Slide 18

Slide 18 text

deploy notebooks view from the base (looking up) save instructions test instructions deploy website

Slide 19

Slide 19 text

on chaos (and deadlines) ● The course will happen ● Apps will be deployed 100 ppl (not okay) Used in real time during the course. Original developer not in the room. Batteries not included. * *

Slide 20

Slide 20 text

on chaos (and deadlines) Who are the contributors? Graduate students (not software developers) ● The course will happen ● Apps will be deployed Used in real time during the course. Original developer not in the room. Batteries not included. * * 100 ppl

Slide 21

Slide 21 text

on chaos (and deadlines) Who are the contributors? Graduate students (not software developers) ● The course will happen ● Apps will be deployed Used in real time during the course. Original developer not in the room. Batteries not included. * * 100 ppl It works? ❏ It runs on my computer what’s a branch? ❏ The code is tested it actually runs!! ❏ Someone else understands how it works ❏ There are docs in the code ❏ The code is structured (inheritance) ❏ There are docs on a website ❏ The code is styled to standard

Slide 22

Slide 22 text

on chaos (and deadlines) Who are the contributors? Graduate students (not software developers) It works? ❏ It runs on my computer what’s a branch? ❏ The code is tested it actually runs!! ❏ Someone else understands how it works ❏ There are docs in the code ❏ The code is structured (inheritance) ❏ There are docs on a website ❏ The code is styled to standard usable shareable reliable community

Slide 23

Slide 23 text

on organization Who are the contributors? Graduate students (not software developers) It works? ❏ It runs on my computer what’s a branch? ❏ The code is tested it actually runs!! ❏ Someone else understands how it works ❏ There are docs in the code ❏ The code is structured (inheritance) ❏ There are docs on a website ❏ The code is styled to standard usable shareable reliable community scope & expectations

Slide 24

Slide 24 text

on organization Who are the contributors? Graduate students (not software developers) scope & expectations It works? ❏ It runs on my computer what’s a branch? ❏ The code is tested it actually runs!! ❏ Someone else understands how it works ❏ There are docs in the code ❏ The code is structured (inheritance) ❏ There are docs on a website ❏ The code is styled to standard usable shareable reliable community

Slide 25

Slide 25 text

on reproducibility start here

Slide 26

Slide 26 text

on reproducibility start here

Slide 27

Slide 27 text

on reproducibility start here

Slide 28

Slide 28 text

on reproducibility start here on extensibility

Slide 29

Slide 29 text

on reproducibility start here on extensibility

Slide 30

Slide 30 text

on reproducibility start here on extensibility

Slide 31

Slide 31 text

on reproducibility start here on extensibility

Slide 32

Slide 32 text

counting some things Doug Oldenburg & Seogi Kang Hyderabad, India

Slide 33

Slide 33 text

@lheagy Thank you! @lindsey_jh

Slide 34

Slide 34 text

Except where noted, this work is licensed under a Creative Commons Attribution 4.0 International License