►
From YouTube: NuPIC Development Progress Review - Oct 3, 2014
Description
A
All
right,
hello,
new
pic,
we
are
live,
we're
having
a
new
development
process
review
meeting
and
I'm
matt
taylor.
We
have
in
the
nementa
office's
austin
marshall,
scott
purdy
and
prince
lesbirinsky.
I
think
jaden's
on
the
way
and
so
for
this
meeting.
What
I
would
like
to
focus
on
is
currently
open
prs,
because
we
have
a
lot
of
open
pr's
right
now,
so
mainly
it's
going
to
talk
about
the
work
that
is
in
progress.
A
A
A
A
A
B
A
Yeah
mark
kind
of
works
in
spurts
if
you've
noticed
he'll
come
in
and
work
for
like
three
days
and
go
a
few
weeks
and
then
come
into
work
a
bunch
in
over
three
days.
So
a
lot
of
the
prs
that
are
currently
open
are
assigned
to
him,
as
you
can
see
over
here
on
the
right
and
I've
gone
in
and
commented
on
pretty
much
all
of
them
and
asked
him
what's
what's
the
status
under
this
or
that
so
the
plan
is
to.
A
C
If
part
of
it
was
compiled
with
ceiling
and
the
other
part
of
it
was
compiled
with
gcc,
it
could
all
build,
but
then
there
were
still
some
linking
issues
and
even
to
get
it
to
that
point,
it
required
quite
a
bit
of
a
hack,
so
not
making
a
whole
lot
of
progress.
We
just
backed
off
on
that
reverted
those
changes
and
thrown
the
back
burner
so
that
we
could
figure
out
what
the
problem
was.
C
A
Okay,
I
mean
the
core
issue
here.
If
I'm
not
mistaken,
is
that
we're
doing
c
compilation
stuff
in
both
of
our
repository
builds
and
if,
if
we
could
simplify
that,
so
that
it
only
happens
in
new
pick
and
we
do,
we
eventually
have
a
binaries
published
that
could
be
pulled
in
by
the
new
pick
builds.
Then
we
wouldn't
be
having
this
problem
right.
A
That
is
the
direction
we
want
to
go
yes,
yeah,
but
it's
not
like.
We
have
all
the
time
or
the
bandwidth
to
do
that
right
now,
or
else
we
would
just
do
that
right
now,
right,
okay,
so
that
makes
sense,
so
this
is
still
open
and
ready
for
work
mark
if
you're
watching
welcome
any
of
your
comments
on
here.
Aside
from
the
last
comment
that
you
had
we'll
be
able
to
work
on
this
coming
up
in
the
next
couple
of
weeks,
this
is
blocking
up
several
other
issues.
A
A
This
is
a
we
were
running
into
a
problem
with
this
too
right.
I
wanted
to
talk
about
that.
He
he
has.
He
presented
some
options
on
how
to
fix
this,
because
I
think
there
were
linking
problems
on
osx,
so
he
is
working
through
this
right
now.
So
it
looks
like
he
even
worked
today
on
this,
which
is
great
and
I'm,
if
you're
watching
utensil,
I'm
ready
to
try
and
test
this
again
once
you're
you're
ready.
A
So
if
that
works
and
that
gets
merged
and-
and
we
should
be
able
to
merge
this
one
excuse
me
after
we
get
the
c
plus
plus
11
thing
done.
So
that's
kind
of
the
cpis
plus
11
one
is
holding
up
the
google
test
one
and
then
there's
these
these
anomaly
tickets
here,
like
normally
strict
anomaly,
call
likelihood
that
are
both
marks
projects,
and
I
believe
the
state
of
both
of
these
are
just
builds
are
erroring
and
he
just
needs
to
put
some
more
work
towards
it.
A
No,
this
one
looks
like
it's
it's
passing,
but
he
has
marked
it
as
blocked
and
I'm
not
sure
why
so
I'm
waiting
for
some
feedback
from
him,
the
anomaly
strict
one.
I
believe
this
is
the
one
that's
not
quite
yeah.
There
is
an
error
on
this,
build
that
he
was
still
working
on
all
right.
So
that's
thanks
for
clearing
up
the
c
plus
plus
11
issue,
I'm
glad
we
hopefully
will
be
able
to
put
that
to
bed
over
the
next
couple
of
weeks.
Let's,
let's
have
a
little
swing
update.
A
So
I
know
basically
nothing
about
swig
at
all.
Mark
started
this
because
we
started
talking
about
how
we
needed
to
update
swag.
So
he
took
the
initiative
and
obviously,
as
you
can
see,
there's
over
a
thousand
files
changed
in
this
pr
which
really
sucks
to
see
that
many
changes
and
austin
has
been
helping
out
with
this.
But
at
this
point
I
don't
know
what
the
next
steps
are.
So
austin,
if
you
know
what's
going
on
here,
status
update,
would
be
good
yeah,
so.
A
A
A
A
They
just
contain
dependencies
beliefs
are
they
I
think
they're
already
compiled
dependencies
for
linux
and
darwin
darwin
being
os
x
and
we've
been
using
it
for
a
long
time.
We
use
them
internally
for
numenta
pipelines,
but
I
don't
think
the
community
generally
uses
them
very
much,
but
it
would
help
if
we
put
it
back
into
our
travis
ci
build.
A
It
might
shave
off
three
five
minutes,
something
like
that
on
our
build,
and
it
also
would
help
be
nice
just
to
continually
validate
that
these
repositories
are
are
properly
working
because
then,
currently
they
are
not.
So
I
tried
adding
this
back
and
realized.
We
had
a
problem
with
pill
and
pillow
pillow
is
or
excuse
me
pill
is
the
predecessor
to
pillow.
A
A
The
files
that
I
found
related
to
pill
tried
to
build
new
pick
on
top
of
it
and,
interestingly,
although
pillow
supposedly
exists
in
here,
I
get
a
no
module
named
pill,
import
error
which
confused
me
so
that
that's
where
I'm
at
on
this
and
I-
and
I
I'm
not
sure
where
to
go
at
this
point
yeah
and
that
led
to
this
issue.
You
know
pill
depends
on
this
certain
library,
lib
tiff
version
5,
which
we
can't
get
access
to
on
in
the
travis
ci
environment,.
C
C
A
A
Yeah,
so
I
I
did
try
when
I
removed
all
the
pill
files,
I
did
try
to
go
into
image
sensor
and
import
from
pillow
instead
of
pill,
and
I
I
I
believe
I
got
the
exact
same
error,
except
from
no
module
named
pillow
was
the
import
error
that
I
got
but
truth
be
told.
I
don't
think
this
is
a
serious
issue.
A
A
Okay,
let
me
see
if
there's
any
other
major
issues
this.
This
is
one
that
david
ray
just
created
and
it's
running
through
travis
right
now,
mark's
issues.
Oh,
let's
talk
quickly
about
the
windows
build,
so
this
is
I
I
want
to
get
this
richard
richard
crowder,
who
started
this
windows,
build
initiative
built
built
on
top
of
work.
I
think
that
david
ragazzi
had
done
in
the
past
and
he's
sort
of
recruited
he's
done
a
lot
of
work
here.
A
Has
this
branch
let's
see
here
it
is
candeel,
has
a
branch
that
is
actually
running
and
passing
in
app
conveyor,
app
conveyor
being
a
windows
ci
system,
so
he's
actually
got
it
running
and
building.
This
is
a
new
big
core,
an
app
conveyor
and
publishing
artifacts
up
to
to
that
that
platform
and
he's
actually
got
its
creating
a
nuget
module,
which
I
don't
know
if
we're
going
to
use
or
not.
I
just
thought:
hey,
that's
that's
cool!
That's
impressive!
That
you
know
we're
very
hands
off
on
this.
A
Numenta
is
not
concerned
about
windows
build,
but
the
community
obviously
is
and
they're
putting
one
together.
The
thing
that
does
concern
me
about
this,
I'm
I
personally
am
happy
as
long
as
if
they
get
a
windows
build
running
as
long
as
it
continues
to
run
in
travis
and
osx,
and
linux
I'm
happy,
but
scrolling
all
the
way
back
up
here.
There's
a
lot
of
files
changed
here
and
they're,
not
just
insignificant
changes.
A
So
this
is
something
I
I
can't
really
review.
I
need
someone
with
the
time
and
the
knowledge
of
c
plus
plus
to
to
run
through
and
make
sure
all
this
makes
sense.
I
mean
it's
not
something
because
it's
so
such
a
big
diff,
not
every
single
line,
doesn't
have
to
be
reviewed,
but
at
least
the
files
need
to
be
reviewed
to
make
sure
that,
like
is
this,
this
is
probably
something
that
was
just
added
for
some
library
that
needs
to
be
included
for
windows.
A
We
just
need
to
verify
that,
first
of
all
that
the
licenses
are
okay
for
us
to
use,
because
I'm
not
certain
about
about
all
the
licenses
and
that
these
additional
dependencies
that
are
used
in
the
windows
build
are
not
going
to
cause
any
other
problems,
and
I
mean
these:
this
is
being
stored
in
external
linux
32
I
mean
it
and
then
there's
a
win,
32
full
holder
in
here
I
mean
I'm
not
even
sure.
If
that's
the
right
place,
we
want
to
put
this
stuff
it
just
it
just.
A
I
think
those
are
the
major
things
yeah.
Those
are
all
the
major
things
I
wanted
to
talk
about.
I'm
not
going
to
talk
much
about
future
plans,
because
I
think
we've
got
more
than
another
two
weeks
of
work,
just
within
the
prs
that
we
currently
have
open.
So
let's
just
focus
on
that
focus
on
near-term.
A
B
Sure
matt
we
were
thinking
about
whether
or
not
we're
getting
any
value
out
of
the
swig
or,
if
it's
just
more
effort
than
it's
worth
so
one
option
is
to
just
have
a
new
pick,
chord
read
the
c
plus
and
then
have
the
language.
Implementations
use
their
native
c
extension
support
to
interface
with
it,
which
would
be
pretty
similar.
What
we
do
with
swift
now
for
python,
at
least
so
it's
something
we're
going
to
kind
of
look
at.
I
think.