►
From YouTube: SimPEG meeting April 11
Description
Combo objective functions and joint inversions
A
A
I,
don't
know
if
you
guys
might
start
with
things
on
your
list
or
the
thing
I
want
to
talk
about
it.
Drank
versions
and
I
have
a
combo.
A
A
Ok,
so
what
I
wanted
to
go
over
is
the
objective
function,
stuff
in
particular,
with
three
versions:
I
was
looking
at
your
directives
and
also
your
script
just
to
get
some
ideas
on
like
we're
constraints
are
and
what
kind
of
things
we
want
to
be
able
to
do
so.
The
first
thing
I
well
there's
two
things
that
came
up
is
both
which
we're
talking
about
the
validation
of
directives
and
then
like
working
with
properties
of
the
objective
function.
I'll
start.
A
I
think
that's
more
straight
forward,
so
in
this
case
there
are
things
like
the
ordering
matters
as
well
as
potentially
like
the
type
of
objective
function.
You
feat
something
to
like
the
irls.
You
should
only
give
it
the
sparse,
if
you
give
it
anything
else
like
it's,
not
actually
doing
a
veteran
primary.
So
in
this
case,
what
I've
done
is
added
a.
A
A
E
A
C
A
Doesn't
actually
go,
excuse
me,
so
it
doesn't
go
like
in
the
initialize
or
anything
like
that.
It's
just
a
separate
method.
So
here
there
is
just
a
new
method
called
death
validate
okay.
C
A
Can
be
anything
about
the
creation
of
the
directive
and
then
also
why
I
gave
it.
The
list
is
because
it
does
like
it
cares
about
the
other
things
in
there.
So
then,
all
that
happens
that
when
this
is
actually
called,
is
within
the
so
this
is
now
when
you
create
a
directive
list.
All
it
does
is
now
the
directive
list
has
a
method
called
validate
on
itself,
and
it's
just
going
to
go
through
all
of
its
directives
and
say:
are
you
valid
yes
or
no?
Oh
man.
C
A
A
validating
my
sweet
sweet
and
that
Franklin
down
the
road
can
play
with
properties
nicely.
Potentially
we
don't
have
properties
injected
into
the
directives
yet,
but
that's
on
the
list.
So
where
is
this
yeah.
B
A
So
that's
like
Chris,
you
jerk
yeah,
it's
nice
to
have
because,
especially
when
you
start
playing
with
multiple
directives
and
things
like
that,
don't
like
yeah,
so
dude
cool
okay.
So
that's
that
one.
This
is
one
that
I
would
appreciate.
Thoughts
on
I
was
chatting
with
Rowan
a
bit
about
it
last
night,
mostly
because
I
just
started
playing
with
some
like
base
functionality
and
Python
and
as
soon
as
you
start
messing
with
like
set
attribute
and
get
attribute.
That
scares
me,
but
you
can
do
some
really
cool
things.
I.
E
A
So
because
what
I
noticed
John
and
your
example
is
so
do
this,
so
you
had
done
something
like
this
and
then
defined
you
sparks,
but
that's
fine
still
break.
Is
there
one
times
break
1,
plus
2
times
rate
you
so
we're
not
going
to
do
a
joint
inversion
for
two
different
parameters,
and
then
you
want
to
set
like
the
MRF,
for
example,
and
so
in
this
case,
if
you
just
do,
raiga
and
r
f
equals.
A
A
A
So
this
is
what
we
were
getting
at
when
I
sooner
talk
about
exposed,
should
try
and
expose
properties,
and
so
I
think,
when
I
was
talking
to
Roland
I
think
link
is
actually
better
and
we
can
get
into
the
details
of
why
so
I'll
show
you
an
example
of
how,
like
I,
think
this
should
work.
So
in
this
case
we
have
our
big
one
and
write
to
you
and
right
now,
if
I
set
two
different
em
breves,
oh
I,
do
you
break
one
dot
com,
ref
plunge
or
two
da
ra?
It's
used.
A
Ok!
So
now
I
wanted
to
find
my
regularization,
which
is
now
composed
of
those
two
things
and
now
I
want
to
be
able
to
access
em
wrath
on
both.
So
what
the
idea
here
is
to
use
something
like
a
link
to
basically
then
expose
em
ref
from
the
children
objective
functions
to
the
top
level.
So
now,
if
I
do
something
like
this,
if
I
said
reg
got
em
breath
on
my
combo
and
I
want
to
then
see
what
reg
one
got
em
ref
is.
A
C
A
See
I
created
a
sketchy
version
of
it,
okay
and
so
right
now,
oh,
it
doesn't
like
what
we
pull
up
this
comment,
so
I
was
trying
to
throw
in
last
night
and
there's
some
weird
things
potentially
in
terms
of
behavior
that
we
want
to
just
clear
up
so
right
now
we
exposed
em
breath
or
the
link
well.
This
is
where
I've
switched
to
lately,
but
if
we
started
with
thinking
about
exposing
amurath
and
all
that
that
was
going
to
do
is
basically
give
you
a
downward
propagating
yes
same.
Yes,
the.
A
That's
a
good,
and
so
if
we
set
em
ref
is
a
and
we
print
that
that
would
have
propagated
all
the
way
down.
That's
fine
yeah,
but
then
in
the
in
its
current
status
you
actually
could
go
in
and
change
right,
one
and
right
to
dependent.
C
E
A
I
set
right
to
dem
records,
be,
and
now
I'm
looking
at
the
top
level
function.
What
should
that
return,
yeah
and
so
the
way
I
think
we
work
around,
that
is
we
actually,
instead
of
exposing
and
just
giving
you
a
downward
propagating
thing,
we
tied
them
all
together
and
basically
say
now.
If
I
change
em
rack
on
the
top
level
that
changes
in
the
plot
level,
I
change
in
the
bottom
level,
it's
also
going
to
change
it
in
the
top
level.
A
C
A
Well,
I
think
I
guess
the
like
my
comment
here
is
like
I
would
be
inclined
to
throw
a
warning
at
you.
If
you
do
this,
if
you're,
if
you
to
write
one
goddamn
ref
like
throw
a
warning
that
says
this
is
linked
to
these
other
objective
functions,
we
are
changing
those
as
well,
because
I
like
you,
should
be
working
at
it
from
the
top
level.
If
you
explicitly
hide
these
things
together.
A
C
A
A
C
A
That's
something
that
we
can
think
about
is
because
maybe
this
is
too
complicated
like
maybe
it
would
just
be
better
to
at
this
well.
The
other
thing
that
we
could
do
is
provide
if
you
call
right
up
amref.
It
then
just
gives
you
back
that
list
of
all
of
the
objective
functions
and
rest
on
the
subtle
thing.
There
is
that
if
you
have
added
objective
functions
together
that
don't
have
an
mrf
or
just
returned
aunty
list,
the
sizes
should
be
the
same,
so
it
could
return
num.
C
C
Just
be
again
same
things
happening
right
now
in
the
joint
inversion
right.
So
it's
a
you
call
it
what's
deep
brown
I
would
want
to
have
it
lists.
Always
you
know,
because
each
each
misfit
functions
should
return
something.
When
you
asked
what
my
deep
red
is
right,
can
we
always
return
the
lists?
Why
are
we
not
returning
less,
even
if
it's
not
if
it's
not
a
combo
or
obese,
always
your.
A
C
C
E
A
D
D
Yeah
I
mean
so
it's
like
if
property
is
not
linked
and
then
you
give
it
a
instance
and
a
property
name,
and
you
can
just
give
it
like
as
many
as
many
instances
in
property
names
as
you
want
and
it'll
link
them
all
together.
So
when
you
change
one,
it
changes
them
all
and
it
can
be
directional
or
it
can
be
like
just
changing
one
changes
the
other,
but
changing
the
other
doesn't
change.
One
cool.
D
See
ya,
it's
it's
on
a
on
a
pull
request.
If
you
want
to
see
it,
but
yes,
I
mean
it
seems
like
that
would
be
helpful.
It
looks
kind
of
like
that
is
what
you're
doing
with
link
I
haven't.
Looked
at
all
if
thats
MPEG
codes,
yeah.
A
Yeah
because
there's
there's
link
and
then
there's
also
like
the
ability
to
expose
it
on
the
parent
objective
function
and
the
way
I'm
doing
that
now
it
is
through
setattribute
and
get
attribute,
which
is
your.
What
I
was
her
to
asking
you
vote.
E
F
D
D
D
What
I
don't
know
enough
of
what
is
going
into
adding
these
regularization
together
so
like?
If
you
add,
can
you
add
to
regularization
that
look
totally
different
into
a
third
one
yeah,
you
can't
just
be
like.
Take
the
overlapping
stuff
or
something
or
well
good,.
A
A
But
what
we
could
do
is
basically
like
exposed
like
hesitant
and
I.
Don't
have
handle
my
we
could.
We
could
expose
everything
at
top
level
and
then
basically
just
give
you
lists
back
always.
F
E
A
D
F
A
C
B
C
E
C
A
B
A
C
C
C
Okay,
but
I,
realized
that
if
I
call
get
deep
red,
then
it
will
return
you
this
for
both,
but
that's
in
and.
A
F
C
Add
them
together,
it's
it's
a
complementary
function:
yeah,
oh
yeah!
You
should
be
able
to
call
that
thing.
So
if
they
call,
if
I
do
this
mr.
function
not
be
proud,
because,
usually
it's
a
misfit,
the
deep
breath
returns.
You
predict
the
beta
yeah
yeah.
If
you
do
this
on
the
combo,
it
returns
me
a
list
with
only
one
element
in
it,
which
is
one
of
the
two
but
yeah
I
don't
get
both
basically
but
now,
I
realize
if
I
call
inverse
problem
instead
getting
prepped.
You
issue
return
it
to
me.
Okay,.
A
B
A
E
B
E
C
C
A
A
Array,
I
guess,
is
a
little
more
flexible
if
I
were
to
give
it
a
list
of
two
things
or
like
if
you,
if
you
give
it
that.
B
E
A
A
A
E
A
B
C
C
A
Again,
hopefully,
something
we
can
achieve
with
the
the
linking
is
be
able
to
expose
deep
red
and
give
you
back
a
list
of
things.
Okay,.
B
A
I
mean
survey
makes
sense
to
have
deep
red
because
there
is
there's
one
problem.
One
model
like
it's:
it's
a
single
forward
simulation
at
that
point,
so
it
should
be
able
to
it
has
to
be
paired.
So
if
you
haven't
paired
it,
it
would
fail
to
get
d
Pryde
and
the
pairing
is
like
a.
What
are
your
thoughts
on
that?
Is
that
a
weird,
because
in
some
ways,
like
I,
think
we
should
probably
just
an
out
talking
to
Rowan
about
the
church
bay?
It's
just
you
basically
like
my
simulation
is,
are
now
something
like.
A
A
A
Cool
okay,
if
you
have
time
later
today,
I
would
be
game
to
just
like
sit
down
yeah.