►
From YouTube: Compiling NuPIC on OS X Yosemite
Description
A guide to building and compiling NuPIC and nupic.core on OS X from source code.
A
Taylor
again
with
another
tutorial
on
building
and
compiling
new
pick
on
toys,
X
Yosemite,
sometimes
you
can't
install
from
the
binary
file,
which
was
the
previous
installation
tutorial
many
times.
This
is
because
you
have
a
non-standard
version
of
Python
installed
in
your
system
if
you're
using
a
homebrew,
Python
or
anaconda
Python,
and
sometimes
it's
just
because
pip
does
not
recognize
your
platform.
A
So
on
this
page
down
and
build
an
installation
after
you
read
some
of
these
notes,
it
sort
of
tells
you
what
you
need.
So
we
support
Mac,
OS
X.
You
need
Python
development
headers,
you
need
a
compiler
tool
chain
for
C++
11
and
you
need
C,
make
make
and
numpy
Antony
Python
2
7,
like
I,
said.
So
there
is
a
guide
on
installing
Mac
OS
X
I'm,
not
sure
how
up-to-date
this
is.
A
But
what
I'm
going
to
do
because
I've
done
this
a
bunch
of
times
is
I'm
just
going
to
start
from
scratch,
and
so,
as
I
run
into
installation
problems,
you
will
watch
me
debugging
a
lot.
This
is
a
fresh
OSX
machine.
There's
nothing
installed
that
is
non-standard
and
so
I'm,
probably
gonna,
run
into
problems
and
you'll
see
me
run
into
problems.
A
A
So
go
to
github.com,
slash
new
mento,
slash
new
pick,
or
there
is
a
second
set
of
installation
instructions.
So
this
is
the
tricky
bit
here.
I'm
looking
first
at
a
new
pic
core
nuba
core
is
a
C++
program,
almost
all
see
a
little
bit
of
Python,
and
that
is
for
the
bindings.
So
this
is
a
C
application
with
Python
bindings.
This
readme
has
instructions
on
building
and
testing
using
the
command
line,
what
you
need
to
have
installed,
etc.
A
A
A
A
A
A
Okay,
command-line
tools
from
Xcode
has
been
installed,
so
I'll
repeat
the
git
clone
command,
which
is
now
going
to
get
the
whole
new
pic
or
directory,
checked
out
locally
and
we're
going
to
start
there
we're
going
to
go
into
new
procore
and
build
it
before
we
do
new.
But
let's
take
a
quick
preview
of
the
new
perk
or
instructions
so.
A
New
picure
looks
like
an
environment
variable
that
this
might
want
us
to
set
up
platform,
specific
readme,
so
there's
some
external
libraries
and
then
there's
a
see
the
main
weight
wiki
for
more
build
notes
and
we'll
go
there.
So
we
have
Python
2:7,
we
may
or
may
not
have
known
begun,
I'm,
not
sure
we'll
see
if
we
run
into
that
problem.
High
cap
and
P
we'll
see
if
we
run
into
that
too.
A
Probably
I'm
going
to
have
to
get
C
make
and
I
might
do
that
with
homebrew
and
Captain
P
believe
we'll
have
to
install
ourselves
so
we'll
run
into
that.
If
there's
a
problem,
we'll
walk
through
it
and
I'll
show
you
how
to
install
them
itself.
Okay,
let's
go
into
new
pic
core
see.
What's
in
here,
alright
have
source
directory
and
readme
Docs
external
CI
bindings.
What
shall
we
do
first,
so,
let's
first
try
and
install
the
requirements
and
see
what
happens.
A
Numpy
permission
denied:
this
is
where
you
should
not
do.
Sudo
just
add
the
user
onto
the
end
of
your
command,
which
tells
it
to
install
into
a
local
directory
instead
of
a
system
level
directory
that
worked
next
make
directory
build
scripts.
So
I
don't
have
this
new
picquart
set.
So
let's
do
that
real,
quick,
like
support
if
it
core
equals
current
directory,
make
sure
that
works.
A
Yes,
okay,
you
might
want
to
put
that
in
your
batch
RC
or
bash
profile,
so
I'm
going
to
make
a
directory
called
build
scripts.
So
there's
an
empty,
build
scripts
directory
now
and
we'll
go
into
that
directory
and
then
we're
going
to
run
CMake
I,
don't
think
I
have
C
make
no
so
I,
don't
even
think
I
have
homebrew
I,
usually
installed
C
mate
with
homebrew.
So
let's
get
homebrew
real,
quick
easiest
way
to
do.
It
is
to
copy
this,
and
do
this
in
same
thing
and
copy
this
Ruby
command
into
your
shell.
A
A
A
All
right
now,
hopefully,
I
can
say
see,
make
oh,
yes,
so
I
have
see.
Make
now
on
my
command
line,
get
rid
of
this
back
to
Newport
core,
and
now
we
will
run
this
cement
command.
So
what
this
is
doing
is
saying,
run
CMake
on
the
source
directory
the
source
directory
are.
We
here
contains
AC
make
lists
file.
These
are
like
the
instructions
for
seaming,
and
then
it's
also
saying
the
install
prefix
or
where
we
want
you
to
install.
A
A
We
may
or
may
not
run
into
problems
here,
we'll
find
out
all
right.
So
we
have
some
errors,
looks
like
Cap'n
Pete
errors,
captain
P.
We
have
to
install
it
our
selves.
So
let's
do
that.
Cap'n!
Proto
is
what
if
this
is
called,
it's
a
serialization
library,
captain,
proto
and
generally
what
I
do
is
I
will
check
it
out
that
data.
Where
do
we
go
installation,
UNIX,
installation,
windows,
people
just
do
the
UNIX
one
so
yeah.
A
Let's
just
do
this:
let's
grab
it
I'm
gonna
go
I'm
gonna,
put
it
into
another
directory.
So
let's
open
up
oops
I'm
gonna
open
another
directory,
I'm
gonna
make
I
usually
make
a
folder
called
dev
work
with
my
developer
stuff,
so
I'm
gonna
curl
and
grab
captain
proto
and
dump
it
right
into
this
directory
and
there
it
is
open
captain
proto
and
that
expanded
it
for
us.
A
So
the
check
is
a
little
bit
of
overkill.
I.
Don't
think
you
need
to
run
check,
but
it
will
verify
that
kept
the
copy
installation
actually
does
the
right
things.
If
you
fail
on
the
check,
I
think
you
can
just
run
make,
and
it
generally
will
work
and
the
next
will
have
to
sue
do
make
install
once
this
is
done.
Checking
yay,
that's
a
good
thing.
A
A
A
A
A
Maybe
we
haven't
gotten
to
that
part.
Yet
so
it
says
there
the
CMA
installed
prefix
is
optional,
specifies
where
it
should
be
installed.
I
haven't
done
make
yet
that's
why?
Okay
so
I
have
this
while
I'm
still
sitting
I'm,
not
a
sea
person,
so
they
have
to
excuse
my
ignorance
when
it
comes
to
this,
but
hopefully
that
I'm
helping
you
other
people
who
are
not
see
people,
so
the
command
I
want
to
run
is
make
j-3.
A
I'm
gonna
do
j6,
so
I
can
take
advantage
on
the
course
there
we
go
building
all
those
Cappy
stuff
and
now
we're
in
all
of
the
new
pick
core
stuff.
So
we
are
building
C++
right
now,
hooray,
okay,
so
we
just
make
make
tit
made
it
now.
We're
gonna
run,
make
install
from
the
same
location.
This
is
going
to
install
it
wherever
we
told
it
to
install
when
we
specify
this
C
make
install
prefix.
So
it
should
put
it
in
that
release.
A
And
now
we
should
totally
see
yes,
a
release
directory
with
been
including
lip.
That's
what
we
want
to
see,
that
is
the
standard
structure
of
a
Linux
product,
so
it
is
currently
installed
in
that
location
that
we
told
it.
If
we
did
not
give
it
this
DC
make
install
prefix,
it
would
install
it
into
a
system
location
that
may
not
be
what
you
want,
but
it
may
be.
It
depends
on
how
you
want
to
use
it.
A
I,
typically,
don't
install
it
to
a
system
location,
but
when
we
get
to
installing
new
pic
or
going
to
the
next
step,
you
need
to
know
where
that
was
so.
We
did
the
make
install
now
we're
going
to
run
some
tests
so
we're
still
in
the
build
scripts
file
or
directory.
So
we'll
make
the
test
cpp
region
all
tests
past
make
tests
unit
takes
a
little
bit
longer.
All
these
errors
are
actual
errors.
It
expects
to
get
so
as
long
as
it
says
past
the
end.
It's
good
so
tests
past.
A
So
now
we're
going
to
go
back
into
newt
the
core
and
we're
going
to
install
new
pic
bindings.
Ok,
so
currently
we
have
a
C++
project
installed
in
that
release
directory,
but
we
don't
have
a
Python
a
way
for
Python
to
call
into
that
C
project.
The
new
pic
bindings
project
is
a
Python
project
that
provides
language
bindings
from
that
nupic
core
C++
project
into
Python.
A
That's
what
we'll
need
when
we
install
new
pick
it
the
bindings
has
to
be
there
so
that
nupoc
can
call
into
new
decor
so
back
to
new
decor
and
pythons
setup
install
and
we're
going
to
tell
it
in
the
nupoc
chord
directory
that
we
installed
new
bit
core.
Is
that
build
release
directory?
So
this
is
exactly
the
right
instruction
use,
and
now
we
get
a
failure.
So,
let's
see
what's
up
here,
it
looks
like
numpy
version:
was
it
to
build
new
decor
bindings,
OS
X?
A
You
must
export
arch
flags
arch
whatever
yeah,
so
that's
absolutely
something
I
neglected
to
do
and
I
think
that's
stated
right
here.
So
this
is
the
command
I'm
going
to
run
on
OS
X,
because
this
architecture
flag
must
be
set.
So
let's
do
that
and
must
provide
a
release
directory,
of
course,
because
I
forgot
to
add
this
bit
right.
A
So
at
the
end,
I'm
gonna
add
that
nupoc
or
so
my
full
command
is
arch
flag
and
you
can
just
export
this
and
leave
it
in
your
batch,
our
CEO
or
whatever.
But
this
is
like
for
this
command.
This
environment
variable
is
going
to
be
said,
python
set
up,
install
needs
it,
and
we
also
need
to
specify
where
new
click
or
release
is,
and
here
we
go.
We
are
building
swig
Python
language
bindings.
On
top
of
your
core
right
now,.
A
A
Putting
together
some
developer
guides
new
minted
developers
set
up.
This
is
brand
new.
We
had
just
a
discussion
about
this
yesterday,
so
there
is
a
wiki
page
called
Numenta
developers
set
up,
and
this
is
how
all
Numenta
engineers
working
on
building
and
running
a
new
pic
are
going
to
set
up
their
machines.
So
there's
much
more
specific
instructions
here
on
exactly
how
we
do
things.
A
If
you
find
that
useful
and
if
you
especially
if
you
plan
on
becoming
a
contributor
to
the
nupoc
project,
this
would
be
a
great
document
to
take
a
look
at,
but
there's
many
much
more
details
than
we
need
just
to
get
new
pic
running
on
your
system.
All
right.
We
got
a
permission
denied
error.
That
typically
means
we
just
need
to
add
the
user
flag
user,
because
we
were
running
a
pip
command
or
a
setup
command.
A
A
A
Lots
of
warnings-
you
know
a
lot
of
those
come
from
external
libraries,
almost
all
of
them
do
because
we're
compiling
them
using
our
own
configuration
and
they
may
not
adhere
to
our
standards
of
our
compiler
settings.
All
right.
This
is
good.
This
looks
like
nupoc
bindings
was
installed
version
zero
to
one.
We
should
be
able
to
now
go
into
a
Python
interpreter,
import
new
pick,
dot
bindings
without
error,
which
is
good.
Okay,
we
have
now
new
picure
installed
and
that
release
directory
inside
of
builds
release.
That's
whoops
build
release.
A
A
So
the
compilation
instructions
I
think
all
we
need
to
do
to
install
new
pic
at
this
point
is
simply
run
Python
setup,
dot,
pi
install
user,
because
new
pic
bindings
is
installed
and
ready
for
its
use
and
the
hard
part's
basically
done
new
pic
is
a
pure
Python
project.
At
this
point,
so
there
should
be
no
complications.
Installing
new
pic
now
that
new,
core
and
diffic
bindings
are
installed,
looks
good.
A
So
now
we
have
the
latest
source
code
for
new
pic
core
and
for
new
pic
installed
on
our
system.
New
pic
core
is
installed
in
that
release
directory
under
build
release
in
the
new
pic
core
repository.
New
pic
bindings
is
installed
as
a
pip
or
a
Python
module
that
binds
to
that
installation
and
new
pic
has
been
installed
as
well
through
setup
tools
as
a
Python
module.
That
depends
upon
new
pic
bindings.
So
now
is
the
time
to
run
some
tests
and
figure
out.
A
If
everything
is
working,
we
have
a
bunch
of
tests
in
the
test
directory
where
my
tests
directory
you've
got
unit
integration,
swarming
aggression
etc,
and
we
also
have
scripts
that
will
run
these
tests
in
the
scripts
directory,
so
I'm
going
to
run
the
scripts
directory.
This
requires
that
you
have
PI
test
installed
on
your
system
in
a
previous
installation,
tutorial
I
forced
an
install
with
sudo,
which
wasn't
the
right
thing
to
do.
A
A
This
scripts,
the
scripts
in
the
scripts
directory
that
run
tests
depend
on
calling
out
to
PI
dot
test.
So
when
you
run
this
run
nupoc
tests,
you,
you
must
have
PI
dot
test
installed
and
it's
all
these
tests
should
either
pass
or
be
skipped,
oh
good.
So
all
of
our
tests
passed,
which
is
a
very
good
thing.
So
now,
let's
run
some
examples:
I'm
gonna
go
into
the
examples:
directory,
opf
clients,
hot
gem,
simple
and
let's
try
and
run
that
there's
a
file
in
here
called
hot
gem.
A
This
will
create
a
new
new
pic
model
and
start
passing
real
data
into
it
and
output.
The
that
the
error
average
error
over
time
it's
in
screen.
So
as
long
as
you
see
it
doing
something
like
this,
it's
working,
so
that's
good
and
let's
go
into
a
one-gene
prediction
one
and
run
a
swarm
real,
quick.
You
will
have
to
install
my
sequel
to
run
the
swarm
the
way
I
installed.
My
sequel
was
with
homebrew.
You
can
go
download
my
sequel
and
compile
it.
A
Install
it
yourself
or
I
think
you
can
also
get
it
on
the
App
Store,
or
something
like
that.
My
my
sequels
starts
by
running
my
sequel.
Server
start,
which
it's
already
running
so
now
I
should
be
able
to
just
run
this
swarm
command,
and
this
should
work.
This
will
run
for
quite
a
while.
There's
no
need
for
for
us
to
run
right
run
through
it
the
entire
way.
But
if
you
want
to
run
swarms,
you
have
to
have
my
sequel
run:
kill
all
the
Python
processes
the
swarm
started.
So
that's
that's
about
it.
A
A
Don't
know
it
was
that
long
arch,
arch,
Flags
equals
Python
setup
install
you
sure,
make
the
core
dirt
equals
all
blah.
So
you
run
that
and
then
you
go
back
into
new
pic
thumbs
and
run
the
Python
setup
install
there.
So
that's
one
thing
that
you
can
do
another
thing
you
can
do
that
I've
found
is,
if
you
go
into
new
pic
and
you
can't
run
tests
for
some
reason
or
they,
when
you
run
the
test
script,
there's
some
weird
failures:
clean
out
the
tests
directory.
You
can
see
some
of
the
tests
leave
out.
A
Some
leave
some
junk
in
here.
I.
Really
wish
they
didn't,
and
even
in
you
get
status,
sometimes
you
can
see.
There's
extra
stuff,
there's
the
stuff
left
over
from
a
swarm
that
I
ran
one
command
that
will
clean
up.
Everything
is
get
clean
dfx.
This
will
blow
away
everything.
That's
not
in
source
control,
so
be
aware
e
if
you've
added
something
and
you
haven't
committed
it
and
you're
planning
on
committing
it
or
working
on
something
it
will
blow
it
away.
A
But
you
see
all
the
junk
that
gets
removed
here,
a
bunch
of
pyc
files
from
tests
and
stuff.
If
these
are
old
or
halfway
generated,
your
tests
might
not
run
properly
so
removing
them
by
running
it,
clean
dfx,
we'll
get
rid
of
all
that
stuff,
and
then
you
can
you'll
have
to
reinstall
new
pic
again
Python
setup,
install
I
think,
but
that's
a
really
quick
step,
and
then
you
can
run
your
test
again
and
everything
should
work
so
there's
a
couple
of
troubleshooting
hints.
A
Hopefully
that
helps
and
if
you're
still
having
problems
getting
new
pic
core
new
big
bindings,
new
pic,
compiling
and
running
on
your
system.
Please
email
the
mailing
list
or
jump
on
to
our
gear
chat,
room
I'm,
usually
in
there
and
I'll,
try
and
help
you
as
well
as
I
can
so
thank
you
for
watching
I
hope
this
helps
you
guys
get
get
running
on
new
pic.
So
let
me
know
thank
you.