►
From YouTube: NuPIC Sprint Planning - Aug 22, 2014
Description
Where we plan Sprint 29: http://status.numenta.org/issues.html#milestone=Sprint+29
A
So
these
are
the
closed,
pull
requests
from
sprint
28,
which
is
a
sprint
we're
closing
out
right.
Now,
I'm
going
to
go
over
some
of
the
main
essential
repos.
Just
a
few
of
these,
like
nuke
core,
for
example,
we
added
back
a
compile
flag
that
shows
errors
on
unused
function.
Parameters
mark
did
that
austin
added
a
sequels
plus
only
region
example
and
utensil
fixed
a
build.
B
A
Jayden
did
some
cleanup
with
renaming
and
temporal
memory
and
added
errors
to
the
hot
gym
example.
Some
of
the
other
things
if
you've
noticed
we've
got
a
new
repo,
which
is
the
java
port.
So
there's
I've
been
working
with
david
ray
who's,
the
the
original
author
of
the
java
port
to
get
that
that
repository
into
a
good
state
for
reporting
on
all
and
testing
and
building
and
all
that
stuff,
so
a
little
bit
more
work
to
do
there,
but
mostly
it's
just
david
ray
continuing
to
work
on
algorithm
implementation.
There.
A
The
other
stuff,
is
just
kind
of
tooling
improvements.
Content
updates
on
nementa.org,
nothing
extremely
important.
So
those
are
the
closed
issues.
Here
are
the
open
pr's
that
are
currently
in
the
sprint,
so
I
want
to
do
a
quick
review
of
those.
Most
of
these
are
still
just
still
under
work
and
will
be
moved
to
the
next
sprint,
like
the
stuff
that
jim
bridgewater
is
working
on.
Mark
mark
is
continuing,
he's
kind
of
back
from
sabbatical
and
continuing
on
the
anomaly
modular
pr.
A
B
A
A
A
We
had
a
short
discussion
on
the
mailing
list
about
a
default
configuration
value
for
the
sp's
wraparound
parameter,
so
jim
bridgewater
is
forging
ahead
with
that
change.
That's
what
these
are
utensil
and
another
guy.
I
think
his
name
is
richard
or
robert
crowder,
richard
crowder
a
little
bit
more
attention
for
the
windows
support,
so
they
are
both
sort
of
now
and
then
actively
contributing
to
that
that
build
is
passing
and
they've
got
an
app
conveyor,
build
that's
trying
to
run
on
windows.
A
So
that's
an
ongoing
nipit
core
enhancement
for
the
build.
It's
got
some
test
refactoring
and
there's
that
other
one
I
mentioned.
That's
the
component
complement
to
that
one,
and
I
haven't
heard
back
from
utensil
about
the
c
plus
plus
tests.
I
did
send
him
an
email
asking
him
how
he
thinks
we
should
move
ahead
with
that,
so
that's
still
kind
of
on
hold,
so
those
are
the
currently
open
pr's.
I'm.
A
A
So
open
issues
in
sprint,
28,
let's
go
buy
repo
here,
nupit
core
the
wrap
around
parameter.
Like
I
mentioned,
that's
the
issue
for
that
now
this
spatial
pooler
behavior
deviates
from
the
python
implementation.
I
do
believe
he
has
a
pr
for
that
and
it's
a
test.
I
think.
No,
that's
not
it.
There
was.
There
was
one
pr
scott
that
I
that
I
commented
on
that
jim
added.
A
I
think
it
was
on
in
new
pic,
but
jim
added
a
test
that
failed
and
I
think
it
seemed
to
be
a
legitimate
test
but
yeah
the
sp
permanent
test,
and
I
want
to
know
what
is
your
take
on
moving
forward
with
this,
because
I
think
the
test
is
valid
and
it
and
it
uncovers
a
condition
that
we
need
to
fix.
Is
that
correct.
A
C
A
A
A
A
A
A
A
So
I
at
this
point
I
need
to
break
it
up
into
different
tickets
and
try
and
figure
out
what
the
individual
issues
people
are
having
are.
So
that's
on
me,
some
more
spatial
pooling
stuff
that
jim
opened
language,
independent,
checkpoint
and
serialization.
So
yeah,
quick,
quick
discussion
on
this
I
sort
of
asked
is
this:
was
this
for
an
investigation
and
if
the
investigation
is
done,
should
we
close
it
and
if
so,
what?
What
is
our
next
action.
C
A
It's
definitely
past
the
time
so
yeah
it's
it's.
I
just
need
to
close
it,
so
nobody
said
minus
one
on
it:
yeah
yeah!
So
here
I
mentioned
it's
been
over
three
days
now
and
I'm
asking
what
are
our
next
actions
for
this
right,
so
I
think
we
can
assume
that
we're
going
to
move
to
c
plus
plus
11.,
given
that
assumption,
I
think
we
should
close
this
ticket
and
create
a
ticket
for
serialization
using
the
best
option
for
c
plus
11.,
okay,
okay,
so
I'm
I'm
gonna
go
ahead
and
close.
It.
A
C
A
A
C
C
A
A
So
we're
getting
some
good
documentation
from
some
people
in
the
community.
So
that's
that's
good!
This.
This
guy
sylvain
is
working
on
some
docks.
He
said
he's
going
to
work
on
cla
model,
so
that's
great
jeff
you're
still
on
tap
to
improve
the
wiki
dock
for
encoders,
which
jayden
did
a
bit
of
so
you
might
not
have
a
lot
of
work
to
do
all
right,
renaming
newpick
to
new
python.
E
A
Most
most
likely,
but
I
don't
think
we've
quite
decided
what
we're
going
to
do.
I
haven't
seen
any
responses
from
the
community
since
your
last
email,
I
was
hoping
someone
would
jump
in
and
say
sure,
here's
I
started
the
wiki
fax
for
jeff
and
they
would
start
writing
questions
in
there.
So
I'm
hoping
that
that
happens.
If
not,
I
could
I
could
start
an
empty
document
and
kind
of
poke
them
and
try
and
get
them
to
to
fill
that
in
yeah.
Other
ideas-
that's
fine,
too
yeah
yeah.
E
B
A
I
mean
because
jeff
is
the
one
that
needs
to
take
a
look
at
that
and
and
look
at
the
changes
and
because
it's
in
la
tech-
and
it's
it's
just
really
hard
for
him
to
review
any
of
the
changes
like
I
could
create
a
document
for
them,
but
it
wouldn't
show
a
diff.
So
I
don't
know,
I
think,
that's
sort
of
a
lost
cause
that
new
pick
documents.
A
I
had
high
hopes
for
it
at
the
beginning,
but
I
think,
but
we
do
need
to
just
figure
out
a
way
for
for
jeff,
to
get
feedback
or
for
at
least
for
him
to
share
his
his
research
process
a
little
bit
with
the
community
because
they're
they're
they're
hungry
for
it
you
know
yeah.
So
so
I'm
gonna
wait
and
see
what
happens
on
the
mailing
list
there
and
I'm
sure
some
action
will
come
out
of
it
yeah.
A
A
So
this
time
I
did
not
do
that.
I
left
I
I
removed
a
bunch
of
where
am
I
there
we
go.
I
I
removed
a
whole
bunch
of
those
help
wanted
tickets.
Most
of
them
were
in
like
cerebro,
2
or
tooling,
or
you
know
newpic.org,
or
something
like
that.
So
I
took
all
those
out
because
it
was.
It
was
cluttering
everything
up
so
now
we
just
got
these
four
tickets
and
four
different
projects
and
we'll
bump
those
up
to
sprint
29.
A
A
A
Okay,
so
we've
got
41
issues,
which
is
pretty
pretty
heavy.
In
my
opinion,
I
may
go
through
here.
Some
of
these
were
already
in
like
austin's
out
today
he
told
me
he
was
going
to
work
on
these
three
issues.
Some
of
them
are
still
unassigned.
Some
of
them
are
marked
with
help
wanted
or
unassigned,
and
those
are
issues
that
I
think
I
would
like
to
get
done,
but
I
don't
know
who's
going
to
do
them,
so
those
are
up
for
grabs
if
anybody
wants
to
work
on
them.
A
Okay,
okay,
so
let
me
just
make
sure
yeah,
so
there's
nothing
in
sprint
28.
So
this
is
our
sprint
29
at
this
point,
and
I
think
we've
hit
all
of
these
issues
one
way
or
another.
Most
of
them
don't
need
a
lot
of
discussion.
So,
okay,
anything
else
from
from
anybody
that
you
want
to
talk
about
in
the
sprint
planning
meeting
before
we
move
ahead.