►
From YouTube: NuPIC Sprint Planning - Mar 27, 2014
Description
There is a chance that this meeting might be cancelled because of a previous engagement running long. In that case, I will update the nupic-hackers mailing list with details for the next sprint.
A
A
A
Ok,
the
dev
tab
here
here
this
morning.
Ok,
this
is
only
open
new
pic
pull
requests,
so
these
guys
are
old.
The
utility
coder
is
mark.
This
scalar
add
safety
check
is
mark.
Clean
up
unused
code
is
Marcus,
I,
think
those
are
all
in
his
court
at
the
moment,
but
he
has
been
busy
so
I'm
not
going
to
continue
pressuring
on
pressuring
him
about
it.
A
Actually,
let's
look
at
pull
requests
in
the
github.
It's
a
little
of
that
stupid
core.
There's
new
pic
pull
requests,
alright,
so
yeah!
These
three
are
mark.
This
point,
Ian
created
and
I
started.
Looking
at,
but
I,
don't
know
how
to
write
tests
for
this.
So
I
like
somebody
to
help
right
test
for
this
Ian
wrote
the
code.
It's
a
really
really
simple
code
change,
but
we
need
a
Python
test
for
it.
A
So
this
might
be
a
good
chance
for
somebody
who
knows
Python,
especially
those
Python
test,
wants
to
understand
how
the
code
is
supposed
to
work.
I
think
this
isn't
a
spatial
pooler
yeah.
So
if
you
wanted
to
dive
into
the
Python
version
of
the
spatial
puller
there,
it
is
there
there's
a
so
I've
marked
this
as
help
wanted,
will
move
this
into
spread
19
we're
reviewing
as
she
goes.
A
I
guess,
I
should
start
from
the
beginning,
we're
reviewing
sprint
18,
it's
the
end
of
sprint
18
and
we're
starting
sprint
19,
so
I'm
reviewing
tickets
and
pull
requests
deciding
what's
moving
into
sprint,
18
I'm
going
to
go.
This
one
is
brit
19
and
I'm
asking
for
help
on
this.
One
and
all
we
really
want
is
a
unit
test
for
this.
This
is
a
part
of
a
broader
issue,
which
is,
if
someone
that
specifies
a
connected
percentage
of
one
hundred
percent,
they
are
not
guaranteed
to
get
one
hundred
percent
connected
permanence.
A
Very
simple
fix
for
this,
which
is
just
a
greater
than
equals
instead
of
a
less
than
or
equals
instead
of
a
less
than,
but
we
want
you
to
test
for
it.
There
is
also
a
corresponding,
so
I'm
going
to
move
this
into
is
right,
19
for
going
I'd
forget
no
one
is
assigned
to
this.
We
just
need
a
yo
test,
but
I
want
to
also
show
you
in
new
pic
or
there
is
a
corresponding
pull
request.
A
A
It's
got
to
help
want
it
on
it
and
down
here:
Jeff
you're,
not
late,
I'm
late,
how
she
was
I,
hi
men
I
already
jumped
in
so
I'm
just
I'm
reviewing
pull
requests
right
now:
okay,
okay,
turn
my
volume
down
a
little,
so
I
was
just
going
over
these
two
fixes
for
connected
permanence
Ian
created
one
for
the
spatial
polar
in
Python
and
I
created
one
for
the
special,
polar
and
c
plus
plus.
Both
of
them
are
not
done
because
they
required
tests
and
I'm
asking
for
help
because
I
don't
know
how
to
I.
A
Don't
know
enough
about
the
special
pool
to
write
the
test
in
Python.
There
already
are
tests
for
that
code.
That
code
flow
so
that
either
one
of
them
needs
to
be
adjusted
and
new
assertion
needs
to
be
put
in
or
a
new
test
case
needs
to
be
created.
So
it's
probably
something
pretty
simple.
This
could
be
an
easy
way
to
jump
into
the
spatial
pool
or
algorithm
and
in
the
c++
case,
a
new
pic
or
I
have
no
idea
what
I'm
doing
so.
B
B
A
Alright,
so
back
to
PRS,
I
I
moved
this
PR.
There
was
into
sprite
19
and
I'm
going
to
move
the
bug
the
bugs
already
in
the
spread
19.
So
it
has
an
Associated
issue
with
it,
so
those
are
getting
moved
up.
So
we're
still
on
the
build
process.
I've
already
moved
that
to
sprint.
19
David's
got
a
new
PR
for
that.
That's
what
we're
looking
at
the
his
is
brand
new
PR
I
think
this
was
this
morning
or
last
night
to
get
the
build
working
in
Newport
court
independently.
A
Ok
back
to
so
both
of
these
PRS
are
in
the
next
sprint
for
our
new,
pic
or
and
then
I
hadn't
quite
finished,
going
through
the
PRS
of
new
pic,
actually
I
hat.
So
these
bottom,
three,
like
I
was
saying,
are
all
marks
and
they're
all
kind
of
old
and
blocked
and
waiting
for
him
and
he's
been
busy
and
hasn't
had
time
to
update
them,
and
then
this
is
the
integration
PR
for
the
new
new
pic
or
built,
which
David
will
be
working
on.
A
Ok,
so
those
are
the
PRS
for
new
pic
and
urban
core
see
Darwin.
One
of
these
was
at
Linux
or
Darwin
how
to
have
an
open
PR
to
open
PRS
areas.
Linux
nuba
clinic
64,
the
python
externals.
You
have
a
couple
of
PRS
here,
they're
getting
a
bit
stale
and
I've
just
been
kind
of
triggering
some
conversation
here.
So
I've
asked
mark.
This
is
again
and
mark
score,
so,
like
I
said,
he's
busy.
A
There's
nobody
he's
screaming
for
this,
so
I'm
just
going
to
leave
it
open
for
the
moment
and
we'll
shove
that
into
19
and
see
if
he
has
a
chance
to
get
back
to
it.
Okay,
the
other
one
I
think
I
was
talking
to
Austin
about
recently,
so
he
has
to
apply
the
same
changes
to
new
pic
Darwin
64,
so
I'm
going
to
I'm
going
to
leave
this
I'm
going
to
leave
this
assigned
to
Austin
and
I
want
to
make
a
note
to
create
a
ticket
for
that.
A
A
Ok,
so
those
I
thought
I
would
just
do
PR
review
quickly.
First,
just
make
sure
we
don't
have
anything.
Ok,
that's
the
website,
nothing
tooling,
server!
Nothing
fluent
influence
server,
I've
been
working
on
some
tools
to
help
consolidate
these
issues,
so
at
some
point,
I'm
going
to
come
out
with
something
that
I
don't
have
to
flip
between
all
of
these
different
issue
trackers,
but
it's
something
that
deserves
a
bit
more
thought
than
just
throwing
something
together.
So
eventually,
this
will
be
a
little
smoother
all
right.
A
Moving
to
issues,
starting
with
new
pic
cores
for
18,
we've
only
got
one
closed
issue,
so
we
didn't
get
a
lot
of
work
done.
Well
we're
closed
this
sprint,
but
we
at
least
did
we
did
get
some
work
done
partially
closed.
David
made
progress
on
the
bill,
so
all
the
rest
of
the
the
issues
for
where
did
I
go
and
pull
requests.
Another
pill
all
the
rest
of
the
issues.
I
have
already
moved
into
sprint
19.
A
A
That's
what
these
two
are
David
and
several
of
us
are
still
having
conversations
about
new
directory
structures,
I'm
still
trying
to
keep
that
conversation
on
the
mailing
list,
and
there
is
also
a
wiki
page
for
that.
It's
on
the
new
pic
hackers
mailing
list-
and
this
is
kind
of
a
stretch
goal
for
this
print,
but
I
was
still
hoping
to
get
it
in
getting
C++
tests
running.
Actually
they
in
David's
build.
They
are
running
and
passing
and
Travis
already.
A
So
if
we
get
that
yeah,
this
was
just
a
bird
full
of
getting
David
stuff
emerging
yeah.
So
that
would
get
that
going,
which
is
great,
and
then
that
would
also
close
this
one
out,
they're
kind
of
redundant
but
oh
well
and
then
the
main
main
one
main
ticket
establish
independent,
build
process.
So
if
it
all
goes
well,
we
might
be
able
to
close
all
of
this
stuff
out-
or
at
least
you
know.
So
all
of
them
involving
the
independent
they'll
process
out,
is
coming
sprint.
That
would
be
wonderful.
A
A
Let's
see,
I
also
did
I
put
together
a
tutorial
on
a
sine
wave
prediction
with
new
pic,
and
one
of
the
things
I
wanted
to
do
is
programmatically,
run
swarms
and
use
the
resulting
models
within
one
script.
So
I
I
made
a
change.
It's
my
first
new
pic
change
to
this
warming
process
to
generate
a
model
parameter
could
be
used
immediately,
fixed
some
typos
and
we
did
end
up
removing
build
SH
and
clean,
build
zubat
I
updated
some
of
the
swarming
parameters
which
helped
some
of
our
other
users
that
were
working
with
sine
wave
experiments.
A
A
The
new
directory
structure
is
kind
of
a
sister
issue
for
the
new
bacoor
new
directory
structure.
That's
that
we're
talking
about
a
new
hackers
mailing
list.
The
documentation
I'm
not
sure,
really
sure
how
to
deal
with
that.
If
we're
kind
of
documented,
as
we
go
where
we've
got
like
I
said,
we've
got
a
wiki
with
where
we
have
our
current
state
and
a
proposed
state.
So
if
you
sort
of
have
a
long-term
plan
versus
a
short-term
plan,
so
I
think
the
wiki
page
is
sufficient
documentation
for
me.
A
If
we
get
that
if
we
go
to
people's
thoughts
put
in
this
in
the
right
place,
and
so
here's-
and
this
is
a
marks
PR
for
cleaning
up
this
code
again,
this
is
waiting
on
his
response
and
I'm,
not
pressuring
him
fazenda
he's
got
schoolwork.
Please
do
I,
have
belief
so
I'm
going
to
move
all
of
these
into
the
next
sprint
and
then
we'll
take
a
look.
I
think
there's
a
couple
others
in
here
more
than
a
couple:
let's
see
what
did
I
miss?
A
Oh
yeah,
so
Alan
was
going
to
work
on
updating
the
doctor
wiki
weird:
that's
I
need
to
have
I
had
an
offline
conversation
with
Alan
who's
worked
on
docker
with
new
pic
and
he
was
kind
of
going
to
be
taking
over
our
doctor,
io
new
pic
presence
and
I.
Don't
think
I'm
gonna
have
to
chip
double
check.
My
email
but
I,
don't
think
we're
going
to
need
our
docker
repository
anymore.
A
All
right,
this
one
is
trying
to
get
it,
so
we
can
remove
the
run
test
script
and
see
make,
or
so
we
can
create
a
seeming
test
target
that
runs
the
test
without
the
run
tests
bash
script,
the
I
imagine
David
might
take
that
on,
but
that's
probably
something
small
enough
that
anybody
with
a
little
seeming
experience,
could
do
so.
I
grabbed
tagged
out
with
help
wanted
that
gross
volunteered.
A
To
do
add
a
readme
to
spatial
pooler
example
that
Kevin
made
I
wanted
to
get
it's
a
nice
little
code
example
with
decent
inline
documentation,
but
I
wanted
to
just
throw
read
me
on
that
page.
That
describes
what's
happening
here.
What
is
the
tutorial
about,
so
he
was
going
to
do
that.
This
is
a
bug
that
Chetan
was
volunteered
to
work
on,
but
that's
another
ones
that
grow
said
he
might
be
interested
in.
We
chatted
with
him
on
IRC
about
that,
so
he
might
grab
that
as
well.
A
A
Please
jump
on
that.
Vagrant
structions
out
the
updated.
Is
that
one
we
already
talked
about
the
tsuba
ty
said
you
would
be
able
to
work
on
switching
to
these
c++
for
the
default
spatial
pooler
and
I
think
the
others.
We
talked
about
okay,
so
this
is
our
current
spread
for
new
new
pic
and
the
other
page
was
for
new
pic
or
okay.
So
that
concludes
our
two
primary
repositories.
I'm
going
to
move
on
to
sort
of
what
I've
been
calling
the
satellite
repositories
or
support
repositories.
A
Darwin
64
has
no
issues
when
x64,
I,
think
house
yeah
couple
issues,
mark
openness
and
Austin
was
wondering
why
we
even
want
to
do
this,
because
why
would
we
move
this
to
python
3
when
none
of
our
other
projects
are
Python
3,
which
is
valid
questions?
So
I
might
ask
mark
that
on
that
bug
the
removing
pill
from
the
repo
is
is
perfectly
fine.
I
think
I
think
the
main
repos
already
moved
to
pillow,
so
this
this
is
still
valid.
So
I'm
going
to
move
this
sprint.
19
should
be
a
pretty
easy
fix.
A
A
The
media
page
is
just
kind
of
a
list
of
videos,
I'd
like
to
provide
a
little
bit
more
organization,
get
the
more
important
videos
more
visible,
and
then
I've
still
got
this
issue
that
that
bugs
me
that
I
I'm
really
not
great
at
this
sort
of
work.
So
if
anybody
is
a
good
front,
end
person
who
wants
to
pick
this
up
and
I
don't
want
to
put
all
these
tickets
on
you
Jeff,
but
if
you're
interested
it's
there,
oh
yeah
I'm
happy
to
do
any
that
stuff.
A
A
A
19
yeah,
nothing
coming
up
there
fluent
I,
don't
think
had
well
actually
there's
several
issues
to
fluent.
This
is
fluid.
Is
that
are
one
of
our
sort
of
do
like
a
demo
application
using
accept
and
doing
word
sequences
pushing
word
sequences
through
new
pic
I.
Think
it's
a
really
interesting
app.
One
of
the
things
we'd
like
to
do
is
to
allow
the
API
or
the
actual
fluent
library
to
disable
enable
learning.
A
A
I
need
this
to
get
done
so
I'm
going
to
work
on
that
I.
Think
I
me
so
I'll
put
that
and
I'm
sort
of
chetan
his
as-built
IRAs
created
most
of
these,
so
I'm
kind
of
letting
him
managed
I,
don't
know.
If
anybody
wants
to
work
on
this
project,
anybody
feel
free
to
jump
in.
I
think
this
is
a
really
interesting
project,
and
even
if
you
don't
know
the
details
of
new
pic,
you
don't
want
to
jump
into.
You
know
a
c++
project.
A
A
A
good
point:
ok,
I
will
do
that.
I'm
gonna
have
to
wrap
this
up.
Pretty
quick,
because
I
know
there's
another
meeting
in
like
two
minutes
that
we're
supposed
to
be
at
so
jumping
ahead.
Wallboard,
I
don't
think
there's
anything
other
is,
but
these
these
are
sort
of
low
priority.
I've
got
some
longer-term
plants
for
wall
board
for
issues
which
I
was
hinting
at
earlier.
A
So
we
do
need
to
update
it
if
we're
going
to
keep
this,
but
you
might
have
another
idea
of
just
keeping
the
docker
image
on
docker
io
up
to
date,
so,
okay,
yeah
I,
think
that's
probably
a
wrap
I
have
a
little
bit
of
cleanup
to
do
which
I'll
do
before
I
end
today,
just
to
close
old
milestones
and
make
sure
all
the
all
the
tickets
are
properly
marked
and
assigned,
but
other
other
than
that
I
think
we
can
probably
wrap
this
up.
You
guys
have
any
have
any
comments
or
anything.