►
From YouTube: NuPIC Sprint Planning - May 22, 2014
Description
This is scheduled a day earlier than usual.
A
A
A
A
A
A
There's
the
associated
ticket
austin
took
on
this
nuked
core
he's
he's
out
today,
so
he
was
planning
on
trying
to
get
a
building
on
solaris.
I
don't
know
what
the
status
of
this
is,
but
I
think
we
might
as
well
keep
it
in
case.
He
finds
time
to
do
that.
He
seemed
to
be
very
interested
in
that
helping
the
guys
from
fujitsu
get
new
running
on
their
big
servers,
so
here's
another
ticket
on
starting
input
dimensions
that
is
currently
chaitan's
ticket.
A
So
I
still
have
this
ticket
on
defining
the
public
api.
I
think
there
is
a
wiki
page
for
that.
I'm
not
sure
how
much
it's
been
updated
yeah
here.
It
is
so
not
not
a
whole
lot
of
of
stuff.
Nothing,
nothing
really
down
here,
except
places
to
start
looking,
but
we
wanted.
I
wanted
to
try
and
define
just
in
in
a
document
what
needs
to
be
defined
as
the
api.
So
then
we
can
make
sure
that
those
things
are
documented
and
that
they
have
tests
written
for
them.
A
A
A
A
A
Let's
see,
okay,
that
seems
like
a
valid
issue
seems
like
an
easy
one
to
fix.
I
don't
know
you
could
probably
just
fix
that
or
somebody
so
we'll
leave
that
up.
That's
that's!
I
got
it.
Help
wanted
a
newbie,
so
it's
an
easy
thing
to
do.
We
will
leave
it
around
and
then
the
unit
tests
thing.
I
got
a
little
bit
of
support
on
this
on
the
mailing
list.
A
A
A
I
have
been
working
on
the
odd
gem
anomaly
sample,
but
it
uses
the
anomaly
likelihood
algorithm
in
new
pic,
so
I
don't
want
to
merge
that
until
the
other
is
merged
in,
but
there
is
already
a
video,
it's
just
not
published
yet
right
so
more.
I
sorry.
I
forgot
your
name
but
more
from
portland
he's
working
on
this
unit
test
cleanup.
A
He
was
going
to
submit
a
pr
on
this
hasn't
happened
yet
so
I'm
just
going
to
leave
it
around.
Hopefully,
he
works
on
that
he's
on
irc
a
lot,
so
I
can
bug
him.
There
run
swarm
fail
on
ubuntu.
I
do
not
remember
what
the
status
of
this
was.
Let's
see
related
to
888,
oh,
I
think
this
was
this
had
to
do
with
the
misleading
error
and
we
could
not
really
identify
exactly
what
was
wrong.
A
So
hopefully,
once
the
swarm
error
message,
vr
is
merged
in
we'll
get
a
better
idea
of
what's
wrong
here.
So
the
there
is
no
job
result,
so
something
something
is
either
wrong
with
the
input
or
the
swarm
description,
most
likely
so
I'll
leave
that
open.
Hopefully,
I
can
follow
up
on
that
after
we
get
better
error
messages
in.
A
A
Yeah,
so
this
is
also
a
valid
issue
with
swarms.
I'm
going
to
sign
that
to
me.
That's
I'm.
I've
worked
in
that
area,
so
I
should
take
that.
I
know
what
he's
talking
about.
Solaris
is
still
in
austin's
court,
so
this
is
a
ticket
for
new,
because
this
is
the
sister
ticket
for
the
core.
This
error
thing
that's
the
pr
I
referred
to
before.
B
The
map,
potential
and
and
dimensional
stuff
that
was
work
that
trayton
did
to
support
arbitrary
numbers
of
dimensions
in
the
spatial
pooler,
but
that
pr
is
is
waiting
on
it,
we'll
see,
plus
plus
one,
so
they
can
be
merged
together,
and
I
think
he
is
tentatively
planning
on
doing
it.
This
next
spring.
A
A
Okay,
this
run
swarm,
produces
model
params
with
non-temporal
model
and
also
with
tp
enable
is
true,
that's
just
a
I
believe
again.
This
is
a
confliction
just
in
the
output,
but
I'd
like
to
find
some
time
to
dig
into
it
and
into
this
swarm
process
and
and
see
exactly
what's
going
on
there
if
there
are
just
defaults
that
always
show
up
and
some
override
the
others
I'd
like
to
get
the
the
model
crams
that
come
out
of
this
form
to
be
a
little
less
confusing.
A
So
if
there's
conflicting
details
in
there,
we
should
probably
fix
it,
and
here
is
the
intex
developer,
build
thing,
so
this
is
sort
of
become
I'd
like
to
maybe
change
the
label
of
this.
What
we
need
is
a
feature
for
developers
that
basically
does
what
intex
developer
build
used
to
do
now,
as
we've
discussed
before
the
once,
we
get
new
big
pip
installable.
A
So
there's
a
workaround
with
sim
links
in
the
release
directory
which
I've
I've
been
doing
as
well
now,
but
it's
a
pain
in
the
ass,
so
we
should
leave
this
around
and
hopefully
somebody
will
work
on
it.
Actually,
I'm
going
to
keep
it
open
and
probably
add
some
clarification
here
to
exactly
what
this
means
and
probably
change
the
title
to
be
more
descriptive
about
what
this
is
more
of
a
feature
request
or
a
feature
replacement
of
something
that
was
removed.
A
A
A
A
And
fill
the
old
sprint
and
we're
experimenting
23.,
there's
a
bunch
of
satellite
projects.
I
don't
really
have
a
good
view
for
these
yet,
but
I
do
sort
of
have
a
command
line
tool
that
I
use
so
this
this
is.
These
are
all
of
the
other
projects,
the
tooling
server
darwin
and
linux
64
and
the
wall
board.
These
are
the
only
things
that
have
issues
that
are
currently
in
sprint
23..
A
So
I'm
not
going
to
go
over
all
of
these
and
and
github
ui,
just
because
I'll
be
switching
between
a
bunch
of
tabs,
but
all
of
the
darwin
linux,
64
stuff
is
assigned
to
austin.
None
of
them
are
extremely
important
or
critical,
but
they're
all
stuff.
That
does,
I
believe,
need
to
be
done
at
some
point.
A
This
is
an
interesting
one
for
for
the
tooling
server
anytime,
there's
a
pr
that
merges
a
new
core
to
master.
So
when
you
pick
core
gets
updated,
it
would
be
kind
of
cool
if
automatically
a
pr
was
created
for
new
pic
that
updates
to
the
new
core
shaw
and
just
sits
there,
so
that
the
build
can
run
against
it.
So
we
can
get
an
indication
that
everything
still
works
properly.
A
Then
it's
up
to
our
discretion,
whether
we
want
to
merge
that
and
update,
maybe
record
a
point
to
the
new
or
excuse
me
to
update
nuke
to
point
to
the
new
new
core
shock.
So
I
kind
of
like
that
idea.
So
I'm
going
to
keep
that
around
and
try
and
work
on
it
and
then
the
the
wall
board
thing
there's
a
couple
of
a
couple
of
things
here:
jeff
is
assigned
to
one
which
is
just
a
nice
to
have
thing
that
the
developer
tab
be
its
own
tab
or
its
own
page.
A
Excuse
me,
because
that
makes
a
lot
of
http
calls,
and
sometimes
it's
not
used,
so
we
do
have
a
rate
limit
that
I've
exceeded
occasionally
having
the
wall
board
up
and
then
I
would
like
a
page
on
there
and
I
have.
I
have
the
back
end
functionality
in
place
for
this.
I
just
need
a
ui
to
display
all
the
issues
across
inventory
repos,
because
it's
kind
of
a
pain
to
go
between.
A
I
don't
know
eight
or
ten
different
repositories
that
we
have
just
to
see
what
issues
are
currently
open
in
the
current
sprint,
so
I've
I've
got
a
command
line
tool
that
does
this
and
which,
which
is
nice
for
me,
but
it's
it
would
be
nice
to
have
a
on
our
wall
board
somewhere
and
that's
basically
it.
I
believe
that
was
a
fast
sprint
planning
meeting,
but
I
don't
think
I
have
anything
else.