►
From YouTube: SimPEG meeting January 8, 2019
Description
First SimPEG meeting of 2019! Dom provides an overview of developments in the potential fields codes and Lindsey introduces some ideas for how to maintain notebook-apps for multiple courses (and instructors).
A
I
haven't
heard
from
him
and
he's
not
online,
so
we
can.
We
can
go
from
there
yeah.
So
there's
a
few
things,
I
guess
on
my
list.
So
maybe
the
first
thing
we
can
do
is
just
like
go
around.
We
can
figure
out
what
is
on
people's
lists
for
regrouping
in
the
new
year
and
then
we'll
go
from
there.
So
the
things
that
I
wanted
to
talk
about
so
Bane.
A
B
A
A
C
A
A
B
A
A
D
A
Yeah
cuz
I
had
a
brief
look
through
it
and
have
a
few
questions
and
things
like
that,
because
there's
a
lot
changing
and
so
I
think
it'd
be
helpful
to
actually
get
if
Dom
could
actually.
First
do
a
pass
and
like
point
out
the
things
that
have
changed
because
there's
a
lot
that
like
was
perhaps
style,
changes
or
name
changes
or
like
changes
in
the
order
of
things,
but
not
actually
changes
in
functionality
and
so
I
yeah
he's
able
to
do
that.
Just
a
first
pass
sort
of
explaining
what
changed
that
would
be
helpful.
A
E
A
Conversations
first
of
all,
I've
been
working
a
bit
on
trying
to
hit
on
ties
a
bit
with
respect
to
the
documentation,
so
getting
that
cleaned
up
and
a
little
easier
to
navigate
because
right
now,
it's
kind
of
all
over
the
place,
which
is
also
I,
mean
this
impact
documentation
is
also
all
over
the
place,
but
dis
critize
is
a
little
more
contained,
so
I
think
it's
a
nice
place
to
start
and
get
all
this
figured
out.
I'm
basing
a
lot
of
it
on
Leo's
work
in
bairdai
I
can
send
you
the
link
cuz.
A
C
D
A
Yeah
yeah,
so
there's
there's
a
couple
things
going
on
there:
the
numpy
doc
style,
also
just
I
mean
the
the
layout
and
the
organization
of
the
docs.
What
we
had
before
is
like
the
API
is
just
sort
of
like
strewn
throughout
the
documentation,
which
is
not
helpful,
so
I
think
that
we
need
to
separate
and
first
have
like
user
documentation
which
actually
does
not
discuss
the
API
like
in
detail.
It
first
off
just
shows
you.
This
is
how
you
set
up
each
of
the
mesh
types.
A
A
We
need
to
get
the
documentation
in
shape
and
so
like
any
time,
you're
asked
a
question:
if
you
can
try
and
make
a
habit
of
trying
to
find
it
in
the
docs
and
if
you
can't
make
an
issue
or
like
add
it
to
the
docs
in
the
long
run,
that's
gonna
save
us
a
bajillion
emails.
I
realized
in
the
short
run.
It's
it's
like
a
few
more
steps
on
you,
but
if
you
can
just
try
and
make
a
habit
of
that,
I
think
we
will
all
be
better
for
it.
A
So
what
that
means
is
that
if
Tebow
goes
in
and
changes
some
code
and
makes
a
pull
request,
if
he
first
runs
black
on
it,
black
has
been
designed
to
try
and
like
be
smart
about
how
many
lines
of
code
have
changed.
So
me
as
a
reviewer,
it's
easier,
because
the
changes
are
a
little
more
targeted,
because
that's
one
thing
that
I'm
really
struggling
with
with
the
current
potential
fields,
pull
request.
Is
it's
really
challenging
to
see
what
are
like
formatting
and
style
changes
versus
what
is
actually
a
functionality
change.
A
D
A
It's
not
like
a
plug-in.
What
you
do
is
just
before
you
submit
a
pull
request,
so
you
make
all
your
changes,
save
them
all
commit
them,
and
then
you
just
run
like
I'll,
give
a
like
I'll
update
the
make
file,
and
then
you
can
just
run
make
format
and
then
it'll
just
go
through
look
at
the
entire
code
base
format
at
all,
and
then
you
can
just
commit
that
yeah.
D
Because
I
do
admit,
like
some
of
the
on
the
potential
field,
one
that
some
of
the
some
of
the
format
change
might
be
because
of
me.
The
reason
is
that
yeah,
like
some
of
the
code
that
have
not
been
touched
in
a
while,
we're
not
like
following
paper
it,
but
in
my
sublime
now
I
have
this
package
that
I
install
a
long
time
ago.
I
said
it
was
like
when
I,
when
I,
when
I
start
using
it,
but
basically
it's
an
auto
format.
So
anytime
I
save
a
file,
it
does
the
paper
automatically
for
me.
D
A
A
D
D
F
A
D
I
might
jump
in
like
so
I'm.
Sorry,
I
don't
have
any.
We
both
for
that.
Like
so
right
after
my
read,
I
read
I
fly
too
Bonjour
I
went
straight
from
the
airport
to
fully
technique
Montreal
and
went
to
see
my
former
CEO
of
Citigroup
there
and
like
I,
guess
so,
a
few
familiar
face
and
the
few
ones
that
I
didn't
know
so
like
it
was
the
end,
or
so
they
noticed
Meza.
So
I
was
away
like
six
people.
A
A
D
D
A
Yeah
I'm
almost
wondering
if
me
is
like
potentially
a
bit
too
soon,
even
I,
don't
know,
but
let's
let's
I
agree
that
we
should
potentially
start
prioritizing
prioritizing
that
and
getting
well,
because
that'll
get
us
to
get
material
in
order
and
really
on
board
a
few
people
which
I
think
is
I
agree.
That's
important,
yeah
yeah.
B
A
A
We
had
talked
so
the
thing
that
we
were
running
into
in
the
past,
and
we
talked
about
this
when
deke
one
was
in
Vancouver.
Is
that
it's
like
there's
so
much
overlap
between
some
of
the
e/m
apps
and
so
on.
The
GPG
labs
and
there's
like
code,
that's
existing
in
both
places
and
like
trying
to
consolidate
all
of
that
so
over
the
holidays.
I
tried
to
give
some
thought
to
how
we
might
like
maintain
these,
but
then
also
have
like
we
also.
A
Originally,
with
sort
of
like
the
e/m
examples
and
e/m
apps,
we
had
separated
the
code
from
the
notebooks,
which
I
think
caused
more
headaches
than
what
it
was
worth
in
the
sense
that
we
often
ended
up
in
like
the
chicken
egg
scenario,
where
you
need
to
merge
one
before
the
other
one
works,
and
vice
versa,
which
is
annoying
and
so
I
think
that
we
should
just
have
them
all
in
the
same
place.
And
that
will
will
remove
that
headache.
A
And
then
we
can
still
distribute
the
code
separately
on
pi
PI
and
like
that,
that's
not
a
problem.
So
when
somebody
pip
installs
they're,
not
pip,
installing,
like
a
bunch
of
notebooks
as
well.
So
the
first
thing
that
I
did
is
try
to
consolidate
all
of
the
code
and
notebooks
into
that
repository
called
geo,
SCI
labs.
A
So
it's
a
combination
of
e/m,
apps
examples
and
GPG
labs.
So
the
way
that
it's
organized
right
now
is
GOC
labs,
all
lowercase,
all
one
word:
this
is
where
all
the
code
lives
and
the
code
is
organized
by
method,
so
I've
got
dcpip
m,
GP,
r,
inversion,
meg
and
seismic,
and
so
that's
just
where
all
the
code
is
and
then
there's
a
base
base
code
as
well.
Then
all
of
the
notebooks
are
organized
in
the
exact
same
way
with
the
addition
of
an
index
notebook.
A
F
A
So
I've
written
a
readme
of
like
how
I
envisioned
this
functioning
you'll
see.
There's
a
big
note
at
the
top
that
says
like
none
of
this
is
actually
real
yeah.
It's
just
a
thought
dump,
because
I
do
sometimes
find
it
helpful
to
like
walk
through
what
the
documentation
should
be
and
like
what
did
use
cases
should
be
before
writing
anything.
A
A
Then
I
would
see
this
repository
having
a
notebook,
dot,
yeah
mole
file,
and
this
would
be
a
structured
file
where
you
can
basically
specify
which
notebooks
you
want
from
GOC
labs.
If
you
want
to
rename
any
of
them
potentially
and
if
you
want
to
put
them
in
a
different
folder,
that's
sort
of
all
I
see
that
doing
and
then
running.
Something
like
make
setup
looks
at
notebooks,
Gemmell
and
downloads,
all
the
notebooks
that
you
want,
and
then
you
can
sort
of
version
control
and
maintain
that
on
your
own.
A
Then
the
other
thing
is,
you
want
to
basically
keep
things
up
to
date,
so
the
way
I
would
envision.
That
happening
is
so
say,
say:
Devon
discovers
a
bug
in
one
of
the
notebooks
or
an
explanation
that
could
be
better
and
wants
to
update
that
if
you
want
that
to
feed
back
into
the
ecosystem,
you
make
that
update
on
GOC
labs,
and
then
you
redownload
that
notebook
to
your
course
repository
and
then
push
it
from
there.
So
all
of
the
changes
should
be
happening
on
geocell
labs,
geo
side
course.
A
A
A
G
A
Yeah
and
then
I
think
like
one
of
the
one
of
the
things
that
I
would
like
to
try
and
support,
and
this
might
not
happen
in
the
first
pass,
but
it's
like
to
allow
you
to
rename
the
notebooks
so
that
if
you
want
to
call
it
TBL
for
for
your
course,
that's
fine,
but
it
won't.
It
won't
affect
anything
in
geosite
labs.
A
D
A
D
A
G
So
yeah
we
have
our
kindest
thing
and
then
we
have
a
way
for
some
professor
to
locally
make
a
custom
version
yeah
they
were
download
the
code
and
then
they
would
have
their
their
custom
list
of
apps.
From
that
point,
I
think
I
want
to
know
or
how
you
suggest
a
and
making
that
accessible
to
the
students.
Are
they
going
to
the
mall
I
think,
but
that
not
have
to
clone
the
entire
repository.
A
F
G
C
C
A
G
A
G
A
Yeah,
so
they
they
fork
it
which
makes
their
own
repository
and
then
it's
up
to
them
if
they
want
to
maintain
it
on
github
or
if
they
just
want
to
like
maintain
it
on
Dropbox
or
whatever,
okay
yeah,
we'll
give
them
all
the
tools
that
they
need
to
maintain
it
on
github,
with
the
hope
that
people
do
that
cuz,
it
I
think
causes
less
headache.
It's
no
longer
run
for
everyone,
but
yeah
it's
up
to
them.
At
that
point,.
A
Yeah
yeah,
so
I
guess,
like
my
biggest
request
at
this
point,
is
that
if
people
could
read
through
the
readme,
that's
on
the
GOC
courses
repository
and
make
issues.
If
there's
things
that
you
think
don't
make
sense
or
if
there's
questions
that
you
have
because
I
think
the
more
that
we
can
flush
out
before
a
single
line
of
code
is
written,
the
better
so
yeah.
A
So
if
this,
if
this
sounds
reasonable,
I'd
like
to,
maybe
you
like-
let's
think
on
this
for
a
few
days
and
then
if
everyone
here
thinks
that
it
makes
sense,
then
I
will
propose
this
to
jaja
and
to
decline,
because
they're
really
our
first
use
case,
and
if
they
also
think
that
this
makes
sense,
then
we
can
actually
start
writing
code.
I.
A
A
C
A
The
other
thing
that
sort
of
like
came
up
with
that
is
that
I
tried
to
sort
of
beat
some
of
the
code
from
the
apps
into
shape
a
little
bit
more,
so
I
am
actually
running
black
and
flick.
Eight
on
those
flake
eight
is
like
a
light
pep.
A
light
touch
pep,
eight
there's
a
few
things
that
I'm
gonna
I'm
gonna,
make
some
issues
and
things
like
that.
That'll
help
perhaps
reduce
complexity.
A
It's
one
of
the
nice
things
that
flake
eight
checks
for
is
complexity
of
the
code,
and
so
it's
just
going
in
looking
through
at
like
how
many
crazy
nested
loops
do
you
have
how
many
like
if-else
statements
and
how
much
code
repetition
and
all
of
that
do
you
have
for
the
GSI
labs
in
order
to
get
it
to
pass
I
set
it
to
like?
Basically,
the
code
can
almost
be
infinitely
complex
because
our
code,
some
of
it,
is
really
really
complicated,
so
I'll
create
issues
that
point
out
which
functions
are
sort
of.
A
You
know
the
worst
offenders
and,
as
we
have
time,
we
can
go
in
and
just
sort
of
refactor
a
bit
of
that
I.
Don't
think
it's
it's
super
urgent,
but
down
the
road
if,
like
Dee,
Quan
wanted
to
go
in
and
fix
something,
and
the
complexity
is
just
huge
that
makes
it
really
hard
for
him
to
go
and
do
a
one-liner
fix.
So
this
world
I
think
helped
keep
us
in
check
with
how
how
much
technical
debt
we
build
up.
So.
D
Yeah
one
of
the
complex
won't
like
that
I
can
think
of
his
poison
for
all
the
DC,
because
we
have
so
many
possible
combination
in
the
ocean
a
bit.
We
have
all
the
different
fields,
though,
like
potential
electric,
we
have
linear
and
not
scale.
We
have
primary
Toto
etc,
and
we
want
we
wanted
it
to
work
in
any
of
those
cases
in
combination.
So
we
have
tons
of,
if
statement
or
on
basic
features
on
how
to
format
the
kauravas
on
fire
yeah.
A
A
E
A
D
A
B
A
B
A
B
So
okay,
yeah
I,
can
cannot
help
all
things
like.
Is
that
a
lot
a
lot
of
things
going
on
here,
but
yeah?
There
are
a
lot
of
cool
things
happening
and
yeah
they're
really
into
the
methodology
itself
and
develop,
write
and
apply
at
the
moment
they
got
to
pilot
like
after
two
or
three
pilot
sites,
but
if
you
can
they,
if
they
can
show
like
this
actually
working
solution,
they
got
a
bit
much
bigger
plan.
They
want
to
apply
for
the
full
airborne
to
their
full
Central
Valley
area.
Nice.
A
B
Incipit,
like
the
time
limit,
is
two
years
so
Rosemary's
in
really
impress
her
to
get
it
done
right
now.
There
it's
up
yeah,
like
actually
I'm
gonna,
do
a
lot
of
technical
work
here,
yeah,
that's
developing
their
code
and
one
of
the
interesting
thing
at
a
meeting
with
the
computational
guy,
like
a
computer
guy
here
and
stand
for
it,
they
got
really
big
computing
machine
so
like
at
the
moment,
I
got
just
three
nodes
but
yeah.
If
I,
if
I
want
yeah,
they
can
set
it
up,
the
Jupiter
have
or
like
I
can
get
like.
B
Could
it
be
computing
machine
here,
yeah
they're,
just
guys,
that's
really
experience.
So
he
got
a
couple
of
Jupiter
hubs
that
he's
running
and
it's
in
this
department,
yeah
and
then
seems
like
it
was
pretty
well
about
how
things
are
working
for
the
computing,
so
yeah
I'm
like
I'm,
pretty
Ashley.
Why
I
it
from
here
so
yeah
yeah,
not
sure
what
things
are
pretty
abstract.
At
the
moment
oh
yeah
I'll
update,
as
things
are
going,
why
I
asked
a
simulation
class
because
I
in
the
main
interest
of
this
3dm
code
for
simulation,
yeah.
A
B
I
want
to
actually
get
that
3d
condominium
code
really
works,
yeah
quite
work
at
the
moment,
but
there
and
it's
like
make
it
more
efficient
and
test
with
commercial
codes
and
stuff.
That's
that's
what
I
need
to
do?
Yeah
so
I
mean
that
they're
there
creepiest
a
lot
of
synergy
with
this
impact
development.
A
That's
awesome,
sorry
well
yeah.
Well
then,
in
that
case
we
can,
we
can
try
and
we
can
prioritize
that
what
I
think
is
nice
about
in
some
ways,
starting
with
the
documentation,
because
the
thing
that's
happening
with
with
simpe
and
that
like
we
need
to
rein
in
is
the
API
and
like
our
naming
conventions
and
all
of
this
sort
of
stuff
are
starting
there
all
over
the
place.
F
A
Like
at
the
base,
it's
still
not
bad,
but
a
lot
of
the
stuff
sort
of
has
gone
off
and
done
its
own
thing
same
thing
with
like
just
in
some
cases
like
properties
and
stuff
that
are
being
attached
to
given
classes
and
like
why
we
had
that
data
misfit
bug
is
just
cuz.
There's
too
many
places
were
in
defining
standard
deviation,
and
it's
not
clear
that
they're
all
hooked
up.
We
need
to
care
some
of
those
things
apart
and
I.
A
A
B
A
F
G
Invest
is
a
way
that
better
ways
that
those
are
STS,
I
think
they're
auto-generated.
They
look
in
the
eye
files
they
find
out.
You
know
the
different
methods,
different
classes,
and
then
they
find
the
properties
and
attributes
and
they
sort
of
generate
what
all
those
things
are
and
we'd
like
to
maybe
investigate
the
way
of
making
it
a
bit
more
stable
of
your
syntax,
isn't
perfect
or
some
other
things.
I
remember
what
I
looked
at
whatever
was
auto-created
was
sort
of
confusing
was
have.