►
From YouTube: NuPIC Community Fork Planning Meeting
A
C
I
mean
so
basically,
I
was
busy
with
like
two
things
that
I'm
trying
to
achieve.
First,
is
it's
basically
getting
getting
rid
of
Swick
from
the
current
reform,
the
current
new
pic
foam-core
installation,
and
so
instead
of
using
swig
I'm
trying
to
you
to
use
something
else,
something
called
PI
bind
and
I.
Think
it's
a
much
easier
interface
and
it's
much
easier
to
test
and
to
use
it
so
I
think
I
am
finally
done
with
this.
Adding
all
these
interface
methods
to
PI
bond.
C
It's
actually
quite
quite
a
lot
of
verbs,
just
for
instance,
this
bus
metrics
class
has
about
over
340
functions
that
have
to
be.
You
know,
converted
into
C++
you
from
the
Swick
interface
fire.
So
there
was,
there
was
quite
a
quite
a
bit
of
work
and
hopefully
I
mean
it
seems
to
be
working
most
of
the
time
by
the
way,
I'm
pretty
sure
they
asked
some
some
bugs
in
them
and
secondly,
I
was
also
working
on
the
Python
free
migration
and
I've
been
making
some
progress.
C
So
the
good
news
is
that
now
most
of
the
new
pig
algorithm
test
cases,
they
want
food,
there's
one
exception,
but
at
least
or
audiology
other
ones.
They
are
running
food
and
that's
good
and
because
problem
is
free
is
coming
from
Python
as
it's
like,
for
instance,
the
internet
division
initiative,
division
change,
I,
just
recently
learned,
you
can
actually
change
the
division
behavior.
Even
in
Python,
you
just
have
to
add
a
different
module.
It
is
so
called
future
module
into
your
Python
2.7
file.
C
He
would
have
the
behavior
of
Python
3
in
it,
so
I
think
that
might
be
one
way
of
of
local
of
localizing
some
of
these
issues
without
actually
using
any
parts
on
free
classes.
There
might
be
something
that
I
really
would
be
trying
out
just
to
see
their
new
Pig
very
fair.
If
I
just
add
this
module
the
future,
much
really
at
the
start
of
a
fire.
You.
B
C
A
C
That
thing,
so
you
can
so
we
can
compile
them
you
you
pick
kora
the
seem
a
quite
now.
It's
really
working
on
on
Visual
Studio,
which
of
course,
is
it.
It's
not
the
final
it's
solution
and
then
also
continue
investor
continuous
integration.
That
would
be
nice
to
a
half
by
the
end,
but
at
the
end
of
the
next
month,
or
maybe
for
the
next
meeting
and
then
hopefully
we
can
finally
move
everything
into
the
no
mantas
community
repositories.
I
think
that
would
be
the
delight
order.
B
B
B
So
then,
later
the
engine
consists
of
the
engine,
utils
types
and
n
types
holders
and
the
plugins
are
built
from
pieces
from
algorithms,
encoders
math
and
of
course,
then
we
have
to
do
a
whole
lot
of
testing
know
that
part
I
haven't
done
at
some
point:
I'm
going
to
go
through
the
Python
test
routines
once
you've
already
worked
with
and
convert
those
all
to
c-sharp,
because
I
have
to
do
the
same
type
of
test
for
my
sides.
What
you
do
from
yours,
oh
yeah,
yeah,
and
that's
going
to
be
a
so
a
lot
of
tests.
B
B
Well,
anyway,
it's
that
makes
up
your
mind,
yeah,
the
python
region
that
makes
the
plugin
now
a
plugin
that
uses
the
c++
algorithms
still
has
to
have
Python
code
first
or
SP
region
and
TM
region,
and
since
I
can't
use
those
I
have
to
create
new
one
so,
rather
than
build
equivalent
in
c-sharp
thinking
about
building
ones.
In.
B
B
B
B
B
B
B
B
C
A
B
A
B
C
Yeah
I
think
I
think
have
you
actually
set
up
the
general
structure
of
these
repositories?
I,
don't
think
we
should
have
just
one
I
think
we
should
have
one
for
loop
pick,
you
know
which,
which
would
contain
the
piles
and
free
stuff,
and
then
maybe
one
for
you
pick
core,
which
is
do
basically
didn't.
Did
you
you
pick
for
you
not
using
Swick
anymore
about
the
PI
bond
yeah.
C
B
C
There
must
actually
I
created
that,
because
of
a
misunderstanding,
I
had
this
pi
bond,
you
don't
actually
need
that
you
actually
don't
have
to
have
you,
don't
really
have
to
use
SharePoint
that
you
can
actually
just
use
C++
point
a
selectively
the
oil
C
C
style
qantas,
but
I
think
in
the
long
run
it
I
think
it
makes
more
sense.
Yeah.
B
Yeah,
it
does
because
there's
a
lot
of
places
where
the
engine
will
allocate
stuff
and
other
places
will
the
interface
is
supposed
to
allocate
them
and
they
had
all
kinds
of
ways
to
keep
a
track
of
who
it
a
located.
What
so
they
get
freed,
but
with
the
shared
pointers,
all
all
that
goes
away,
that's
much
cleaner.
We
might
want
to
even
go
back
and
and
clean
up
some
of
the
core
code.
Some
point
I.