►
From YouTube: NuPIC Development Progress Review - Oct 31, 2014
Description
We'll review the road map at http://status.numenta.org/roadmap and talk about progress.
B
A
A
C
A
And
then
one
below
called
beta,
so
the
idea
being
hopefully
we'll
be
moving
to
a
release
process
at
some
point
in
the
future
and
I
wanted
to
line
that
up
so
that
we
were
sort
of
in
the
habit
of
collecting
feature
sets
and
drawing
a
line
somewhere
in
the
sand.
Some
point
in
the
future
so
we're
starting
with
alpha.
A
So
up
in
this
top
right,
I'm
going
to
click,
this
more
detail
button-
and
this
will
give
us
all
of
the
tickets
within
each
of
these
super
tickets
or
what
they're
called
initiatives
on
this
page.
So
we
have
one
big
initiatives
that
just
collects
a
bunch
of
general
build
improvements
that
we've
all
sort
of
agreed
need
to
be
done
at
some
point.
So
it
would
be
great
if
we
could
clean
this
up
and
get
this
done
within
the
Alpha
milestone
you
all.
A
You
might
also
know
there's
a
date
which
is
the
end
of
the
year
calendar
year.
That's
a
due
date
for
alpha
I,
don't
know
how
solid
that
is.
I,
just
kind
of
guessed
at
that.
So
that's
definitely
subject
to
change
and
up
at
this
up
in
the
top
right
says,
we
have
nine
out
of
67
tickets
currently
completed
so
there's
kind
of
a
progress
indicator
on
on
the
milestone
itself
and
then
each
one
of
the
initiatives
also
has
a
progress
indicator.
A
So
far,
so
we've
got
one
for
general,
build
improvements,
I'm
not
going
to
go
over
each
and
every
one
of
these.
But
you
can.
You
can
see
them
here
and
then
I
have
a
couple
of
kind
of
generic
catch-all
buckets
for
bug,
fixes
or
bugs
that
are
important
enough,
I
think
to
be
fixed
within
this
alpha
release
and
then
new
features
that
are
currently
either
being
worked
on
or
important
enough
to
be
included
in
this
release.
I,
don't
know
if
I'm
going
to
continue
doing
this,
but
I
wanted.
D
A
A
So
that's
still
a
initiative.
That's
ongoing!
Sorry!
Some
of
these
github
icons
aren't
showing
up.
This
is
a
scientist
coppery,
but
this
is
the
platform
annotate
independent
model
civilization.
This
is
also
a
phase
one
which
is
the
implementation
of
the
new
technique
and
deprecating
the
old
technique.
A
And
then
we
have
another
general
initiative
to
improve
our
unit
testing
framework
headed
by
utensil
song
and
he's
done
a
lot
of
work
on
this,
and
we
still
have
a
lot
more
work
to
do
on
it
so
I'm
over
beta,
except
to
say
that
the
phase
two,
the
TM
implementation
and
the
phase
two
of
the
civilization,
which
is
to
create
a
conversion
utility
and
remove
the
old
serialization.
Those
are
going
to
be
data
initiatives.
A
If
and
I
think
for
the
purpose
of
this
meeting,
I
would
like
to
focus
on
tasks
that
are
within
this
milestone.
There
are
some
other
tasks,
many
of
them
community-created
tasks
for
certain
things
that
people
want.
That
may
not
be
included
in
an
alpha.
Winning
are
these
milestones
but
may
still
get
worked
upon
and
completed
and
that's
fine,
but
for
the
purposes
of
our
planning
and
progress
review,
I
would
like
to
try
and
stick
to
looking
at
the
current
milestone,
we're
in
and
focusing
on
getting
that
done.
Okay.
So,
let's
move
to
our
waffle
board.
A
Star
issues
track
issue
board
at
the
moment
start
over
here
on
the
right.
So
these
are
our
I'm
just
looking
at
again
the
issues
that
are
within
alpha.
So
a
lot
of
this
is
going
to
be
a
PR
review.
There
are
a
couple
of
PRS
here:
are
ready
to
be
reviewed
and
are
just
sitting
waiting
for
review,
1
x,
mark,
that's
exposing
anomaly
parameters
into
swarming
and
then
another
two,
that's
a
fix
something
in
a
niche
function.
I,
don't
know
exactly
sure
what
this
is,
but
a
seal,
a
model,
the
net
function.
A
So
these
are
passing
the
build
anyway
and
they
just
need
to
be
reviewed
and
they've
been
around
for
a
while.
So
this
one
is
was
marked
as
ready.
26
days
ago,
the
anomaly
parameters
exposed
was
marked
as
ready.
Well,
it's
not
actually
yeah
it's
ready
17
days
ago,
18
days
ago.
So
these
are
things
that
are
kind
of
low-hanging
fruit.
We
could
get
these
merged
if
we
got
them
reviewed
and
they're,
both
community
PRS.
A
So
the
longer
they
sit,
the
worst
relationship
we
have
with
those
guys
so
there's
those
two
either
initially
I've,
just
tacked,
Scott
and
said:
hey,
if
you
don't
have
time
for
this,
let's
talk
about
who
should
be
reviewing
it.
So
we
can
talk
about
those
offline,
but
I'd
like
to
get
the
reviewed,
and
now
we.
D
A
Have
a
bunch
of
blocked
issues
most
of
these
well
first
few,
our
PRS,
so
it's
at
least
to
run
through
these
at
least
identify
why
they're
blocked
here's
one?
That's
a
encoders
inherit
more
from
the
encoder
class.
Another
one
by
Mark
and
the
issue
here
is
it
is
the
build,
is
failing.
So
this
is
in
marks
court,
although
he
doesn't
gonna
fix
it.
It's
tagged
this
with
Help
Wanted
hopeful,
hoping
someone
will
come
along
and
help
them
out.
So
this
is
an
open
issue
and
it's
just
sitting
there
not
building
so
there.
A
There
is
an
issue
with
that,
and
hopefully
somebody
might
take
some
interest
in
it.
The
next
one
is
adding
new
SP
compatibility
test.
This
is
nothing.
This
is
adding
a
test
that
fails
and
so
there's
sorry
about
the
awful
scrolling,
but
there's
another
issue
that
says
basically
fit
make
the
fix
that
will
make
the
test
pass
and
that's
being
worked
in
another
place.
So
I'm
not
too
concerned
with
this
issue.
A
Okay
so
and
Mark's
been
a
busy
lately.
I
have
not
seen
him
around
a
lot.
So
a
lot
of
these
things
that
are
depending
on
unmarked
might
still
just
have
to
sit
around
for
a
while
until
if
he
gets
some
time
to
work
on
things,
adding
the
test
for
decompose
ability
this.
This
is
the
related
to
the
the
unit
test.
A
I
believe
the
unit
test
failure
mark
added
that
I
was
talking
about,
so
it
is
currently
blocked
by
another
issue,
which
is
the
one
that
I
was
that
we
just
referred
to
so
again
marks
court,
and
this
was
a
a
bug
that
mark
brought
up
that
anomaly.
The
anomaly
temporal
anomalies
are
ignoring
unfulfilled
predictions
suit.
I
you
and
Mark
went
around
about
this
I'm,
not
sure
I
understand
the
issue,
but
the
result
of
it
is
that
it's
blocked
by
some
other
issue,
which
is
the
same
issue
just
talked
about.
A
So
there's
a
lot
of
things
leading
down
the
same
path
to
that
ends
in
whoops.
Where
is
it
now?
I
can't
find
it
this
other
issue,
which
was
add
test
for
decomposed
ability
so
again
we're
holding
on
mark
and,
and
these
issues
are
things
that
he
found
and
he
came
up
with
and
nothing
is
really
broken
for
us.
Everything
still
works
as
far
as
we're
concerned
for
the
needs
of
de
menta.
A
A
These
are
full
requests
that
are
being
worked
on,
but
they're
not
tagged
as
ready.
Yet
most
of
them
don't
have
builds
that
are
actually
passing.
This
one
has
been
around
for
a
very
long
time.
I
won't
lead,
not
September,
13
I
thought
it
was
a
lot
around
longer
than
that
and
it
is
still
sitting
in
marks
court.
A
The
swig
issue,
pull
request
is
still
open.
I
think
this
is
an
important
one
to
work
on,
but
I
don't
know
what
the
status
of
it
is
again.
Mark's
been
working
on
it
and
he's
been
m.I.a
for
a
while,
so
we'll
have
to
catch
catch
up
with
him
when
he
gets
back
mark
if
you're
watching
we'd
love
to
catch
up
with
you,
there's
also
this
PR
open
to
close
out
the
c++
switch
on
nucca
core,
and
this
just
got
a
little
comment.
A
Ation
today,
so
Scott
and
and
and
Austin
we're
talking
about
switching
out
Libya
amal
cpp
with
just
live
channel
instead,
so
Scott,
you
said
you
might
try
and
do
that.
That
would
be
awesome.
I
would
love
to
get
this
merge
there.
A
This
movie,
that's
up
in
the
air
with
one
of
you
guys
update
the
ticket
please.
So
we
know
it's
there's
not
like
a
solution
being
created
at
the
moment.
A
A
Great,
ok
speaking
up
code
is
always
good.
So
the
end
the
anomaly
call
likelihood
PR
has
been
around
for
a
while
and
again
it's
back
in
barre
chord.
A
Other
than
those
we've
got
a
bunch
of
tickets
on
sitting
in
alpha
ready
to
be
worked
upon.
I
think
those
are
the
main
things
in
it
that
I
wanted
to
go
over.
I
wanted
to
make
sure
everybody
had
some
visibility
over
all
the
PRS,
because
they're
there
are
quite
a
few
open,
pr's
right
now,
and
a
lot
of
them
have
been
open
no
a
month
two
weeks,
so
I
just
hate
sitting
around
for
that
loan,
but
otherwise
what?
If
anything,
does
anyone
else
have
to
share
while
we're
all
here
in
the
same
virtual
room.
D
D
A
Very
night,
so
look
good
on
you
any
feedback
on
the
road
map
I.
A
One
thing
I'm
concerned
about
is
not
going
over
what's
in
the
cool
mile
tone
in
these
meetings
and
though
that
might
leave
a
few
things
off
to
the
side
that
don't
get
discussed,
but
I
would
like
to
get
into
the
habit
of
focusing
on
unless
in
this
the
milestone
we're
currently
in
so
we
can
get
that
done
and
if
there
are
things
that
aren't
in
that
milestone,
that's
a
discussion.
We
should
have
on
the
mailing
list
about
whether
it
should
be
in
the
mouse
turn
it
off,
but
I'm
open
to
any
discussion
about
that
process.
D
It
seems
like
a
few
of
the
milestones.
Are
you
know,
like
the
general
build
improvements?
Thing
is
kind
of
a
grand
back
or
a
whole
bunch
of
stuff.
It's
not
really
a
technique
define
milestone
per
se.
D
Yeah,
it
seems
like
some
stuff
in
there
could
be
really
important
in
others
can
be
less
important.
It's
not
like
there's
a
particular
goal
that
we're
shooting
for.
We
could
be
making
build
improvement
for
the
next
five
years
because
you,
but
that's
yeah.
That's
true.
I
dream
around
the
end.
December
hostility
on
I.