►
From YouTube: SimPEG Meeting April 16
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Kevin
give
us
an
overview
with
a
song
of
his
present
he's,
given
a
presentation
at
be
sequestered
next
week,
I
think
it's
just
this
Thursday
okay
yeah,
but
got
a
message
and
he
was
saying
he's
not
feeling
so
great
today,
so
yeah,
hopefully,
he'll
recover
quickly
and
I
think
he'll
send
through
since
life
at
some
point,
but
yeah.
A
So
do
we
want
to
start?
Does
anybody
have
quick
dates,
things
you
wanna
things
you
want
to
tell
us
about
what
you've
been
up
to
you.
A
B
B
If
we
need
to
I
mostly
just
wanted
to
show
what
I've
done
so
far
in
the
Google
Doc
and
really
just
gauged
interest
in
terms
of
who
wanted
to
be
involved,
so
I've
actually
started
making
examples
or
sort
of
tutorials,
starting
with
models,
mapping
and
then
I
want
to
start
making
them
for
for
modeling
and
then
showing
off
all
the
different
versions.
Functionality.
So
yeah
I've
got
some
stuff
started
on
that
excellent.
A
C
D
E
Users
playing
around
with
it
and
he
was
looking
if
there's
any
sources
that
people
have
tried
it
before
I
can
remember.
He
was
taking
the
observed
minus
the
predicted
and
then
mapping
his
weights.
That
way
from
the
difference.
That's
wrong.
Yeah,
that's
gonna,
have
a
reward
thing:
yeah,
yeah
yeah!
After
a
future
yeah.
E
A
D
D
A
A
D
A
That
is,
brings
up
like
a
bit
of
an
order
of
operations
question,
and
this
also
maybe
ties
into
the
docks.
So
maybe
this
is
worth
going
into
now
order.
A
There's
pull
requests
so
I
can't
screen
because
I
went
through
and
like
refactor
the
discretized
docks
and
I've
showed
you
all
this
before,
but
now
it's
actually
passing
and
I
think
basically
ready
to
go.
It
shouldn't
cause
too
much
of
conflicts,
I,
don't
think
with
your
PR,
but
there
will
be
a
bit
to
sort
through
and
I
can
I'm
happy
to
do
that,
and
we
can
take
a
look
at
this
afterwards
in
terms
of
order
of
operations
dawn,
but
I
think
I
can
give
a
bit
of
an
overview.
Can
you
all
see
done?
D
A
A
And
Devon,
this
I
think
is
very
much
along
the
lines
of
what
we
could
do
for
our
simpe
docks
as
well.
Yeah.
A
A
So
just
reading
young
things
based
on
like
what
are
you
using
for
getting
started?
What's
a
bit
of
a
user
guide?
Well
and
so
I
have
an
issue
going
of
like
other
things
that
we
should
actually
in
the
user
guide.
Good
right
now,
it's
pretty
light,
but
there's
all
the
questions
we
get
on
like
building
operators.
What
does
the
curl
do?
What
is
the
face?
Divergence
view
all
those
sorts
of
things
and
to
actually
think
that,
basically,
for
like
every
operator,
we
should
think
about
having
a
quick
user
guide.
A
A
A
Actually,
the
API
is
built
I
kind
of
quite
like
is.
We
have
just
like
a
hockey
level,
one
payment
overview,
basically
everything
that's
there
and
then
you
can
go
in
and
you
can
click
on
the
tensor
mesh,
for
example,
and
then
actually
the
docks
that
are
specific
to
that
as
your
mesh
and
all
of
its
properties
and
methods,
and
all
that.
A
The
the
other
thing
that
I
changed
and
we
don't
have
to
go
into
too
much
detail
on
this,
but
I
do
want
to
point
it
out
is
the
testing
so
before
it
was
actually
kind
of
unclear
which
version
of
Python
we
were
testing
on.
We
because
we
were
installing
anaconda.
It
was
always
grabbing
the
latest.
You
know
we
thought
we
were
testing
on
Python
3.6.
A
It
would
grab
the
latest
Python
3
from
anaconda,
which
is
actually
3.7
and
so
I've
reflected
some
stuff
just
following
what
Leo
does
for
their
day,
which
is
one
of
the
fatty
and
oh
wow,
and
basically
split
up
or
Travis
file
a
bit
more.
So
let
me
show
you.
This
is
gonna,
be
confusing,
so
I'm,
just
gonna
pull
up
the.
D
A
So
the
way
that
this
works
is
basically
each
bullet
point
here
provides
the
description
for
one
of
the
tests.
What
are
the
test?
Suites?
That's
triggered
on
Travis,
so
if
I
actually
showing
you
what
Travis
looks
like
so
here
for
this
documentation
clean
up
or
request,
we
can
see
on
the
latest
one.
There
is
one
named
Python
2.7
base.
A
This
is
exactly
like
this.
Is
that
so
it's
running,
we
type
nine
point,
seven
and
it's
gonna
press
the
base
directory
and
so
I
know.
This
is
a
bit
more
verbose
and
our
previous
Travis
file,
but
I
think
it's
a
bit
more
clear
is
like
here
were
explicit,
about
which
version
of
Python
were
testing,
which
were
it's
running
and
all
of
that
so
hopefully
that's
a
bit
cleaner.
Your
us
to
maintain
down
the
line
and.
A
Can
specify
specific
package
versions
so
here,
for
example,
we
do
the
deploy
to
PI
P
on
from
the
tree
mesh
testing
right
and
so
here
I
install
an
extra
package
on
Wanda
I
install
twine.
It
is.
A
A
The
only
other
thing
and
they'll
be
a
change
that
needs
to
propagate
through
on
the
peg.
With
this
is
that
I
reorganised.
I
lately
did
some
reorganization
of
where
the
base
classes
live.
So
there's
now
a
base
directory
in
discretize.
So
here,
if
we
look
at
the
code,
so
this
is
all
the
code.
There
is
now
actually
a
base
directory
where
we
have
the
base
mesh
and
the
base
tensor
mesh.
This
shouldn't
change,
basically
anything
user-facing.
A
B
Think
it's
definitely
like
a
massive
improvement
over
what
we
had
before
so
I.
Don't
I,
don't
mind
like
taking
a
look
and
giving
any
comments
and
we
can
bring
it
in
with
maybe
making
adaptations
in
the
future,
but
I
mean
it
looks
significantly
better
than
what
we
had
before
pretty
happy.
But
I
may
have
some
stuff
that
we
could
do
to
to
further
improve
it.
If
people
wanted
so
I'd
be
willing
to
look
at
it
this
week
and
we
could
we
could
get
in
it.
That'd.
A
Be
awesome,
demin
and
I've
linked
like
in
the
issue
a
couple
issues
that
sort
of
say:
here's
some
things
that
we
need
to
do
so
feel
free
to
add
to
those
or
if
you
want
to
flush
them
out
further,
like
that'd,
be
great
yeah.
B
You
go
to
slack,
I
mean
are
going
to
the
the
meeting
notes,
there's
the
link
to
the
Google
dot
right.
There.
D
B
So
yeah
this
was
basically
kind
of
looking
at
the
highest
level
organization
of
cippec.
It
was
sort
of
inspired
by
the
discretize
stuff
as
well
just
being
someone
who's,
not
maybe
as
experienced
as
a
user
as
some
of
the
other
people.
I
guess
I
noticed
that
we
wanted
to
be
easy
for
people
to
get
started
and
so
yeah
I
kind
of
came
in
there
with
fresh
eyes
and
thought.
Maybe
we
can
make
some
improvements
to
the
website,
and
this
is
really
related
to
things
in
the
issues
6:59
on
the
repository.
B
A
B
D
D
B
One
thing
we
have
is
that
the
the
API
section
we
auto
generate
the
API,
but
it
doesn't
really
have
a
consistent
organization,
so
sometimes
there's
theory
in
the
doc
string,
and
sometimes
it's
yeah.
It's
it's
in
a
particular
geophysical
method.
Sometimes
yeah,
it's
it's
auto-generated,
so
that
that
isn't
really
consistent
in
here.
So
we
have
some
questions.
B
Do
we
want
to
maybe
for
like
the
e/m
problem,
do
we
want
to
in
the
doc
string,
provide
some
kind
of
theory
on
how
it's
solved
that
makes
pages
longer,
or
do
we
want
to
have
a
separate
area
to
put
theory
and
make
use
of
hyperlinks?
So
maybe
you
know
the
API
goes
in
its
own
section
and
in
the
doc
string.
We
could
actually
link
that
to
a
theory
section
in
the
website
if
you
want
to
actually
know
how
that
was
being
done,
so
we
can
make
use
of
a
lot
of
these
little.
B
These
tools
with
the
website,
design,
yeah
I,
think
we're
pretty
happy
with
the
API
style,
how
we
auto-generate
that
I
think
what
Lindsay
showed
in
the
discretize,
having
sort
of
that
highest
level
and
then
being
able
to
click
on
that
and
sort
of
see
everything
for
particular
I,
guess
class.
That's
pretty
sweet
and
I'm
pretty
happy
with
that.
I
think
I
think
we
use
it
and
then
examples.
B
So
this
really
is
our
biggest
teaching
tool
and
right
now
we
have
an
example
section
and
we
have
all
these
thumbnails
and
all
this
great
stuff,
but
it's
not
really
organized
in
us
of
a
fashion
where
you
go
through
tutorials
and
really
learn
how
to
become
an
expert's
impact
user.
It's
sort
of
looking
at
you
find
a
particular
problem,
and
you
can
use
that
that
example,
but
if
you
want
to
kind
of
generally.
F
B
How
to
simple
works?
I,
don't
know
if
they're
the
most
successful,
so
I've
kind
of
been
working
on
some
of
those
mostly
started
with
making
models
and
mappings
and
showing
that
yeah.
So
I
think
we
want
to
start
with
a
structure.
That's
pretty
similar
to
what
we
have
for
discretize
I,
don't
we'll
kind
of
decide
what
we
think
is
the
best,
but
I
do
like
the
getting
started
section.
I
found
that
to
be
pretty
good
too.
You
know
getting
things
set
up
on
my
computer
I
thought
that
was
really
quite
good
and
then
having
examples.
B
So
I
have
sort
of
examples
for
førde
simulations.
It's
one
thing:
people
really
want
to
use.
Mpeg-4
is
to
predict
data
for
a
particular
scenario
and
then
try
and
show
off
our
functionality
for
inversion
and
then
have
the
API
documentation
be
separate
and
then
have
a
section
for
theories.
So
you
know
how
do
we
discretize
the
system
to
be
solved
for
the
form
problem,
though
those
kinds
of
details?
B
So
that
was
my
sort
of
a
proposal
for
organization
and
I
think
we
can
kind
of
take
the
best
things
from
what
we've
done
with
the
discretized
website
and
take
the
best
things
out
of
what
I've
got
here
and
come
up
with
something
that
should
be
pretty
good
yeah.
So
I
mostly
wanted
to
figure
out
get
some
comments
on
this
and
then
figure
out
who
is
interested
in
being
a
part
of
it?
B
D
F
A
Yeah
I
mean
like
I,
think
this
is
looking
really
solid
Devin
and
the
one
thing
that
I
was
thinking
well,
two
things
I
guess
actually
is
one
I
think
starting
in
dis.
Critize
might
be
nice
because
it's
like
pretty
it's
a
smaller
package,
so
we
can
sort
of
play
around
with
like
how
much
detail
is
needed
in,
like
the
user
guide
versus
perhaps
a
theory
section,
because
we
could
we
could
go
a
bit
more
in
that's
needed.
A
We
also
could
try
and
find
like
do
a
good
job
of
finding
appropriate
references,
and
things
like
that.
Like
there's
a
lot
of
things
where
we
can
point
people
to
to
sum
of
all
that's
good
stuff,
and
so
we
don't
need
to
reinvent
those
things.
The
other
thing
is
like
I
think
as
we
do
this,
it
might
be
useful
to
kind
of
create,
and
this
could
be
its
own,
like
sim
paid
meta
repo,
but
a
few
guidelines
that
are
helping
us
like
scope.
A
What
goes
in
each
part
of
the
documentation
so
basically
saying
stuff
like
the
API
documentation,
really
should
be
code
usage.
Only
not
theory.
I
totally
agree
that
that's
the
whole
thing
and
it
might
be
nice
for
us
to
just
kind
of
like
scope
like
have
a
document
where
we
scope
these
kinds
of
things
same
thing
was
sort
of
like
the
separation
between
perhaps
and
examples
gallery
and
the
user
guide.
So
where
I'm
thinking
that
this
is
based
on
Leo's
work
in
Fatih
Ando
in
Verde,
I'll
just
show
you
a
quick.
A
But
I
think
there's
we
can
think
of
examples
slightly
differently
and
I'll.
Show
you
this
I
guess
in
the
way
that
the
discretized
Docs
organized
too,
but
it's
very
much
inspired
by
what
Leo
did.
The
gallery
is
sort
of
like
our
examples
right
now,
where
it's
just
here's
a
collection
of
things
that
you
can
do
with
this
software
package
yeah
and
then
the
user
guide
is
much
more
targeted
like
here
is
how
I
go
and
sample
data
or
sorry.
How
do
we
go
and
do
trend
estimation?
A
B
D
A
So
if
we
actually
look
at
the
discretized
repo
there's,
one
folder
called
examples
and
that'll
generate
like
the
gallery
and
then
there's
one
called
tutorials
and
those
actually
are
going
to
be
used
to
generate
just
like
the
single
script.
So
they
they
both
are
following
the
exact
same
like
Python
syntax,
our
Python
file
structure,
but
just
they're
stored
in
different
places,
because
we
like
put
them
in
different
places
on
the
website.
A
A
B
B
A
And
then
to
like
what
we
can
do
and
I
think
this
would
be
a
nice
way
to
try
and
do
it
for
the
district
I
start
to,
and
this
enables
multiple
people
to
contribute
if
they
want
to
just
basically
do
like
almost
1:1
scripted
or
one
I
didn't
edit
time.
So
they're
really
lightweight
way
to
pull
requests.
Does
that
make
sense?
A
B
C
B
B
A
B
H
Actually
so
I
agree
with
a
lot
of
the
things
that
you're
saying:
Devon
right,
yeah,
okay,
I've,
actually
I've
had
actually
a
lot
of
issues
with
trying
to
figure
out
how
exactly
to
use
some
of
like
how
to
use
the
commands,
because
I'm
not
entirely
sure
exactly
what
order,
how
what
type
they
need
to
be
in,
like
I
mean
I
can
see
that
type
like
list
exactly
how
it's
supposed
to
work
within
calling
the
survey
function,
that's
something
that
I've
been
having
an
issue
with
and
having
like
a
low
level.
B
H
Another
thing
that
would
be
super
useful
is
that,
like
you
were
saying,
with
using
hyperlinks
within
there
and
having
like
sources
receivers
like
every
single
section
that
you
go
like
say,
you
start
at
the
sources
doing
again
hyperlink
headers
sources
receivers,
and
that
way
you
could
jump
back
and
forth
because
I
am
DUP
having
to
scroll
through
several
different
ways
to
try
to
figure
out
exactly
what
I
need
in
order
to
build
what
I'm
actually
trying
to
figure
well.
So
that
would
be
actually
really
useful.
H
Right
now,
I'm
trying
to
do
a
grounded
source
frequency
domain,
iam
again
also
I'm.
You
know
telluric
problem
so
and
I'm
looking
in
actually
turning
to
a
do
and
I'm
an
isotopic
case
or
both
of
those
which
we
don't
have
documentation
there
do
that
yet
so,
but
so
I've
been
having
a
little
bit
of
issues,
one
learn
how
to
use
the
meshes,
even
though
there's
a
great
example.
I,
remember,
learning
breaking
it
up
into
like
the
three
boxes
was
that's
how
that
works.
H
H
A
And
if
you
have,
we
can
speculate
the
links
for
the
issues
with
respect
to
documentation,
but
when,
like
on
the
github
issues,
but
one
thing
that
would
be
extremely
useful
sort
of,
even
as
we're
refactoring
things
is,
if
your
doll
so
dish
will
heard
of
keep
track
of
questions
that
you
have
or
things
that
are
infusing
because
I
mean
refactored
the
documentation.
It's
helpful
to
have
in
mind
like
we
need
to
make
sure
that
it
actually
solved
these
real
questions
that
use
yourself.
A
H
I've
been
keeping
a
running
like
thought,
process
and
questions
document,
so
I
can
organize
that
into
something
a
little
more
reasonable
and
send
that
your
way
that'd.
H
A
B
A
What
we
can
do,
too,
is
if
you
want
to
connect
either
tomorrow
or
Thursday,
even
just
like
for
a
brief
chat
to
sort
of
go
over
what's
in
there
and
like
how
to
proceed.
Just
ping
me
on
slack
and
we
can
find
a
time
the
afternoons
are
really
busy,
but
the
mornings
I've
got
a
little
more
flexibility.
Okay,
yeah.
B
B
A
Other,
like
topics
things
you
want
to
chat
about,
or
things
related
to
the
boxing
bring
up.
A
A
F
F
Kind
of
belong
along
the
wire
path
to
the
appropriate
edges,
so
I
kind
of
rewritten
a
function
that
will
do
that
and
they're
trying
to
test
it,
just
to
make
sure
that
we're
getting
kind
of
a
good
agreement
between
the
tensor
and
the
octree
and
then
I've
also
been
testing
it
against
the
e3d
code.
The
UVC
code,
oh
nice,.
A
F
I
talked
with
Devin,
and
he
suggested
that
we
write
like
a
little
analytic
that
just
kind
of
numerically
integrates
like
a
horizontal
electric,
dipole
kind
of
along
the
wire
path
to
simulate
a
finite
length
wire.
And
so
we
have
a
little
analytic
that
we
can
compare
to
those
ones
as
well.
So
I've
just
been
kind
of
playing
around
with
that
to
try
to
make
sure
that
things
are
behaving
reasonably
and
trying
to
figure
out
kind
of.
F
J
F
The
line
source
function
right
now.
It's
only
really
working
if
your
source
wire
path
falls
within
kind
of
a
uniform
region
of
the
octree
mesh.
It
has
your
smallest
cell
size
if
you
have
cell
size
changes
along
that
wire
path
or
you
don't
have
your
kind
of
base
cell
size
in
that
region.
You're
gonna
run
into
problems,
but
Joe
wrote
up
a
quick
function
or
at
least
the
template
for
a
function.
F
It
shouldn't
help
us
generalize
that
pretty
pretty
easily
and
so
I
need
to
just
touch
back
with
him
again
basically
and
see
where
this
function
was,
that
he
kind
of
showed
me
an
example
of
and
if
it's
kind
of
in
a
usable
state
where
I
can
start
trying
to
test
it
out
a
little
bit
more
and
trying
to
integrate
it
into
this
function.
But
the
basic
stuff
is
I,
think
there
and
I
think
we're
getting
overall,
pretty
good
agreement
with
the
analytic
and
with
the
EBC
code.
A
B
A
F
To
write
just
a
couple,
little
functions
that
all
like
easily
expose
the
edges
for
a
given
cell.
Instead
of
right,
it's
like
right
now,
I'm,
basically
using
like
distance
calculations
based
on
like
the
Pierce
point
of
the
wire
path
or
like
the
cell
Center,
and
then
using
kind
of
these
distance
measures
to
figure
out
which
edges
things
need
to
be
assigned
to.
So
it's
probably
not
the
most
like
efficient
way
of
doing
it.
F
A
D
F
D
F
J
A
One
more
just
like
quick
requesting
this
is
somewhat
related,
because
I
was
just
about
to
ask
you
if
you
have
that
on
a
branch
somewhere,
but
we
also
heard
like
I,
think
there's
something
like
40
branches
of
simpang
right
now,
which
is
a
lot
and
a
lot
of
them
are
actually
quite
a
sale
as
in
like
are
there's
37,
and
some
of
it
were
like
a
year
old.
And
so
if
people
would
just
be
willing
to
take
a
look
here.
A
Just
if
it's
in
paid
branches-
and
whatever
is
yours,
and
if
it's
like
I
went
through
and
do
we
did
everything
that
could
safely
be
deleted
in
the
sense
that
the
branch
was
not
ahead
at
all.
So,
like
all
of
the
changes
had
either
been,
were
all
the
changes
had
been
merged
in
I
deleted
any
of
those
branches,
but
there's
a
handful
where
I
think
like
people
started
to
explore
an
idea
and
then
maybe
stopped
and
who
dawn,
and
maybe
we
implemented
it
in
a
different
way
and
I
did
not
delete
any
of
those.
A
So
if
you
have
a
look
at
like
where
there's
more
branches
and
if
there's
something
that
you
haven't
updated
in
three
years-
and
you
know
that
you're
not
planning
to
touch
it
again,
if
you
could
just
delete
it,
that
would
be
great.
A
A
E
Been
trying
to
get
those
sensitivities
to,
of
course,
but
it
seems
okay,
I,
don't
think
it's
there
come
with
me
with
Oh
me
use
the
problem
that
dot
get
jtj
bag.
What
is
that
supposed
to
be
an
inversion
problem
or
server
problem?
Dc
problem,
you
see
every
case,
Oh
problem.
Do
you
see?
Maya
anyway,
is
the
one
that
I
took
from
master,
doesn't
have
that
so
when
you
try
to
do
it
from
the
update
sensitivity
or
like
the
pre-conditioner
side
of
things,
it.