►
From YouTube: NuPIC Sprint Planning - Feb 28, 2014
Description
Where we plan NuPIC work for Sprint 17.
A
Okay,
we
are
on
the
air,
so
welcome
to
sprint
planning.
This
is
going
to
be
for
sprint
17
over
the
next
two
weeks,
I'm
going
to
share
my
screen.
Here
we
go
starting
off
with
the
review
of
the
poor
extraction.
Plan,
went
down
to
step,
1
drew
stolen,
so
here
are
the
tasks
that
have
been
completed
and
we're
currently
on.
A
So
the
emphasis
for
this
friend
is
going
to
be
to
get
new,
pic
or
building
itself
independently,
with
tests
running
and
see
I
then
some
subtasks
to
implement
new
directory
structures,
and
hopefully
you
can
switch
over
new
pic
to
call
into
new
before
to
execute
that
build.
So
that's
the
main
emphasis
once
once
we
get
past
that
we
can
move
on
to
a
bunch
of
parallel
work
and
step
2
to
prepare
for
any
before
release.
So
hopefully
I
can
get
some
more
people
involved.
A
That
can
work
on
things
and
simultaneously
so
I'm
going
to
do
a
pull
request
view
for
new
pic
and
do
before.
First,
so
we
get
to
see
what
the
status
is
starting
from
the
oldest,
we
have
a
utility
encoder
from
Martha.
Apparently,
the
build
is
not
passing
so
I
think
it's
uncommon
to
try
and
figure
out
why
that's
working
before
we
read
rest
that
this
scalar
and
safety
checks
is
also
in
the
same
state
and
we've
also
had
some
discussion.
This
was
this
clean
up.
A
Unused
code
and
CLA
model
used
to
be
a
ticket
called
remove
reconstruction
from
the
CLA
model,
and
we
had
some
discussion
on
that
ticket
where
I
I
closed
it
and
then
changed
it
and
be
emphasized
in
the
opened
it.
So
this
is
about
just
cleaning
up
unused
code,
except
for
reconstruction,
which
is
now
covered
in
another
discussion
on
the
mailing
list,
I'm
hoping
he
and
will
start
up,
because
I
think
he
was
the
one
that
was
against
removing
the
reconstruction
code.
A
So
that
is
in
the
discussion
phase,
but
this
is
just
for
removing
some
other
opps.
They
couldn't
see
the
model
that
the
art
needs.
Another
update
from
mark
to
revert
the
removal
of
the
reconstruction
code,
this
other
PRS
by
en
which
just
fixes
the
bug
a
buffer,
an
edge
case
where
initial
connected
percent
is
one
percent.
So
there's
a
ticket
for
that.
I
think
it's
just
awaiting
review
I
think
he
had
to
add.
A
Right,
there's
a
unit
test,
so
we're
waiting
for
the
end
two
ready
go
to
test
for
that.
That's
right,
let's
jump
over
to
new
pic
or
PRS
so
David
is,
is
removing
the
old
build
system.
So
there's
a
there's,
a
PR
for
that
and
Scott
you
created
this
PR
to
remove
or
to
make
a
virtual
destruct
ER
and
the
same
work
is
done
in
this
bottom
PR,
which
is
a
squash
PR
that
contains
a
bunch
of
stuff
that
Harvard
in
quite
a
while
ago.
A
A
B
A
Okay,
so
okay,
two
issues
now
so
this
is
the
remaining
issues
in
sprint:
16,
I'm
just
going
to
run
through
and
make
sure
that
they
all
make
sense
to
be
moved
into
sprint.
17
we've
got
the
environment
variable
review,
which
I
think
is
important.
The
discussion
about
what
to
do
with
your
nose
reconstruction
code
or
just
only
being
stressed
from
the
mailing
list.
This
ticket
was
about
the
ER
that
I
just
talked
about
that
mark
has
opened.
A
This
is
another
ticket
I
created
for
Ian's
PR
about
the
bug
he
found,
and
this
is
the
pr
itself
a
lone
star.
I
forgot
his
name.
This
is
kevin.
Yes,
he
is
working
on
a
tutorial
for
new
pic,
so
that's
still
ongoing
that.
What's
the
status
that
tsumetai,
it
seems
like
it's
looking
like
it's
going
pretty
well
yeah.
B
A
This
bottom
PR
matches
up
with
this
ticket
the
compose
directory
structure
for
new
pick.
A
new
Bakura
will
be
a
part
of
I,
think
David's
work
for
creating
them
to
build
and
a
tiny,
pic
or-
and
thus
implementation
saw
all
this
stuff
looks
like
it
should
be,
and
move
directly
into
this
print.
17
salt
looks
like
decent
work,
so,
let's
close
this
milestone
after
now
that
I've
moved
it
all
ended,
yellow
so
I
should
probably
a
quick
look
for
clothes
tickets,
so
we
could
get
a
good
amount
of
work
done.
I.
A
Okay
before
we
move
on
I'm
going
to
do
the
same
thing
going
before
spring
16,
the
I've
marked
a
couple
of
these
is
important.
So
we
know
these
are
the
ones
that
I
really
want
to
get
done.
The
spread
read
the
new
build
process,
and
that
includes
the
new
directory
structure
that
can
be
involved
with
that.
So,
there's
probably
just
going
to
be
one
PR
for
these
two
tickets.
I.
Imagine
this
squash
everything
PR!
A
We
talked
about
I'm,
trying
to
merge
master
of
I've
a
PR
open
against
that
VR
to
merge
master
into
it,
because
I
want
to
see
what
Travis
says
it
looks
like
Brad
Smith
hung
up
on
it,
so
that
will
continue.
If
we
could
get
these
top
two
done,
we
can
get
tests
running
and
and
build
it
NCI.
So
as
soon
as
it
builds
up,
I
assume
this
building
see.
A
That
was
a
really
simple
thing
you
working
on
see
make.
It
was
one
of
the
compiler
issues
for
sea
lion
thing:
ok,
let's
close
16
to
17
again
going
back
to
new
pic
now,
so
I'm
leave
everything.
There
wasn't
anything
extra
in
here,
it's
just
the
tickets
that
I've
moved
in.
So
this
is
our
workload
for
this
coming
sprint
and
say
the
the
most
important
work
I
believe
is
going
to
be
in
New
kapoor,
and
these
are
the
ones
that
mark
is
important.
A
B
A
The
pr
so
the
clothes
on
ok,
thank
you
just
for
anyone
watching
I
scheduled
to
meet
up
for
march
14th,
where
Jeff
is
going
to
talk
about
sensorimotor,
an
integration
and
the
CLI.
So
with
this
newest
and
thinking
about
this.
So
this
should
be
a
really
interesting
talk.
I
will
also
be
live
streaming.
It
and
reporting
it
with
better
audio.
A
This
isn't
part
very
much
in
in
response
to
people
complaining
about
the
quality
of
the
recording
and
at
the
last
hackathon,
where
you
talk
about
sensory,
lower
integration,
so
there
should
be
a
much
higher
quality,
so
that
should
be
fun,
we'll
be
in
san
jose
7
p.m.
friday
march
14th,
there's
only
50
slots
available,
so
RSVP.
If
you're
interested-
and
that's
it's
pretty
much
all
that
I
have
this
point-
is.
A
Gonna
be
a
bit
different,
so
he's
going
to
be
incorporating
some
of
his
new
thoughts
about
layer
for
sort
sort
of
what
you
talked
about
recently
at
their
last
engineering
meeting
yeah.
So
it
is
going
to
be
different
enough,
but
I
think
it
would
be
good
to
have
a
complete
new
reporting
of
it
other
than
that.
Can
we
let's
do
a
quick
process
review
as
we
we
did
have
a
little
bit
of
confusion
at
the
Times
about
our
process
has
been
so
I've
been
a
bit
of
a
kind
of
strict
about
enforcing.
A
So
if
I
see
a
PR
that
does
not
have
a
ticket
attached
to
it,
what
I've
been
doing
recently
is
creating
addicted
updating
the
pr2
references,
and
it's
been
at
least
one
case
where
there's
been
a
lot
of
discussion
on
a
PR
that
I
thought
shouldn't
be
in
a
PR.
It
should
have
been
discussed
before
the
PR,
but
there
was
just
some
confusion
about
what's
happening
in
the
PR.
It
was
also
an
old
PR.
That
kind
of
was
created
at
the
same
time.
A
This
process
has
been
created
so
just
to
review
this,
and
if
you
want
to
make
it
change
to
the
code,
a
new
pic,
if
it's
not
just
a
simple
bug
fix,
it
should
be
discussed
on
the
mailing
list
and
the
fits
if
it's
going
to
affect
out
rhythmically
how
something
works
probably
discuss.
If
it's
just
a
an
implementation
change.
Definitely
we
could
hackers
mailing
list,
and
then
we
should
come
to
some
consensus.
A
You
can
always
argue
in
code
by
making
code,
changes
and
I'm
pushing
them
to
a
remote
branch
and
that's
easily
comparable
to
the
master
branch.
So
you
can
always
do
that
and
that
could
turn
into
the
actual
PR.
So
there's
you
don't
want
to
create
a
PR
until
it
has
been
discussed
and
an
issue
has
been
created.
So
we
want
to
track
the
issues
that
are
being
observed
in
an
issue
on
github
issues
and
the
discussion
of
the
solution
to
that
problem.
A
A
B
A
Hey
well,
this
has
been
a
very
easy
sprint
planning
session.
So
we
know
the
important
work
needs
to
get
done
and
I
want
to
be
passed
to
the
sprint.
If
we
get
everything
done,
we
should
be
able
to
open
up
some
work
to
a
lot
of
other
people
that
doesn't
associated
directly
with
builds
and
see
Mike
yeah.