►
From YouTube: SimPEG DC Hackathon
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).
B
A
Yes,
which
is
D,
we
have
done
a
whole
bunch
of
I,
mean
there's
been
a
bunch
work
done
on
the
DC
codes.
So
it's
chance
to
shadow
out
that
try
to
vote
some
conventions
and
like
now
that
we've
got
multiple
people
in
a
code
base
just
trying
to
come
up
with
standards
and
follow
some
of
the
Python
standards
that
are
already
out
there.
Yeah
I
was
there,
maybe
just
start
the
Google
Doc.
E
B
C
C
C
B
C
F
A
B
A
A
E
F
A
E
A
A
B
A
A
C
E
E
D
C
So
this
is
a
can
core
they're,
like
other
packages
related
like
IP
deployed
pcs
P.
So
obviously
all
the
like
it
not
exactly
same
physics,
but
that
very
someone,
physics
and
the
code
itself
was
pretty
similar
yeah.
So
there
are
a
lot
of
sharing
pieces,
so
I
think
it's
probably
good
to
like
just
chat
re-organized
this
yeah
inside
and
also
there's
like
a
little
bit
different
outside
and
inside
so
yeah
it'll,
be
country
of
Chad
I
have
everyone?
What
can
I
say?
Yeah.
D
C
B
C
A
B
C
F
C
A
So
actually,
I
think
the
place
to
start
is
f8
and
just
doing
a
bit
of
an
overview
of
that
is
that's
gonna,
leave
into
conversations
on
naming
conventions
and
all
invest
good
and
racketing
levels
and
I
realized
that,
like
some
of
these
things
seem
silly,
but
it
actually
was
really
evident
to
me
like
coming
through
about
4,000
line,
pull
requests,
it's
so
hard
to
do
when
people
are
using
like
different
bracketing
invitations
and
stuff.
Whereas
if
everything
is
consistent,
it's
like
so
much
easier
to
see
what's
changed
so.
A
That's
like
some
motivation,
I
guess
here:
okay,
so
I'm
gonna
put
this
on
slack.
This
is
the
8
style
guide.
So,
first
of
all,
so
you
guys
know
what
a
PEC
is.
Pe.
F
A
Enhancement
proposal:
ok,
so
there's
these
come
in
periodically
and
there's
I,
don't
know
they're
up
to
like
two
or
three
hundred
I
think.
But
that's
how
discussions
happen
before
the
code
changes,
and
so
this
was
a
pretty
early
one,
just
unlike
style
of
guides,
and
there
might
be
some
things
that,
like
don't
necessarily
agree
with,
but
at
the
same
time
standardizing
to
like
something
is
better
than
nothing.
A
F
A
A
F
D
A
D
A
A
So
that
is
this
pull
request
here.
This
ducks
and
community,
and
so
what
I've
tried
to
do
is
outline
just
a
few
of
the
details
on
conventions
where
to
find
stuff
on
Feb
8
and
all
of
that.
But
the
thing
in
that
page
so
figure
the
docks,
there's
a
getting
started
for
developers
and
I've
actually
copied
my
oh.
A
D
A
D
A
F
A
Can
also
like,
for
example,
if
you
hadn't
mixed,
you
can
convert
indentation
into
spaces
or
tabs
if
it
caught
myself.
A
C
How
about
in
like
that
when
you're
writing
the
code,
like
you
got
a
statement
right,
people
have
a
style,
yeah
and
then
I,
sometimes
that,
like
I,
have
my
own
style
yeah,
it's
probably
good
to
have
a
little
bit
of
like
dead
yeah,
not
sure.
That's
the
too
much
details
is
a
kind
of
fine,
like
whatever
I
mean.
A
A
D
A
E
A
A
Its
role
is
so
there's
a
few
different
cases
that
they're
gonna
talk
about,
so
the
ones
are
to
pay.
Attention
to
here
are
lowercase
with
underscores
uppercase.
Well,
those
ones
are
for
global
variables
really
and
then
camelcase
and
this
kiss
they
don't
recommend
ever
doing
capitalize
with
underscores.
So
we're
gonna
pick.
A
A
That's
something
so
those
actually,
we
should
not
be
naming
with
camel
case
as
much
function
names.
We
should
be
trying
to
use
lowercase
with
underscores
in
the
case
of
something
like
get
a
because
a
is
actually
referring
to
a
matrix
like
that.
That
is
something
that
I
think
we
should
break
bigger
convention
and
do
either
get
underscore
eight
or
what
we
could
actually
do
in
this
might
not
be
a
bad
idea,
is
like
get
system
matrix,
it's
a
little
more
verbose,
but
it's
actually
very
explicit.
A
E
A
F
A
So
once
we
actually
like
get
dis,
critize
and
sempai
folks
are
in
line
with
hi
bait,
we
can
actually
run
tests
to
make
sure
that
names
and
stuff
like
that
are
good.
But
right
now
that's.
D
A
C
A
A
D
D
A
D
C
A
C
C
C
A
A
We
can
go
over
it
in
the
mesh
class.
I
think
oh,
this
is
also
an
important
thing.
So
when
printing
erred
statements
or
warning
statements,
try
and
always
also
include
what
the
user
input
so,
instead
of
just
saying
invalid
input,
you
should
do
this.
Tell
me
what
they
told
you,
because
that's
especially
when
you're
dealing
with
what,
if
you
set
up
an
entire
Ford
simulation
and
it's
airing
somewhere
way
back
here.
You.
C
F
F
A
E
E
E
A
That
sounds
good.
One
comment
regarding
just
like
high-level
comment
regarding
organization
of
utils
and
then
using
those
new
classes
in
SFI
fact.
In
a
lot
of
cases,
if
there
is
something
like
a
geometric
factor,
that
is
a
standalone
you
Club
that
can
be
treated
as
a
function,
write
it
as
a
simple
function
in
me,
you
till
some,
where
oh
and
then
just
call
that,
from
whatever
classes
you
need
yeah,
that's
sort
of
the
easiest
way
to
those
things.
E
A
A
A
A
So
properties,
what
the
purpose
really
is
is
actually
bringing
in
strongly-typed
variables
into
Python
and
also
coercion
and
checking
and
validation
and
all
the
service.
So
a
strongly
typed
means
that,
like
we're
going
to
enforce
assumptions
on
variables.
D
B
D
D
D
A
A
D
D
D
A
D
C
A
A
Right
now
yeah,
yes,
so
we
serialized
the
class
as
well
yeah
yeah,
one
of
the
things
that
we
should
add
to
this
is
actually
serializing
the
version.
I've
done
that
in,
like
my
casing,
stuff,
I'm,
not
handy
because
then,
if
we
update
the
version
and
something
goes
awry,
we
can
figure
that
it
so,
but
for
now
I
mean
we
shouldn't
be
changing
too
many
of
these
things.
So
you
can
start
to
to
play
with
this
a
bit
so
gnosis.
D
A
D
D
A
Think
you
necessarily
want
to
use
it
in
that
case,
these
are
like
the
minimum
elements
required
to
set
up
the
class.
So
these
are
all
the
things
that
I
need
to
actually
set
up
everything
else
that
follows
so,
for
example,
I
need
H
to
build
my
cell
grad,
but
I
don't
have
like
the
celdrid
does
not
have
to
be
saved.
I.
D
D
A
So
I
actually
broke
some
stuff
today,
so
well.
I'll
have
to
go
fix
that,
but
the
validators,
so
what
they
do
they'll
actually
go
and
basically
check
all
of
your
assumptions
on
this
SOI.