►
From YouTube: NuPIC Sprint Planning - June 20, 2014
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Remind
me
hello,
a
new
pic,
so
broadcasting
now
I
was
just
going
over
closed
issues
from
sprint.
24.
We
had
a
few
minor
issues
in
new
pic
or
mostly
just
clean
up.
Nothing.
Major
and
new.
Pic
we've
got
a
new
to
New,
encoders,
I,
believe
geospatial
encoder
and
a
coordinate
encoder,
so
that's
cool.
Hopefully
somebody
tries
some
things
out
with
those.
It's
a
looks
like
from
internal
demonstrations.
Those
seem
to
be
working
rather
well.
A
A
A
I'm
gonna.
This
is
the
tooling
server.
So
there
was
some
work
on
the
tooling
server.
Utensils
has
been
doing
a
lot
of
work
on
the
tooling
server
with
me,
which
has
been
great,
so
he's
got
a
there
was
a
status
in
github.
Well,
there
was
a
conditioning
github
where,
if
there
was
a
PR,
but
it
was
not
merge
about
and
we
posted
a
status
that
said,
the
status
was
good.
It
looked
like
it
was
good
to
merge.
A
It
wasn't
quite
evidence
that
it
was
not
mirja
below
he
utensil
worked
on
adding
a
status
that
would
post
that
it
was
not
good
to
merge
because
it
was
just
now
Virgil
I
think
he's
still
working
on
a
few
aspects
of
that.
Nothing
else.
Major
I
did
investigate
trying
to
see
if
we
can
deploy
our
tooling
server
on
Heroku,
which
would
be
a
little
bit
better
for
the
community
since
it's
well,
it's
free
and
it's
easier
to
collaborate,
he's
really
easy
to
deploy.
A
You
just
pull
to
heroku
remote
branch,
but
it's
was
problematic,
so
I
discussed
why
and
that
ticket,
but
I'm
going
to
give
that
out.
For
now,
the
tooling
server
needs
a
bit
of
a
free
architecture
before
we
can
do
something
like
that.
So
that
is
the
work
that
was
done
on
the
sprint,
and
now
we
are
here
on
current
issues.
I
already
have
some
issues
planned
for
spread,
25
things
that
have
come
up
that
I
just
pushed
on
this
for
25.
A
This
status,
this
board
we're
looking
at
here
with
the
issues
as
part
of
the
wall
board,
so
I
have
a
few
things.
I
want
to
update
on
it.
Those
are
just
kind
of
my
own
administrative
tasks.
Sprinter
is
also
a
part
of
that.
That's
an
internal
project
that
I
use
to
support
this
issues
page
on
new
pic
are
there's
an
issue
as
that
Chayton
created
to
extend
spatial
polar
support
and
in
dimensional
topology
and
there's
tickets.
A
A
new
pic
and
new
record
for
that
and
I've
also
got
a
plan
to
configure
a
code
scan
tool
for
both
new
pic
and
new
pic
or
so
that's
currently
on
the
books
for
sprint,
25,
so
back
to
sprint
24,
which
is
the
sprint
we're
closing
out.
Let's
look
at
open
pull
requests
and
you
guys
I'll
see
my
screen.
Okay,
it
looks
like.
B
A
It's
awesome:
how
did
that
happen?
Yeah,
that's
odd!
Okay,
there
we
go
all
right,
let
speak
up
if
it
if
it
goes
off
again.
Okay,
so
let
me
just
look
at
new
pic
or
first
so
there's
new
tensile
is
working
on
this
pull
request,
which
I
believe
is
in
a
merger,
will
state
right
now
it's
the
one
to
move
towards
more
windows
friendly,
build,
it's
not
everything
that
needs
to
get
done
to
support
windows,
but
its
movement
in
that
direction.
I
believe
this
is
passing
all
the
others.
A
You
know,
there's
not
a
whole
lot
of
validation
going
on
in
the
nuclear
core
build
so
I
have
asked
mark
and
David
to
take
a
look
at
this
because
it's
mostly
see
make
changes
and
let
me
just
assign
that
I'm
going
to
sign
it
to
mark.
Why
not
for
review
so
there's
there's
that
for
new
pic
or
open
pull
requests
for
new
pic
mark
has
a
this
anomaly
modular
pull
request
which
I
can't
remove
its
past
or
not.
A
A
Build
I've,
seen
a
lot
of
air
builds
lately
yeah,
it
looks
like
just
the
windows:
are
the
OSX
build
aired,
I've
had
to
go
in
and
restart
jobs,
quite
a
bit
I'm,
actually
considering
removing
the
OSX
build
until
they
get
a
little
bit
more
stability,
so
I
might
bring
that
up
on
the
mailing
list,
but
so
I
think.
B
A
A
B
A
Yeah
report
that
on
the
mailing
list
or
on
this
ticket,
although
the
ticket
comments
are
getting
pretty
hefty
okay,
the
last
pull
request
we
have
open
is
something
that
mark
is
currently
working
on,
and
this
is
great
it's
a
it's
an
issue
that
I
issued
or
that
I
created
we're
at
run
time.
If
you
pass
a
row
of
data
into
a
new
pic
model
with
the
wrong
data
type,
it
should
be
able
to
find
that
out
and
give
you
an
error.
A
This
sprint
Fergal
said
he
got
some
progress
made,
but
none
of
it's
in
a
remote
branch,
so
I
asked
him
to
put
anything
he's
got
in
a
remote
branch
with
or
without
that
I'm
going
to
continue
with
this
and
try
and
get
something
completed
by
the
end
of
spread.
25
Austin
has
been
talking
about
working
on
supporting
solaris
with
a
new
book
or
a
new
pic
I
think
he's
going
to
have
some
time,
not
this
coming
week,
but
the
next
week
to
work
on
that.
So
that's
assigned
to
him.
A
David
has
a
few
issues
here
that
had
to
do
with
the
region.
Implementation
factory
he'll
be
working
on
that
after
the
PIP
installable
ticket
is
done.
So
if
that
gets
merged
in
this
coming
sprint,
he'll
move
on
to
this.
These
region,
implementation,
factories,
things
and
jayden.
You
still
have
an
issue
about
an
assertion,
four
dimensions.
A
A
The
butter
swarm
era
when
swarm
description
is
wrong.
Cricket
field
right
mark
mark
said
he
would
probably
address
this
with
his
model
with
his
PR.
So
that's
why
that's
currently
showing
up
here
same
thing
with
this
the
mid
warning,
that's
the
same
PR
that
would
would
address
that
separate
code
coverage
reports
for
unit
integration
tests
right
now.
If
you
go
to
the
new
big
repository
v,
we
have
a
coverage
report
here,
as
as
fifteen
percent,
that's
only
unit
tests,
I
would
love
to
have
a
coverage
for
integration
tests
as
well.
This.
A
Priority
item
for
me,
I
think
I'm.
I
think
I
might
just
put
it
on
the
backlog.
I
think
I
have
other
things
that
I'd
rather
work
on,
but
it
would
be
it'd
be
nice
to
have
potentially
ok,
so
I
dropped
that
to
the
backlog,
assuming
I
don't
put
things
on
the
backlog
from
that
are
currently
Vince
print
24
I'm,
going
to
move
them
into
sprint
25.
Just
so.
You
all
know
that
there's
a
run
swarm
feel
you're
on
a
boon
to
that.
Just
still
needs
to
be
addressed.
A
So
we
still
have
this
easy
way
to
make
python
changes
without
recompiling.
Everything
I
want
to
keep
this
open
even
after
the
PIP
installable
branches
merged
in
because
I
want
to
make
sure
that
that
does
give
us
this.
So,
ideally,
we'll
have
a
Python
set
up,
develop
target
where
that
would
accomplish
this,
but
it
might
not
work
so
I
want
to
make
sure
that
it
works
before
we
close.
This
move.
Docker
stuff
out
of
the
root
folder
I
think
this
is
fixed
now,
yeah,
that's
fixed.
That
was
something
that
David
worked
on.
A
A
Yeah
I,
guess
that's
why
it's
still
assigned
to
me
because
I
don't
remember
what
I
need
to
take
you.
There
is
so
I'm
going
to
keep
that
on
my
plate.
Don't
require
d
y
LD
library
path
and
I.
Don't
remember
what
the
status
of
this
is
everybody
once
it
should
be
resolved
by
PIP,
installable,
okay,
so
we'll
keep
it
open
and
verify
it
after.
That
is
I.
A
Think
this
one
too,
with
the
install
binary,
is
the
default
location
by
default.
This
thing
would
be
solved
by
PIP,
installable,
to
and
I
believe
so
with
this,
so
you
don't
have
to
edit
your
Python
bathroom
bath,
etc.
So
all
three
of
these
are
kind
of
addressed
by
the
PIP
installable
thing
move
github
full
get
books
folder
into
new
pic
that
is
done.
I
was
done
with
David's
above
the
root
folder.
A
Okay,
so
all
of
the
remaining
issues
and
sprint
24
we
go
back
to
I,
don't
have
a
complete
functionality
with
all
the
things
I
want
to
do
on
this
kind
of
patch
together
page
though
so
all
the
open
issues
in
sprint.
24.
Now
that
I've
moved
the
ones
out
that
I
don't
want
us
to
work
on
are
going
to
be
moved
into
spring
25
and
it's
from
24
we're
going
to
close
okay
and
now
we'll
go
to
the
core
spread.
A
24
new
bit
core
issues,
sue
+,
+
tests,
yes,
I-
want
that,
like
I
said,
Austin
will
work
on
the
solara,
spilled
I'm,
going
to
leave
the
region
implementation
stuff
in
here
my
yeah,
because
David's
going
to
work
on
that
after
the
bib
installable
is
complete.
So
all
of
these
issues
in
newport
core
currently
in
sprint
24
will
be
moved
into
sprint,
25
and
we're
closings
for
24,
and
there
we
go
for
the.
A
A
One
sec:
the
slab,
goes
to
get
up
several
times
to
love
this
issues.
Something
broke
one
step
every,
oh,
ok,
so
sprint,
24,
there's
a
couple
of
fluent
issues.
I've
I've
been
working
on
trying
to
add,
add
any
new
minta
open
source
projects
to
make
sure
that
they
have
a
Travis
build
and
so
that,
even
if
there
are
no
tests
there
and
most
of
them
do
have
tests
just
to
make
sure
that
they
are
running
in
Travis.
A
A
A
Okay,
I
think
that
is
it
so
now
now
we've
got
sprint:
25
got
36
issues
already
in
sprint,
25,
and
that
includes
pull
requests
so
one
in
two
lanes
over
lancour,
a
bunch
of
new
pic
and
a
couple
other
little
things,
but
that's
where
we
are
at
and
now
we
could
talk
about
how
how
things
went
in
the
sprint.
If
anybody
has
any
any
feedback,
if
you
are
involved
in
any
of
these
issues,
let
me
know
now
or
forever
hold
your
peace.