Pontão Nós Digitais - Contribuições do usuário [pt-br]

MultiViewCam

2014-10-02T20:23:09Z

Mamorim:

O objetivo desta página é fornecer um tutorial para montagem de um sistema de captura de múltiplas câmeras de vídeo simultâneo, utilizando o "Motion"

== Instalação ==

Primeiro instale o Motion


sudo apt-get install motion


== Configuração ==

Localize os arquivos .conf. No Ubuntu o melhor lugar para procurar é /etc/motion. Nesta pasta serão encontrados 5 arquivos:
motion.conf; thread1.conf; thread2.conf; thread3.conf; thread4.conf.

O arquivo motion.conf mantém as configurações globais de todas as câmeras utilizadas.
As configurações individuas para cada câmera são feitas nos arquivos thread#.conf

Para utilizar 2 câmeras simultâneas será necessário modificar os arquivos motion.conf e 2 arquivos thread#.conf, ou seja, 3 arquivos no total

=== motion.conf ===

Neste arquivo devemos verificar se as seguintes linhas estão comentadas como abaixo

;netcam_url value
;target_dir value
;webcam_port 8081
;videodevice /dev/video0

como serão usadas duas câmeras será necessário descomentar as linhas correspondentes a 2 thread#.conf no final do arquivo motion.conf.

thread /etc/motion/thread1.conf
thread /etc/motion/thread2.conf
;thread /etc/motion/thread3.conf
;thread /usr/local/etc/thread4.conf

Agora basta configurar os arquivos thread#.conf

=== thread#.conf ===

Estes arquivos requerem pouca modificação, por exemplo

==== thread1.conf ====

videodevice /dev/video0
text_left Cam-1
target_dir /home/Usuario/motion/Cam1
webcam_port 8081

==== thread2.conf ====

videodevice /dev/video1
text_left Cam-2
target_dir /home/Usuario/motion/Cam2
webcam_port 8082

OBS:

* videodevice: Deve ser configurado para o endereço /dev da webcam usada. Para descobrir basta digitar find /dev -name vídeo* no terminal. Este comando deverá mostrar as webcams que você tem. No meu caso, foi video0 e video1.

*input - Deve ser configurado para 8 se for utilizar uma webcam, ou 1 se for utilizar uma placa de TV.

*target_dir - Deve ser configurado para o local onde deseja armazenar as imagens e vídeos capturados.

== Configurações adicionais ==

No arquivo motion.conf é onde devem ser mantidas as configurações globais de ambas as câmeras. Aqui apresento algumas das possíveis configurações

* width: largura da imagem. Intervalo válido: dependente da câmera (default: 320)
* height: altura da imagem. Intervalo válido: dependente da câmera (default: 240)
* framerate: Número máximo de frames a serem capturados por segundo. Intervalo válido: 2-100 (default: 2)
* output_all: Esta opção quando ativada permite sempre gravar imagens mesmo quando movimentos não são identificados. (default: off)

MultiViewCam

2014-10-02T20:18:09Z

Mamorim: /* Configurações adicionais */

O objetivo desta página é fornecer um tutorial para montagem de um sistema de captura de múltiplas câmeras de vídeo simultâneo, utilizando o "Motion"

== Instalação ==

Primeiro instale o Motion


sudo apt-get install motion


== Configuração ==

Localize os arquivos .conf. No Ubuntu o melhor lugar para procurar é /etc/motion. Nesta pasta serão encontrados 5 arquivos:
motion.conf; thread1.conf; thread2.conf; thread3.conf; thread4.conf.

O arquivo motion.conf mantém as configurações globais de todas as câmeras utilizadas.
As configurações individuas para cada câmera são feitas nos arquivos thread#.conf

Para utilizar 2 câmeras simultâneas será necessário modificar os arquivos motion.conf e 2 arquivos thread#.conf, ou seja, 3 arquivos no total

=== motion.conf ===

Neste arquivo devemos verificar se as seguintes linhas estão comentadas como abaixo

;netcam_url value
;target_dir value
;webcam_port 8081
;videodevice /dev/video0

como serão usadas duas câmeras será necessário descomentar as linhas correspondentes a 2 thread#.conf no final do arquivo motion.conf.

thread /etc/motion/thread1.conf
thread /etc/motion/thread2.conf
;thread /etc/motion/thread3.conf
;thread /usr/local/etc/thread4.conf

Agora basta configurar os arquivos thread#.conf

=== thread#.conf ===

Estes arquivos requerem pouca modificação, por exemplo

==== thread1.conf ====

videodevice /dev/video0
text_left Cam-1
target_dir /home/Usuario/motion/Cam1
webcam_port 8081

==== thread2.conf ====

videodevice /dev/video1
text_left Cam-2
target_dir /home/Usuario/motion/Cam2
webcam_port 8082

OBS:

* videodevice: Deve ser configurado para o endereço /dev da webcam usada. Para descobrir basta digitar find /dev -name vídeo* no terminal. Este comando deverá mostrar as webcams que você tem. No meu caso, foi video0 e video1.

*input - Deve ser configurado para 8 se for utilizar uma webcam, ou 1 se for utilizar uma placa de TV.

*target_dir - Deve ser configurado para o local onde deseja armazenar as imagens e vídeos capturados.

== Configurações adicionais ==

No arquivo motion.conf é onde devem ser mantidas as configurações globais de ambas as câmeras. Aqui apresento algumas das possíveis configurações

* width: largura da imagem. Intervalo válido: dependente da câmera (default: 320)
* height: altura da imagem. Intervalo válido: dependente da câmera (default: 240)
* framerate: Número máximo de frames a serem capturados por segundo. Intervalo válido: 2-100 (default: 2)
* outpout_all: Esta opção quando ativada permite sempre gravar imagens mesmo quando movimentos não são identificados. (default: off)

MultiViewCam

2014-10-02T20:01:45Z

Mamorim: /* Configurações adicionais */

O objetivo desta página é fornecer um tutorial para montagem de um sistema de captura de múltiplas câmeras de vídeo simultâneo, utilizando o "Motion"

== Instalação ==

Primeiro instale o Motion


sudo apt-get install motion


== Configuração ==

Localize os arquivos .conf. No Ubuntu o melhor lugar para procurar é /etc/motion. Nesta pasta serão encontrados 5 arquivos:
motion.conf; thread1.conf; thread2.conf; thread3.conf; thread4.conf.

O arquivo motion.conf mantém as configurações globais de todas as câmeras utilizadas.
As configurações individuas para cada câmera são feitas nos arquivos thread#.conf

Para utilizar 2 câmeras simultâneas será necessário modificar os arquivos motion.conf e 2 arquivos thread#.conf, ou seja, 3 arquivos no total

=== motion.conf ===

Neste arquivo devemos verificar se as seguintes linhas estão comentadas como abaixo

;netcam_url value
;target_dir value
;webcam_port 8081
;videodevice /dev/video0

como serão usadas duas câmeras será necessário descomentar as linhas correspondentes a 2 thread#.conf no final do arquivo motion.conf.

thread /etc/motion/thread1.conf
thread /etc/motion/thread2.conf
;thread /etc/motion/thread3.conf
;thread /usr/local/etc/thread4.conf

Agora basta configurar os arquivos thread#.conf

=== thread#.conf ===

Estes arquivos requerem pouca modificação, por exemplo

==== thread1.conf ====

videodevice /dev/video0
text_left Cam-1
target_dir /home/Usuario/motion/Cam1
webcam_port 8081

==== thread2.conf ====

videodevice /dev/video1
text_left Cam-2
target_dir /home/Usuario/motion/Cam2
webcam_port 8082

OBS:

* videodevice: Deve ser configurado para o endereço /dev da webcam usada. Para descobrir basta digitar find /dev -name vídeo* no terminal. Este comando deverá mostrar as webcams que você tem. No meu caso, foi video0 e video1.

*input - Deve ser configurado para 8 se for utilizar uma webcam, ou 1 se for utilizar uma placa de TV.

*target_dir - Deve ser configurado para o local onde deseja armazenar as imagens e vídeos capturados.

== Configurações adicionais ==

No arquivo motion.conf é onde devem ser mantidas as configurações globais de ambas as câmeras. Aqui apresento algumas das possíveis configurações

* width: largura da imagem. Intervalo válido: dependente da câmera
* height: altura da imagem. Intervalo válido: dependente da câmera
* framerate: Número máximo de frames a serem capturados por segundo. Intervalo válido: 2-100
* outpout_all: Esta opção quando ativada permite sempre gravar imagens mesmo quando movimentos não são identificados.

MultiViewCam

2014-10-02T19:57:40Z

Mamorim: Criou página com 'O objetivo desta página é fornecer um tutorial para montagem de um sistema de captura de múltiplas câmeras de vídeo simultâneo, utilizando o "Motion" == Instalação ==...'

O objetivo desta página é fornecer um tutorial para montagem de um sistema de captura de múltiplas câmeras de vídeo simultâneo, utilizando o "Motion"

== Instalação ==

Primeiro instale o Motion


sudo apt-get install motion


== Configuração ==

Localize os arquivos .conf. No Ubuntu o melhor lugar para procurar é /etc/motion. Nesta pasta serão encontrados 5 arquivos:
motion.conf; thread1.conf; thread2.conf; thread3.conf; thread4.conf.

O arquivo motion.conf mantém as configurações globais de todas as câmeras utilizadas.
As configurações individuas para cada câmera são feitas nos arquivos thread#.conf

Para utilizar 2 câmeras simultâneas será necessário modificar os arquivos motion.conf e 2 arquivos thread#.conf, ou seja, 3 arquivos no total

=== motion.conf ===

Neste arquivo devemos verificar se as seguintes linhas estão comentadas como abaixo

;netcam_url value
;target_dir value
;webcam_port 8081
;videodevice /dev/video0

como serão usadas duas câmeras será necessário descomentar as linhas correspondentes a 2 thread#.conf no final do arquivo motion.conf.

thread /etc/motion/thread1.conf
thread /etc/motion/thread2.conf
;thread /etc/motion/thread3.conf
;thread /usr/local/etc/thread4.conf

Agora basta configurar os arquivos thread#.conf

=== thread#.conf ===

Estes arquivos requerem pouca modificação, por exemplo

==== thread1.conf ====

videodevice /dev/video0
text_left Cam-1
target_dir /home/Usuario/motion/Cam1
webcam_port 8081

==== thread2.conf ====

videodevice /dev/video1
text_left Cam-2
target_dir /home/Usuario/motion/Cam2
webcam_port 8082

OBS:

* videodevice: Deve ser configurado para o endereço /dev da webcam usada. Para descobrir basta digitar find /dev -name vídeo* no terminal. Este comando deverá mostrar as webcams que você tem. No meu caso, foi video0 e video1.

*input - Deve ser configurado para 8 se for utilizar uma webcam, ou 1 se for utilizar uma placa de TV.

*target_dir - Deve ser configurado para o local onde deseja armazenar as imagens e vídeos capturados.

== Configurações adicionais ==

No arquivo motion.conf é onde devem ser mantidas as configurações globais de ambas as câmeras. Aqui apresento algumas das possíveis configurações

* width: largura da imagem. Intervalo válido: dependente da câmera
* height: altura da imagem. Intervalo válido: dependente da câmera
* framerate: Número máximo de frames a serem capturados por segundo. Intervalo válido: 2-100

VXL

2014-05-28T14:04:49Z

Mamorim: /* Compiling */

VXL is a collection of C++ computer vision libraries (and python bindings) with contributions from Kitware, GE, Brown University, and others. This wiki page contains unofficial notes from some developers.

== Git Repo ==
Folow the instructions at https://sourceforge.net/p/vxl/wiki/Git/

== Hacking ==

=== Apple OSX ===
There are a few bugs affecting compilation, see [https://trac.macports.org/ticket/41241]

* make -j9 is having a non-deterministic behavior - try running it a few times, but make -j5 sometimes works better as far as errors go. A plain make is always safer.
* If you find an error related to ffmpeg, then I just left all FFMPEG-related entries in CMAKE blank. That removes support for video loading but thats about it.
* A compilation error related to X11 means the headers from the wrong place are being used. I had to modify the cmake flag for x11 includes to point to /opt/local/include
* My current CMake settings to compile in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-txt]

==== Patches to compile VXL in OSX ====
In addition to the above measures, a number of source code changes had to be implemented to get VXL to compile.
* All the source code changes I had to do in order to get VXL to compile are available in my Github copy of vxl, branch <tt>osx-compile-fixes</tt> [https://github.com/rfabbri/vxl]
* A link time error related to OpenGL acceleration in vgui/tests means this test is outdated and should be ignored. Comment out that file or the offending lines. Alternatively, you could point the OpenGL CMake variables to /opt/... since those opengl libs contain the desired symbols, but they're older.
* The above link mentions a OPENJPEG2 work around
* '''See also''': [[Mac|General OSX-related development instructions]]

== Writing a program that uses VXL ==

A simple example using CMake is <tt>hello-vxl</tt>:
git clone ssh://SOURCEFORGE_LOGIN@labmacambira.git.sourceforge.net/gitroot/labmacambira/hello-vxl

Read the README.

== Setting up VxL Programming environment at [[IPRJ]] ==
This is Ricardo Fabbri's recommended workflow for working with the official VXL plus an internal repo (here named LEMSVXL)

* download vxl git
** place it into folder vxlprg/vxl
* we use LEMSVXL - an internal (closed) repo of vxl-based libs from Brown
** download lemsvxl git
** place it into folder vxlprg/lemsvxl
* create build directories lemsvxl-bin and vxl-bin inside vxlprg
mkdir lemsvxl-bin vxlprg-bin
=== Compiling ===
* on the commandline, enter vxl-bin
* type
ccmake ../vxl
* type 'c' for "configure"
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
at first BUILD_VGUI = OFF
CMAKE_BUILD_TYPE = Debug (for now)
VNL_CONFIG_LEGACY_METHODS = on (needed for lemsvxl)
* type 'c' once more
* inspect any CMAKE variables that might have changed (they have a star * attached to them)
* type 'c' again until no new variables show up and config is right
* once 'g' appears, press 'g' (generate)
* press 'q'
* type 'make -j9'
* if there is any error:
** retry with simply 'make'
** test your build
*** go inside 'core' and type 'make'. See if there are any errors. If not, good.
*** go inside contrib/brl and type 'make'. See if there are any errors. If so, you might not be able to build what you want from the internal lemsvxl repo. But keep going, at least core builds.
*** optionally if there are still errors just do 'make -j9 --keep-going' to
build as much as possible before moving on to your private lemsvxl repo

==== Compiling lemsvxl ====

* enter lemsvxl-bin
* ccmake ../lemsvxl
* Fill in where your vxl-bin folder is as the VXL path, then press 'c', then
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
CMAKE_BUILD_TYPE = Debug (for now)
BUILD_CONTRIB = on (for now)
BUILD_ALGO = on
BUILD_CONTRIB = on
can be usefol to set USE_BOOST
* press 'c' and fill out info until you get a 'g'
* try out a first make -j9 - it will likely have errors
* if it does have errors, just make in your desired path:
** For the symbolic edge linker, for instance, you just need to get 'brcv/seg/dbdet' to compile. All dependencies will be compiled.
*** cd brcv/seg/dbdet/tests
*** make
*** cd brcv/seg/dbdet/algo/tests
*** make
*** cd brcv/seg/dbdet
*** make
** Once you compiled the key basic libs for your application, now move on to compile the GUI parts
** In the case of edge detection:
*** cd contrib/edge_det/gui
*** make
*** backtrack and compile each lib separately to solve problems.
* April 4 2014: I had to comment out anything related to bvis1_gl_codec, and vidl1, with no apparent harm to my research code
* My current CMake settings to compile LEMSVxL in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-lemsvxl-txt]

== Links ==

* Official website: http://vxl.sourceforge.net
* Our [[Pattern Theory]] course page
* Our [[Computer Vision]] grad and undergrad course page

[[Category:Lab Macambira]]

[[Category:Video]]

VXL

2014-05-28T13:57:22Z

Mamorim: /* Compiling */

VXL is a collection of C++ computer vision libraries (and python bindings) with contributions from Kitware, GE, Brown University, and others. This wiki page contains unofficial notes from some developers.

== Git Repo ==
Folow the instructions at https://sourceforge.net/p/vxl/wiki/Git/

== Hacking ==

=== Apple OSX ===
There are a few bugs affecting compilation, see [https://trac.macports.org/ticket/41241]

* make -j9 is having a non-deterministic behavior - try running it a few times, but make -j5 sometimes works better as far as errors go. A plain make is always safer.
* If you find an error related to ffmpeg, then I just left all FFMPEG-related entries in CMAKE blank. That removes support for video loading but thats about it.
* A compilation error related to X11 means the headers from the wrong place are being used. I had to modify the cmake flag for x11 includes to point to /opt/local/include
* My current CMake settings to compile in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-txt]

==== Patches to compile VXL in OSX ====
In addition to the above measures, a number of source code changes had to be implemented to get VXL to compile.
* All the source code changes I had to do in order to get VXL to compile are available in my Github copy of vxl, branch <tt>osx-compile-fixes</tt> [https://github.com/rfabbri/vxl]
* A link time error related to OpenGL acceleration in vgui/tests means this test is outdated and should be ignored. Comment out that file or the offending lines. Alternatively, you could point the OpenGL CMake variables to /opt/... since those opengl libs contain the desired symbols, but they're older.
* The above link mentions a OPENJPEG2 work around
* '''See also''': [[Mac|General OSX-related development instructions]]

== Writing a program that uses VXL ==

A simple example using CMake is <tt>hello-vxl</tt>:
git clone ssh://SOURCEFORGE_LOGIN@labmacambira.git.sourceforge.net/gitroot/labmacambira/hello-vxl

Read the README.

== Setting up VxL Programming environment at [[IPRJ]] ==
This is Ricardo Fabbri's recommended workflow for working with the official VXL plus an internal repo (here named LEMSVXL)

* download vxl git
** place it into folder vxlprg/vxl
* we use LEMSVXL - an internal (closed) repo of vxl-based libs from Brown
** download lemsvxl git
** place it into folder vxlprg/lemsvxl
* create build directories lemsvxl-bin and vxl-bin inside vxlprg
mkdir lemsvxl-bin vxlprg-bin
=== Compiling ===
* on the commandline, enter vxl-bin
* type
ccmake ../vxl
* type 'c' for "configure"
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
at first BUILD_VGUI = OFF
CMAKE_BUILD_TYPE = Debug (for now)
VNL_CONFIG_LEGACY_METHODS = on (need to use lemsvxl)
* type 'c' once more
* inspect any CMAKE variables that might have changed (they have a star * attached to them)
* type 'c' again until no new variables show up and config is right
* once 'g' appears, press 'g' (generate)
* press 'q'
* type 'make -j9'
* if there is any error:
** retry with simply 'make'
** test your build
*** go inside 'core' and type 'make'. See if there are any errors. If not, good.
*** go inside contrib/brl and type 'make'. See if there are any errors. If so, you might not be able to build what you want from the internal lemsvxl repo. But keep going, at least core builds.
*** optionally if there are still errors just do 'make -j9 --keep-going' to
build as much as possible before moving on to your private lemsvxl repo

==== Compiling lemsvxl ====

* enter lemsvxl-bin
* ccmake ../lemsvxl
* Fill in where your vxl-bin folder is as the VXL path, then press 'c', then
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
CMAKE_BUILD_TYPE = Debug (for now)
BUILD_CONTRIB = on (for now)
BUILD_ALGO = on
BUILD_CONTRIB = on
can be usefol to set USE_BOOST
* press 'c' and fill out info until you get a 'g'
* try out a first make -j9 - it will likely have errors
* if it does have errors, just make in your desired path:
** For the symbolic edge linker, for instance, you just need to get 'brcv/seg/dbdet' to compile. All dependencies will be compiled.
*** cd brcv/seg/dbdet/tests
*** make
*** cd brcv/seg/dbdet/algo/tests
*** make
*** cd brcv/seg/dbdet
*** make
** Once you compiled the key basic libs for your application, now move on to compile the GUI parts
** In the case of edge detection:
*** cd contrib/edge_det/gui
*** make
*** backtrack and compile each lib separately to solve problems.
* April 4 2014: I had to comment out anything related to bvis1_gl_codec, and vidl1, with no apparent harm to my research code
* My current CMake settings to compile LEMSVxL in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-lemsvxl-txt]

== Links ==

* Official website: http://vxl.sourceforge.net
* Our [[Pattern Theory]] course page
* Our [[Computer Vision]] grad and undergrad course page

[[Category:Lab Macambira]]

[[Category:Video]]

VXL

2014-05-28T13:55:52Z

Mamorim: /* Compiling lemsvxl */

VXL is a collection of C++ computer vision libraries (and python bindings) with contributions from Kitware, GE, Brown University, and others. This wiki page contains unofficial notes from some developers.

== Git Repo ==
Folow the instructions at https://sourceforge.net/p/vxl/wiki/Git/

== Hacking ==

=== Apple OSX ===
There are a few bugs affecting compilation, see [https://trac.macports.org/ticket/41241]

* make -j9 is having a non-deterministic behavior - try running it a few times, but make -j5 sometimes works better as far as errors go. A plain make is always safer.
* If you find an error related to ffmpeg, then I just left all FFMPEG-related entries in CMAKE blank. That removes support for video loading but thats about it.
* A compilation error related to X11 means the headers from the wrong place are being used. I had to modify the cmake flag for x11 includes to point to /opt/local/include
* My current CMake settings to compile in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-txt]

==== Patches to compile VXL in OSX ====
In addition to the above measures, a number of source code changes had to be implemented to get VXL to compile.
* All the source code changes I had to do in order to get VXL to compile are available in my Github copy of vxl, branch <tt>osx-compile-fixes</tt> [https://github.com/rfabbri/vxl]
* A link time error related to OpenGL acceleration in vgui/tests means this test is outdated and should be ignored. Comment out that file or the offending lines. Alternatively, you could point the OpenGL CMake variables to /opt/... since those opengl libs contain the desired symbols, but they're older.
* The above link mentions a OPENJPEG2 work around
* '''See also''': [[Mac|General OSX-related development instructions]]

== Writing a program that uses VXL ==

A simple example using CMake is <tt>hello-vxl</tt>:
git clone ssh://SOURCEFORGE_LOGIN@labmacambira.git.sourceforge.net/gitroot/labmacambira/hello-vxl

Read the README.

== Setting up VxL Programming environment at [[IPRJ]] ==
This is Ricardo Fabbri's recommended workflow for working with the official VXL plus an internal repo (here named LEMSVXL)

* download vxl git
** place it into folder vxlprg/vxl
* we use LEMSVXL - an internal (closed) repo of vxl-based libs from Brown
** download lemsvxl git
** place it into folder vxlprg/lemsvxl
* create build directories lemsvxl-bin and vxl-bin inside vxlprg
mkdir lemsvxl-bin vxlprg-bin
=== Compiling ===
* on the commandline, enter vxl-bin
* type
ccmake ../vxl
* type 'c' for "configure"
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
at first BUILD_VGUI = OFF
CMAKE_BUILD_TYPE = Debug (for now)
* type 'c' once more
* inspect any CMAKE variables that might have changed (they have a star * attached to them)
* type 'c' again until no new variables show up and config is right
* once 'g' appears, press 'g' (generate)
* press 'q'
* type 'make -j9'
* if there is any error:
** retry with simply 'make'
** test your build
*** go inside 'core' and type 'make'. See if there are any errors. If not, good.
*** go inside contrib/brl and type 'make'. See if there are any errors. If so, you might not be able to build what you want from the internal lemsvxl repo. But keep going, at least core builds.
*** optionally if there are still errors just do 'make -j9 --keep-going' to
build as much as possible before moving on to your private lemsvxl repo

==== Compiling lemsvxl ====

* enter lemsvxl-bin
* ccmake ../lemsvxl
* Fill in where your vxl-bin folder is as the VXL path, then press 'c', then
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
CMAKE_BUILD_TYPE = Debug (for now)
BUILD_CONTRIB = on (for now)
BUILD_ALGO = on
BUILD_CONTRIB = on
can be usefol to set USE_BOOST
* press 'c' and fill out info until you get a 'g'
* try out a first make -j9 - it will likely have errors
* if it does have errors, just make in your desired path:
** For the symbolic edge linker, for instance, you just need to get 'brcv/seg/dbdet' to compile. All dependencies will be compiled.
*** cd brcv/seg/dbdet/tests
*** make
*** cd brcv/seg/dbdet/algo/tests
*** make
*** cd brcv/seg/dbdet
*** make
** Once you compiled the key basic libs for your application, now move on to compile the GUI parts
** In the case of edge detection:
*** cd contrib/edge_det/gui
*** make
*** backtrack and compile each lib separately to solve problems.
* April 4 2014: I had to comment out anything related to bvis1_gl_codec, and vidl1, with no apparent harm to my research code
* My current CMake settings to compile LEMSVxL in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-lemsvxl-txt]

== Links ==

* Official website: http://vxl.sourceforge.net
* Our [[Pattern Theory]] course page
* Our [[Computer Vision]] grad and undergrad course page

[[Category:Lab Macambira]]

[[Category:Video]]

VXL

2014-05-28T13:55:01Z

Mamorim: /* Compiling */

VXL is a collection of C++ computer vision libraries (and python bindings) with contributions from Kitware, GE, Brown University, and others. This wiki page contains unofficial notes from some developers.

== Git Repo ==
Folow the instructions at https://sourceforge.net/p/vxl/wiki/Git/

== Hacking ==

=== Apple OSX ===
There are a few bugs affecting compilation, see [https://trac.macports.org/ticket/41241]

* make -j9 is having a non-deterministic behavior - try running it a few times, but make -j5 sometimes works better as far as errors go. A plain make is always safer.
* If you find an error related to ffmpeg, then I just left all FFMPEG-related entries in CMAKE blank. That removes support for video loading but thats about it.
* A compilation error related to X11 means the headers from the wrong place are being used. I had to modify the cmake flag for x11 includes to point to /opt/local/include
* My current CMake settings to compile in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-txt]

==== Patches to compile VXL in OSX ====
In addition to the above measures, a number of source code changes had to be implemented to get VXL to compile.
* All the source code changes I had to do in order to get VXL to compile are available in my Github copy of vxl, branch <tt>osx-compile-fixes</tt> [https://github.com/rfabbri/vxl]
* A link time error related to OpenGL acceleration in vgui/tests means this test is outdated and should be ignored. Comment out that file or the offending lines. Alternatively, you could point the OpenGL CMake variables to /opt/... since those opengl libs contain the desired symbols, but they're older.
* The above link mentions a OPENJPEG2 work around
* '''See also''': [[Mac|General OSX-related development instructions]]

== Writing a program that uses VXL ==

A simple example using CMake is <tt>hello-vxl</tt>:
git clone ssh://SOURCEFORGE_LOGIN@labmacambira.git.sourceforge.net/gitroot/labmacambira/hello-vxl

Read the README.

== Setting up VxL Programming environment at [[IPRJ]] ==
This is Ricardo Fabbri's recommended workflow for working with the official VXL plus an internal repo (here named LEMSVXL)

* download vxl git
** place it into folder vxlprg/vxl
* we use LEMSVXL - an internal (closed) repo of vxl-based libs from Brown
** download lemsvxl git
** place it into folder vxlprg/lemsvxl
* create build directories lemsvxl-bin and vxl-bin inside vxlprg
mkdir lemsvxl-bin vxlprg-bin
=== Compiling ===
* on the commandline, enter vxl-bin
* type
ccmake ../vxl
* type 'c' for "configure"
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
at first BUILD_VGUI = OFF
CMAKE_BUILD_TYPE = Debug (for now)
* type 'c' once more
* inspect any CMAKE variables that might have changed (they have a star * attached to them)
* type 'c' again until no new variables show up and config is right
* once 'g' appears, press 'g' (generate)
* press 'q'
* type 'make -j9'
* if there is any error:
** retry with simply 'make'
** test your build
*** go inside 'core' and type 'make'. See if there are any errors. If not, good.
*** go inside contrib/brl and type 'make'. See if there are any errors. If so, you might not be able to build what you want from the internal lemsvxl repo. But keep going, at least core builds.
*** optionally if there are still errors just do 'make -j9 --keep-going' to
build as much as possible before moving on to your private lemsvxl repo

==== Compiling lemsvxl ====

* enter lemsvxl-bin
* ccmake ../lemsvxl
* Fill in where your vxl-bin folder is as the VXL path, then press 'c', then
BUILD_SHARED_LIBS = ON (faster link time)
BUILD_UNMAINTAINED_LIBRARIES = ON
CMAKE_BUILD_TYPE = Debug (for now)
BUILD_CONTRIB = on (for now)
BUILD_ALGO = on
BUILD_CONTRIB = on
VNL_CONFIG_LEGACY_METHODS = on
can be usefol to set USE_BOOST
* press 'c' and fill out info until you get a 'g'
* try out a first make -j9 - it will likely have errors
* if it does have errors, just make in your desired path:
** For the symbolic edge linker, for instance, you just need to get 'brcv/seg/dbdet' to compile. All dependencies will be compiled.
*** cd brcv/seg/dbdet/tests
*** make
*** cd brcv/seg/dbdet/algo/tests
*** make
*** cd brcv/seg/dbdet
*** make
** Once you compiled the key basic libs for your application, now move on to compile the GUI parts
** In the case of edge detection:
*** cd contrib/edge_det/gui
*** make
*** backtrack and compile each lib separately to solve problems.
* April 4 2014: I had to comment out anything related to bvis1_gl_codec, and vidl1, with no apparent harm to my research code
* My current CMake settings to compile LEMSVxL in OSX are available on-line [https://gist.github.com/rfabbri/d0d6dc19cffef50aea60#file-cmakecache-lemsvxl-txt]

== Links ==

* Official website: http://vxl.sourceforge.net
* Our [[Pattern Theory]] course page
* Our [[Computer Vision]] grad and undergrad course page

[[Category:Lab Macambira]]

[[Category:Video]]