►
From YouTube: SimPEG meeting Feb 26
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
B
B
B
C
Nothing
really
I
kind
of
been
picking
up
a
new
processing
code
kind
of
stuff
for
our
new
surveys,
but
I'm
gonna
be
working.
We
got
some
clients
that
want
to
be
routine
stuff
and
I.
Remember
you
talking
about.
We
can
kind
of
assume
that
with
the
3d
code
we
could
do
something
there.
I
might
bug
you
guys
here
in
a
bit
like
next
week
that
and
the
a
inverse
matrix
is
symmetric.
So
if
don't
need
them
both,
but
other
than
that,
that's
all
I
got.
A
A
So
he
was
looking
at
storing
some
of
the
matrix
factorizations
and
right
now
and
throughout
the
code
we
work
with
a
and
a
transpose
when
we're
doing
a
Geling,
but
because
it's
symmetric,
we
don't
actually
need
to
do
like
we
don't
need
to
refactor,
and
so
that's
something
that
we're
doing
in
a
lot
of
places.
But
ya
know
we
could
streamline
yeah.
A
E
Yes,
we
had,
we
had
an
adventure.
I
think
this
would
be
a
you
could
call
this
a
simple
adventure,
because
we
we
plan
to
do
a
lot
of
our
teaching
and
instructing
around
using
jupiter
notebooks.
If
you've
heard
of
those
yeah
and
use
my
binder
and
all
still
anaconda,
and
then
you
find
out
that
maybe
if
they
actually
had
Wi-Fi,
it
would
be
helpful.
E
You
know
really
deserves
to
be
complimented
on
this,
because
if
you
could
just
see
how
the
learning
could
come
about,
even
though
you
know
the
basic
mathematical
understanding
or
you
know,
any
kind
of
technical
material
could
not
really
be
understood
because
their
mathematics
level
was
actually
much
lower
than
we
had
anticipated.
So
yeah
there
was
a
number
of
apps
I,
guess,
there's
probably
six
or
seven
there.
Now
that
are
available
and
yeah
we
used.
We.
E
People
were
they
were,
they
would
be
involved.
I
mean
I,
think
that
was.
That
was
the
thing
it
just
really
got
engaged
with
with
the
material.
So
I
think
that
this
whole
set
of
material
that
the
slides
and
the
apps
that
are
being
put
together.
We
need
a
little
bit
of
refurbishments
just
to
kind
of
really
tidy
them
up,
but
I
think
this
is
going
to
be
just
a
wonderful
resource
that
can
be
used
virtually
everywhere.
So
the
you
know
the
1d.
E
You
know
that
the
parametric
and
then
the
1d
smooth
and
then
we've
got
the
2d
2.5
D
code,
so
we've
been
making
use
of
that
yeah
it's
slow,
but
it
seems
to
be
giving
results
that
are
comparable
to
res
2
D,
which
is
the
Loki's
code,
and
also
the
dcpip
2d
UVC
and
I,
and
we
want
to
do
some
more
testing
in
to
making
no
we're
getting
the
right
results
from
these
codes.
But
yeah
aside
from
the
fact
that
it's
slow,
it
actually
seems
to
be
working
pretty
well.
I've
talked
to
Joe
and
Joe.
E
You
know
spent
an
evening
just
taking
a
look
through
and
did
some
profiling.
You
talked
about
a
bit
more,
but
he
found
a
number
of
places
that
looked
like
they
could
be
so
John
I
was
gonna.
Ask
you,
how
have
you
used
the
2d
code
or
the
2.5
D
code?
Because
you
were
just
talking
about
wanting
to
run
there?
Oh
I.
C
E
Sometimes
the
lines
got
a
bit
crook'd
when
you
run
into
run
into
road,
I
need
to
take
a
detour,
or
in
one
case
it
was
just
curving
around
so
we'll
have
the
opportunity
to
look
at
potential
3d
effects,
I
think
in
the
end,
it's
going
to
make
some
really
nice
case
studies
and
as
we
try
to
get
through
this
you're
more
intensively,
it's
it's
a
perfect
opportunity
side.
You
know
where
we
can
speed
things
up
so
that
both
2d
and
the
3d
nice.
C
E
C
E
That's
that's
great.
It
would
be
nice
to
kind
of
find
out
what
what
you
got
and
then
yeah
I
guess.
The
other
thing
that
maybe
kind
of
comes
up
with
this
is
maybe
where
to
where
to
put
these
notebooks
so
that
they
can
be,
they
could
be
shared,
actually
Lindsay.
The
reason
I
asked
kind
of
bring
that
up.
At
this
point.
It's
a
bit
tangential
but
Allison
Malcolm
was
here
and
she's
been
using
some
of
the
notebooks
that
we
had
for
the
GPP
and
he's
you
know,
she's
further
developed
them
and.
A
A
couple
in
a
couple
of
weeks
time,
if
that's
helpful
or
if,
like
I,
know
that
Jo
has
been
motoring.
So
so
that's
great,
because
I
know
that
branching
a
ton
of
documentation,
updates
and
tutorials.
So
that
will
be
helpful
for
onboarding
other
people
yeah.
But
so
we
started
the
education
in
discourse
and
there's
a
couple
posts
in
there.
Deep
ones
posted
and
cram
has
posted.
So
if
anyone
wants
to
chime
in
on
those
conversations,
that
would
be
great
I
think
so.
A
The
way-
and
this
may
or
may
not
be
the
most
effective
way
to
move
forwards,
and
this
is
something
we
should
think
through
the
way
that
the
GSI
stuff
kind
of
works
right
now
is,
we've
got
at
least
4
a.m.
and
for
the
GPG
is
we
have
basically
a
notebook
warehouse,
that's
the
Geo
style
labs
and
then
for
each
course.
A
You
basically
just
copy/paste
a
subset
of
those
notebooks
and
import
the
geosite
labs
code,
and
then
you
can
sort
of
tailor
your
course
to
include
whatever
subset
is
so
if
that
model
seems
to
be
working,
we
can
certainly
continue
with
that.
But
if
not,
we
can
rethink
things
a
bit.
I
know
that,
for
example,
Leo
started
a
repository
or
an
organization,
I
think
public
did
geophysics
library
or
something
like
that,
and
the
goal
with
that
was
to
be
much
more
like
smaller
scope
things.
A
So
each
repository
was
basically
a
single
notebook
plus
an
environment
file
and
whatever,
maybe
like
a
readme,
was
sort
of
some
of
the
learning
goals
and
things
like
that,
so
that
actually
sort
of
goes
the
other
extreme.
So
I
don't
know
where
we
want
to
be
sitting
with
all
of
that,
because
yeah
we've
kind
of
got
notebooks
all
over
all
over
the
place.
F
A
E
A
A
Repository
and
say
that
she's
made
some
updates
and
if
she's
comfortable,
she
can
make
a
pluralist
she's,
not
comfortable
with
github.
Then
we
can
talk
about
how
to
actually
incorporate
her
her
stuff,
either
like
sitting
down
I'm
having
a
phone
call
with
her
and
just
walking
through
that
or
we
could
do
something
via
Dropbox
or
whatever,
but
yeah
I
think
just
getting
sense
of
like
which
notebooks
did
she
change.
And
then
then
we
can
move
forward
on
that
that
trajectory
and
then
figure
out
sort
of
a
broader,
broader
recognize
own
moving
forward.
Okay,.
E
E
No,
what
do
we
do
about
John
who's
sitting
there
and
said
he's
got
a
number
of
notebooks
3dc
resistivity,
you
know
we're
we're
going
to
be
using.
You
know
the
3d
Sagi
is
definitely
got
you
know
notebooks,
but
that
one
John's
got
something.
How
do
we
kind
of
communicate
and
decide
what
we
really
want
to?
You
know
further
develop
and
have
general
or
what
you
know
parts
are
just
like.
Okay,
that's
for
me!
That's
my
notebook
and
you
know
we
don't
really
need
to
worry
too
much
about
upgrading
or
sharing
it.
Yeah.
A
I
mean
so
maybe
we
need
to
think
through,
like
I,
like
the
way
that
we've
set
up
the
simple
research
github
organization
is
anybody
can
create
their
own
repository
and
then
it's
just
like
here's
some
stuff
that
I
did.
That
goes
either
with
the
publication
or
it's
just
a
scratch
base.
Like
that's,
that's
fine.
We
could
maybe
think
I
think
we
would
need
a
bit
more
structure
and
scoping
for
like
a
Geo
size
style.
A
Thank
you
sort
of
looking
at
who
is
the
intended
audience.
I
think
matters,
because
the
geocell
lab
stuff
right
now
is
very
much
just
like
here
is
a
notebook,
that's
an
app
and
that's
that's
great,
and
that
serves
a
specific
audience,
but
for
3d
inversion
we
may
or
may
not
want
to
turn
the
entire
thing
into
it.
Like
a
widget
eyes.
A
No
book
like
that
might
not
actually
be
the
best
way
for
users
to
get
familiar
with
the
code
and
interact
if
they're
doing
something,
that's
3d.
I
think
it's
in
some
sense
is
fair
to
assume
that,
like
they
can
maybe
punch
in
a
line
of
code
to
like
type
out
the
file
name
and
things
like
that,
and
so
that
might
make
more
sense,
as
just
like
a
very
nicely
structured
notebook
with
maybe
a
few
widgets
in
there
for
like
exploring
inversion,
results
and
stuff
like
that.
A
I,
don't
I,
don't
know,
but
I
think
that
those
things
like
perhaps
have
different
scopes.
So
I
wonder
if
you
want
to
start
like
if
that
would
either
be
a
new
sim,
peg
repository
or
a
new
DSi
repository
just
around,
for
example,
DC
resistivity
and
we
could
just
do
have
like
a
collection
of
notebooks
that
work
through,
like
example,
notebooks
that
work
through
DC
resistivity.
A
E
Something
too
I
think
that's
something
for
all
of
us
to
think
about,
because
it's
the
perfect
timing
right,
it's
just
when
these
things
have
just
converged
from
a
whole
bunch
of
different
directions
and
and
actually
I'll
I'll.
Let
people
know
another
thing
that
is.
This
is
related
to
this,
and
that
is
the
whole
concept
of
using
case
histories
as
the
real
glue
for
you
know
any
of
these
DC
resistivity
wealth
or
any
kind
of
survey.
So
what
we
found
in
in
Myanmar.
E
All
of
that
is
documented.
So
that
means
that
somebody
else
can
come
through
and
discard
the
same
points
that
you
did
and
know
exactly
what
was
done
and
then
for
the
inversions
in
using
any
of
the
you
know
the
simple
codes
again,
all
of
the
all
the
parameters
are
there.
Whatever
your
mesh
was,
and
it's
just
all
document
actually
inside
the
case
history
and
then
you've
got
a
final
result
and
with.
E
A
E
It's
it's
it's
freely
available
and
then
there's
some
filtering,
that's
that's
done
and
those
are
captured
so
that
somebody
else
could
start
with
the
raw
data
and
get
their
own
copy
of
this
process
and
have
enough
information
that
we
decide.
Okay,
what's
you
know?
What's
the
data
set
that
I'm
going
to
invert
and
within
that
within
a
Dropbox
file?
We
also
have
those
processed
data.
So
somebody
could,
you
know
just
start
from
there
and
then
carry
through
and
do.
E
You
know
there
was
a
new
revelation
and
some
people
you
might
be
interested
as
to
what
was
actually
going
on
in
in
Myanmar
and
that
is
DC
resistivity
soundings
have
been
traditionally
used
there
and
there's
been
something
like
5,000
soundings
done
over
the
last
I
know,
10
or
15
years.
There
they're,
basically
all
slumber
shades
soundings,
so
each
sounding
is
done
by
the
National
DRD.
E
E
Sometimes
he
has
a
couple
of
people
kind
of
running
code
for
him
and
then
he
takes
the
results
of
that
and
he
makes
the
final
interpretation
of
like
whether
there's
a
potential
aquifer
up
here
or
there,
and
that
is
all
encoded
then
on
on
a
single
piece
that
shows
you
know
the
resistivity
structure
and
his
interpretation.
That
is
then
sent
down
to
the
state
level.
They
see
this
single
piece
of
paper
and
then
they
decide
to
drill
at
the
state
level.
They
have
no
idea
how
that
model
was
generated.
E
All
they
have
is
like.
Ok,
here's
there's
a
resistivity
model
and
you
know
we're
supposed
to
find
an
aquifer,
equals
death
so
and
that's
just
about
as
extreme
and
and
member
of
geophysical
surveying
and
interpretations.
I
think
you
yeah,
and
so
the
that
concept
of
just
trying
to
have
the
data
and
have
whatever
analysis,
you'd
be
you're.
Doing,
reproducible
I
think
yours
will
be
cute
for
them.
We
just
great
to
see
that
pushed
forward.
E
G
F
G
G
And
then
let
people
do
their
own
experiments.
You
know
because
I'm
just
scared,
we're
gonna
burn
a
lot
of
resources
that
we
have
already
very
little.
We
have
Joe
as
a
resource
and
if
we
spent
too
much
time
handling
notebooks
we're
just
going
to
burn
through
it
and
we're
not
going
to
accomplish
what
we.
Why
we're
here
to
do?
That's
that's
my
opinion.
What.
E
G
Although
that
the
Hawaiian
icon
dies
one
thing
and
then
Jupiter,
yeah
and
then
Jupiter
requires
chrome,
it
doesn't
think
there's
a
handle
other
other
browsers.
So
you
need
to
like
step
people
left
for
that
and
then,
if
you
wanna,
you
know,
if
you
want
to
run
their
same
peg
m1d,
you
need
to
make
sure
that
the
they
come
filed
since
icon
that
icons
and
not
the
other
one,
because
it's
on
path
right
now,
it's
just
it's
just
a
nightmare.
I
was
running
trying
to
rerun
the
old
jewel
tolki
up.
What
I
did
with
I
am.
G
A
Yeah
Dom
I
think
it's
a
very
fair
point
that
we
should
like
documentation
is
really
the
place
to
be
and
like
examples
in
the
doctor's
really
the
place
to
be
investing
I
mean
the
notebooks
make
sense
for
like
targeted
projects,
but
really
getting
focus
up
and
running.
It's
yeah.
The
maintenance
is,
is
for
sure
non-trivial
and
it.
G
They're,
just
they're
just
really
hard
to
version
control.
Alright,
like
notebooks,
are
there
enough?
There
are
not
control
on
yet
so
that's
unless
they
are
inside
of
documentation
and
they
run
inside,
and
we
know
it
there
if
they're
working
on
when
we
build
the
dogs.
Otherwise
it's
just
such
a
you're
gonna
spend
so
much
time
trying
to
maintain
those
notebooks
and
I'm,
not
sure
how
much
traction
we're
actually
getting
out
of
them.
You
know
if
we
have
one
person
now
under
the
notebook
where
we
spend
another
week,
total
time,
maintaining
it
like.
A
An
important
point
to
think
through
with
the
workshop
one
of
the
things
so
like
for
the
s
e-g.
We
should
think
through
what
the
goals
of
that
really
are,
because
one
thing
that
we
could
do
if
installation
is
expressively,
not
a
goal,
then
we
can
launch
a
Jupiter
Cub
and
it's
something
that's
actually
pretty
easy
to
do.
A
If
we
thought
not
a
huge
number
of
users
as
long
as
the
Internet
is
okay
with
s
e-g,
that's
something
that
we
could
do,
because
if
the
goal
is
just
to
teach
people,
the
API
then
like
having
them
play
around.
You
know
both
these
nice
but
I
completely
agree
that
we
yeah,
like
sort
of
the
maintenance
of
notebooks
as
a
job
of
ours,
is
not
a
great
great
thing
to
take
on
yeah.
G
And
we
don't
want
to
spend,
we
don't
have
to
waste
an
hour
an
hour
and
a
half
just
having
you
know,
ten
people
in
a
room
and
stall
anaconda
and
all
the
dependencies
like
I've
done
this
already
three
times
this
weekend.
It's
huge
waste
of
time
like
I,
don't
want
to
have
to
do
it
again,
yeah
or
maybe
we
just
have
like.
We
have
a
chest
file.
You
know
that
if
you
can
run
this,
it
says
because
I
remember
that
the
when
I
did
be
at
the
Python
carpentry.
G
You
know
the
software
carpentry,
that's
what
they
were
asking
people
to
do.
If
you
can
run
this-
and
it
says
okay,
you
give
then
show
up
if
it
doesn't
do
it
that
email
us
at
a
time
and
we'll
figure
it
out,
but
don't
show
up
without
an
installation,
because
it's
it's
too
much
of
a
waste.
We
only
have
a
half
a
day
right
for
that
for
that
worship.
So
I.
B
G
E
A
Yeah,
because
to
that
point
we
might
actually
be
able
to
get
and
I
have
never
looked
into
this,
but
I
wouldn't
be
surprised
if
we
could
get
basically
like
pay
for
a
cell
service.
That
just
gives
us
a
big
enough
hotspot,
for
you
know:
30
ish
people
yeah,
but
these
are
like
we
can.
We
can
brainstorm
on
this
before
I
see
because
this
yeah,
we
don't
want
to
be
dealing
with
having
folks
try
anaconda
for
the
one
job
you.
G
G
E
E
G
G
G
B
G
No
I'm
certainly
yeah.
We
just
need
to
basically
to
make
sure
that
there's
some
of
sensitivities
is
is
the
same
as
the
global
and
to
make
sure
that
the
transfer
model
property
to
the
local
meshes
is
like
also
also
make
sense,
yeah
and
then
yeah.
It's
gonna
be
small,
no
inversion.
We
just
need
to
have
a
basically
the
back
in
port
mapping
working
and
other
than
that.
G
I
have
I,
had
more
interests
to
keep
working
on
the
on
the
on
the
my
Grady
AMA
tree
yesterday,
so
we're
gonna
be
pushing
the
next
week
and
then
I,
just
the
smaller
work
and
exposing
sent
back
through
the
to
the
analyst
API.
So
I've
been
working
on
at
work.
It's
kind
of
everything
is
kind
of
converging.
So
that
sounds
good
for
me.
Sitting
time
did
you.
Toolkit
is
actually
sewed.
G
I
am
I
we
met
again
with
the
guys
at
Minerva,
because
they
they
really
use
it
heavily
for
their
their
daily
work,
but
I
just
don't
want
to
have
to
maintain
import
exports
anymore.
You
know
geo
silage,
aox,
pie
and
and
there's
a
bunch
of
requirements
that
break
down.
So
we
might
just
simplify
the
whole
package
and
just
only
do
like
a
few
core
core.
They,
like
you,
know,
operations
and
draw
up
all
the
input
input
output
visits
it's
just
too
much
too
much
appendices.
A
And
Dom
do
you
think,
maybe
like
one
way
to
hit
perhaps
graceful
you
drop?
That
is
just
like
put
it
in
the
comment
box
or
like
provide
at
least
provide
some
instruction
Howie.
If
somebody
wants
to
do
something
more
advanced,
like
there's
a
queue
that
yes,
this
is
more
advanced
for
like
they
look
at
this
package
and
you
can
figure
it
out
yourself,
yeah.
G
That's
a
good
idea,
I
think
yeah
we've
run
those
dependencies
because
we
want
it
to
I,
like
very
people
like
newcomers
to
be
able
to
just
straight
grab
that
I
could
Joseph
gorilla
or
an
arc
shapefile,
but
the
dependencies
are
intense.
So
we
can
just
add
comment
and
say
if
you
want
to,
if
you
want
to
get
a
grip,
get
a
grill,
some
warehouse
and
bring
it
in
you
know.
That's
all
you
have
a
thing,
I
think
that's
fair,
yeah,
I.
B
E
A
Open
up
if
there
is
any
sort
of
priority
items,
the
thing
that
I
think
we
should
go
through
and
I'll,
maybe
ask
that
even
if
we've
got
time
to
do
this
now,
there's
three
issues
that
I
think
Joe
has
pointed
to
and
draw
what
you
speak
to
these,
that
we
need
to
start
coming
to
decisions
on
for
moving
forward
with
the
simulation
branch,
and
so
it
would
be
great
to
get
input
from
folks
so
that
we
can.
We
can
make
a
decision
on
these
things.
Joe.
Do
you
want
to.
B
G
A
G
B
B
B
B
B
Okay,
eventually,
right
now
like
right,
there's
I,
don't
know
if
you
can
see
my
mouse
or
not
yep.
F
B
B
Potential
fields
instead
drastically
different,
like
these
are
all
the
same
kind
of
class
they're,
just
different
subsets
of
that
class
right,
whatever
BRM
stuff
it's
different
again
and
for
the
other
two
outliers
they're,
like
the
Richard's
in
the
straight
great
seismology
thing
again,
it's
you
know
different.
So
the
idea
is
we
just
come
up
with
a
consistent
naming
formulation
that
we
would
propagate
to
all
of
them,
so
a
few
options
and
I
put
out
there.
B
Okay,
a
simulation
then,
whatever
dimensionality
is,
is
and
then
some
short
a
short
description
about
the
problem
so
for
the
efj.
So
for
like
the
electric
field,
so
it's
one
optionally
simulation
three
de
for
the
electric
field
simulation
yeah.
You
should
3d
P
for
the
magnetic
flux
density
simulation,
green
EJ.
Another
option
would
be
maybe
a
longer
description
about
the
simulation,
so
instead
of
e
will
be
called
electric
field
or
magnetic
flux,
density
self,
centered
into
a
real
simulation,
or
something
like
that.
B
G
C
G
E
A
Yeah,
initially
I
was
drawn
more
towards
the
short
description
II
just
cuz.
That's
like
the
thing
that
we're
actually
discretizing
but
hearing
this
I
think
that
yeah,
that
seems
that
seems
pretty
reasonable,
especially
if
we're
importing
it,
which
work
and
and
or
I
think
eventually
creating.
Basically
a
higher
level
wrapper
layer.
A
B
G
A
It
makes
more
sense
in
this
case
to
sort
of
clock
is
staying.
It
p.m.
here
so
in
this
case
we're
basically
overwriting
the
way
that,
like
the
a
matrix,
is
formed
for
each
of
those,
each
one
has
a
different
K
matrix.
The
class
structure
is
identical,
so
I
think
for
those
ones.
The
inheritance
side
of
things
makes
makes
it
easier
to
have
them
as
separate
classes.
B
F
B
B
And
let
me
go
over
it
so,
basically,
right
now
they
use
some
of
the
biggest
formula
kind
of
in
terms
of
the
code
rate
like
it's
this
term
terminology
of
the
code,
but
there's
a
standard
deviation.
It's
multiplied
by
the
absolute
value,
the
data
they
add
a
noise
floor
and
that
equals
some
uncertainty
right
well.
I
mean
most
the
time
we're
using
uncertainty
as
the
standard
deviation
of
a
Gaussian
right
certainty
is
actually
one
of
the
standard
deviation,
so
kind
of
doesn't
like
having
this
here
doesn't
quite
make
sense
like.
B
Great,
we
were
talking
about
kind
of
possibly
renaming
that
quantity
or
just
asking
so
some
of
the
options
for
name
we
naming
it
breather
relative
error
percent
error
I
think
we
kind
of
look
talking
about
one
of
those
two
and
then
Tom
brought
up
something
about
just
okay
screw
it.
You
just
have
uncertainty.
Have
it
be
standard
deviation
like
not
worried
about
either
the
two
of
them
I
think
I.