From linus.sherrill at kitware.com Mon Aug 29 22:56:06 2016 From: linus.sherrill at kitware.com (Linus Sherrill) Date: Mon, 29 Aug 2016 22:56:06 -0400 Subject: [Viame] Announcing the early availability of the VIAME toolkit Message-ID: VIAME is a processing framework designed to integrate image and video processing algorithms in a flexible processing framework. The core infrastructure connecting different system components is currently supplied by the KWIVER library by the Vital algorithm framework and the sprokit pipeline framework. VIAME is an SDK intended to be an integration platform for assembling analytical tools composed of modules from a wide variety of sources. Using the sprokit data flow approach, data sources, image processing, detectors, and analyzers can be easily integrated from different organizations. Algorithms and processes can be developed independently as stand-alone modules (libraries) that are discovered and loaded at run time. This dynamic approach reduces coupling between customer code bases and facilitates easy sharing of these modules without requiring each user to rebuild them from the original source. *Getting the software* VIAME itself can be built either as a super-build, which builds all of its dependencies alongside itself, or standalone. By default it is a superbuild so all major dependencies are built into the VIAME project. To build ViAME: git clone https://github.com/Kitware/VIAME.git The build instructions can be found in the documentation directory: VIAME/doc/install_guide.rst There are currently several cmake options to VIAME, such as "VIAME_ENABLE_MATLAB", "VIAME_ENABLE_OPENCV", "VIAME_ENABLE_VXL", and "VIAME_ENABLE_CAFFE" to turn on support for different components. It is generally a good idea to enable most all of these options to assure that all KIWVER based components are available. If a package based option is not enabled, then the functionality that depends on that package will not be available from KWIVER or for your project. The options can be set on the cmake command line or interactively selected using the ccmake program. *Using the VIAME toolkit* The VIAME toolkit provides an environment to support data processing algorithms such as image filters and detectors. There is a introductory tutorial on how to create an object detector in the file "VIAME/doc/detector-introduction.rst". This tutorial steps through creating a basic detector algorithm and then wraps that detector in a sprokit process. With the VIAME toolkit, you should be able to wrap existing image processing and detection algorithms so they can be easily assembled and reconfigured to solve existing and new image based problems. In addition to the tutorial, there is a wrapped SCALLOP-TK detector to serve as an example of how an external package are added to VIAME and how they can be wrapped. This also serves as an example for how inputs and outputs are converted. The current VIAME toolkit contains some basic support for running Matlab code as a detector and image filter. Matlab support will evolve to meet the needs of the community. In anticipation of the pre-hackathon teleconference to be held on Wednesday at 1PM EDT, we'd like participating organizations to prepare a single slide outlining their technology, their goals for the hackathon and other useful information as outlined in the following PowerPoint template: http://www.viametoolkit.org/wp-content/uploads/2016/08/VIAME _Hackathon_Quad_Template.pptx To facilitate the meeting, please provide us your slide by noon on Wednesday so that we can aggregate them and make them available for the meeting. -- *Linus Sherrill - *Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthony.hoogs at kitware.com Tue Aug 30 15:30:18 2016 From: anthony.hoogs at kitware.com (Anthony Hoogs) Date: Tue, 30 Aug 2016 15:30:18 -0400 Subject: [Viame] Announcing the early availability of the VIAME toolkit In-Reply-To: References: Message-ID: <01f001d202f4$f19ade60$d4d09b20$@kitware.com> Note the action for hackathon participants at the end of the email: In anticipation of the pre-hackathon teleconference to be held on Wednesday at 1PM EDT, we'd like participating organizations to prepare a single slide outlining their technology, their goals for the hackathon and other useful information as outlined in the following PowerPoint template: http://www.viametoolkit.org/wp-content/uploads/2016/08/VIAME_Hackathon_Quad_Template.pptx To facilitate the meeting, please provide us your slide by noon on Wednesday so that we can aggregate them and make them available for the meeting. Anthony From: Viame [mailto:viame-bounces at public.kitware.com] On Behalf Of Linus Sherrill Sent: Monday, August 29, 2016 10:56 PM To: viame at public.kitware.com Subject: [Viame] Announcing the early availability of the VIAME toolkit VIAME is a processing framework designed to integrate image and video processing algorithms in a flexible processing framework. The core infrastructure connecting different system components is currently supplied by the KWIVER library by the Vital algorithm framework and the sprokit pipeline framework. VIAME is an SDK intended to be an integration platform for assembling analytical tools composed of modules from a wide variety of sources. Using the sprokit data flow approach, data sources, image processing, detectors, and analyzers can be easily integrated from different organizations. Algorithms and processes can be developed independently as stand-alone modules (libraries) that are discovered and loaded at run time. This dynamic approach reduces coupling between customer code bases and facilitates easy sharing of these modules without requiring each user to rebuild them from the original source. Getting the software VIAME itself can be built either as a super-build, which builds all of its dependencies alongside itself, or standalone. By default it is a superbuild so all major dependencies are built into the VIAME project. To build ViAME: git clone https://github.com/Kitware/VIAME.git The build instructions can be found in the documentation directory: VIAME/doc/install_guide.rst There are currently several cmake options to VIAME, such as "VIAME_ENABLE_MATLAB", "VIAME_ENABLE_OPENCV", "VIAME_ENABLE_VXL", and "VIAME_ENABLE_CAFFE" to turn on support for different components. It is generally a good idea to enable most all of these options to assure that all KIWVER based components are available. If a package based option is not enabled, then the functionality that depends on that package will not be available from KWIVER or for your project. The options can be set on the cmake command line or interactively selected using the ccmake program. Using the VIAME toolkit The VIAME toolkit provides an environment to support data processing algorithms such as image filters and detectors. There is a introductory tutorial on how to create an object detector in the file "VIAME/doc/detector-introduction.rst". This tutorial steps through creating a basic detector algorithm and then wraps that detector in a sprokit process. With the VIAME toolkit, you should be able to wrap existing image processing and detection algorithms so they can be easily assembled and reconfigured to solve existing and new image based problems. In addition to the tutorial, there is a wrapped SCALLOP-TK detector to serve as an example of how an external package are added to VIAME and how they can be wrapped. This also serves as an example for how inputs and outputs are converted. The current VIAME toolkit contains some basic support for running Matlab code as a detector and image filter. Matlab support will evolve to meet the needs of the community. In anticipation of the pre-hackathon teleconference to be held on Wednesday at 1PM EDT, we'd like participating organizations to prepare a single slide outlining their technology, their goals for the hackathon and other useful information as outlined in the following PowerPoint template: http://www.viametoolkit.org/wp-content/uploads/2016/08/VIAME_Hackathon_Quad_Template.pptx To facilitate the meeting, please provide us your slide by noon on Wednesday so that we can aggregate them and make them available for the meeting. -- Linus Sherrill - Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthony.hoogs at kitware.com Tue Aug 30 18:41:15 2016 From: anthony.hoogs at kitware.com (Anthony Hoogs) Date: Tue, 30 Aug 2016 18:41:15 -0400 Subject: [Viame] FW: Announcing the early availability of the VIAME toolkit In-Reply-To: <29A60D49-5515-4322-B32F-EC072A50BE5D@noaa.gov> References: <018201d202dd$a164c710$e42e5530$@kitware.com> <29A60D49-5515-4322-B32F-EC072A50BE5D@noaa.gov> Message-ID: <024c01d2030f$9e7a3e90$db6ebbb0$@kitware.com> Hackathon attendees, see info on the hackathon preparation teleconference tomorrow. Please attend if you can, and note the action at the end to provide a quad chart describing your hackathon goals. Thanks, Anthony From: Benjamin Richards - NOAA Federal [mailto:benjamin.richards at noaa.gov] Sent: Tuesday, August 30, 2016 5:48 PM To: Anthony Hoogs Cc: Elizabeth Clarke; George Cutter; Kresimir Williams; Scott Gallager; Deborah Hart; Lakshman Prasad; Michael Piacentino; Bill Michaels; Charles H. Thompson; Duane Edgington; Alexandra Branzan Albu; David Kriegman; Clay Kunz; keith.fieldhouse at kitware.com; Linus Sherrill; matt.dawkins at kitware.com Subject: Re: [Viame] Announcing the early availability of the VIAME toolkit Thanks Anthony - As a reminder, we have setup a WebEx portal for this tcon. The meeting information is as follows: Meeting number: 998 625 492 Meeting password:noaa Meeting link: https://noaa-meets.webex.com/noaa-meets/j.php?MTID=mac5fe56b34afe601508a749f7f924388 Audio connection: Call-in: 1-866-764-5737 Participants code: 880411 ~ben <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< Benjamin L. Richards, PhD Research Fishery Biologist Lead Survey Scientist Stock Assessment Program Pacific Islands Fisheries Science Center NOAA, Inouye Regional Center 1845 Wasp Blvd., Bldg. #176 Honolulu, HI 96818 phone: 808-725-5320 cell: 808-782-1734 http://www.pifsc.noaa.gov/fbsab/ benjamin.richards at noaa.gov Recent publications "Discovery consists of seeing what everybody has seen and thinking what nobody has thought." - Albert Szent-Gyorgyi - The views expressed in this message are my own and do not necessarily reflect any position of NOAA, the Department of Commerce, or the government of the United States. On Aug 30, 2016, at 6:43 AM, Anthony Hoogs wrote: The VIAME toolkit was officially released yesterday, per the email below sent to the VIAME mailing list. Currently this list includes the hackathon attendees, so most of you should have received the announcement directly. If you?d like to join the list, please send me an email. We?ll present an overview of the VIAME software and how to install it in the teleconference tomorrow. Anthony From: Viame [ mailto:viame-bounces at public.kitware.com] On Behalf Of Linus Sherrill Sent: Monday, August 29, 2016 10:56 PM To: viame at public.kitware.com Subject: [Viame] Announcing the early availability of the VIAME toolkit VIAME is a processing framework designed to integrate image and video processing algorithms in a flexible processing framework. The core infrastructure connecting different system components is currently supplied by the KWIVER library by the Vital algorithm framework and the sprokit pipeline framework. VIAME is an SDK intended to be an integration platform for assembling analytical tools composed of modules from a wide variety of sources. Using the sprokit data flow approach, data sources, image processing, detectors, and analyzers can be easily integrated from different organizations. Algorithms and processes can be developed independently as stand-alone modules (libraries) that are discovered and loaded at run time. This dynamic approach reduces coupling between customer code bases and facilitates easy sharing of these modules without requiring each user to rebuild them from the original source. Getting the software VIAME itself can be built either as a super-build, which builds all of its dependencies alongside itself, or standalone. By default it is a superbuild so all major dependencies are built into the VIAME project. To build ViAME: git clone https://github.com/Kitware/VIAME.git The build instructions can be found in the documentation directory: VIAME/doc/install_guide.rst There are currently several cmake options to VIAME, such as "VIAME_ENABLE_MATLAB", "VIAME_ENABLE_OPENCV", "VIAME_ENABLE_VXL", and "VIAME_ENABLE_CAFFE" to turn on support for different components. It is generally a good idea to enable most all of these options to assure that all KIWVER based components are available. If a package based option is not enabled, then the functionality that depends on that package will not be available from KWIVER or for your project. The options can be set on the cmake command line or interactively selected using the ccmake program. Using the VIAME toolkit The VIAME toolkit provides an environment to support data processing algorithms such as image filters and detectors. There is a introductory tutorial on how to create an object detector in the file "VIAME/doc/detector-introduction.rst". This tutorial steps through creating a basic detector algorithm and then wraps that detector in a sprokit process. With the VIAME toolkit, you should be able to wrap existing image processing and detection algorithms so they can be easily assembled and reconfigured to solve existing and new image based problems. In addition to the tutorial, there is a wrapped SCALLOP-TK detector to serve as an example of how an external package are added to VIAME and how they can be wrapped. This also serves as an example for how inputs and outputs are converted. The current VIAME toolkit contains some basic support for running Matlab code as a detector and image filter. Matlab support will evolve to meet the needs of the community. In anticipation of the pre-hackathon teleconference to be held on Wednesday at 1PM EDT, we'd like participating organizations to prepare a single slide outlining their technology, their goals for the hackathon and other useful information as outlined in the following PowerPoint template: http://www.viametoolkit.org/wp-content/uploads/2016/08/VIAME_Hackathon_Quad_Template.pptx To facilitate the meeting, please provide us your slide by noon on Wednesday so that we can aggregate them and make them available for the meeting. -- Linus Sherrill - Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith.fieldhouse at kitware.com Wed Aug 31 12:46:21 2016 From: keith.fieldhouse at kitware.com (Keith Fieldhouse) Date: Wed, 31 Aug 2016 12:46:21 -0400 Subject: [Viame] Slides for Today's T-Con Message-ID: Folks, I've placed the slides for today's t-con at http://www.viametoolkit.org/wp-content/uploads/2016/08/VIAME_Hackathon_Day0_Kickoff.pptx Having them should serve as a backup in case you have difficulty with the WebEx connection. I'm looking forward to speaking with you all. Keith -- Keith Fieldhouse Assistant Director of Computer Vision Kitware, Inc. E-mail: keith.fieldhouse at kitware.com Phone: (518) 836-2190 -------------- next part -------------- An HTML attachment was scrubbed... URL: From benjamin.richards at noaa.gov Wed Aug 31 14:09:13 2016 From: benjamin.richards at noaa.gov (Benjamin Richards - NOAA Federal) Date: Wed, 31 Aug 2016 08:09:13 -1000 Subject: [Viame] VIAME build error Message-ID: <05698F46-2992-4F26-AE68-0D249ED702BC@noaa.gov> from Randy Cutter (george.cutter at noaa.gov ) > I cloned VIAME repository using git. > > Updated submodules using git. > > Used CMake to create Visual Studio solution. > > But when I tried to build the VS solution/projects, it seeks to download various dependency sources. However, on my build machine is not connected to the internet and cannot access them, therefore I get errors. > > Is it possible to convince git, CMake or some other process to download the necessary dependency sources; perhaps CMake can include them in the VS solution? ~ben <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< Benjamin L. Richards, PhD Research Fishery Biologist Lead Survey Scientist Stock Assessment Program Pacific Islands Fisheries Science Center NOAA, Inouye Regional Center 1845 Wasp Blvd., Bldg. #176 Honolulu, HI 96818 phone: 808-725-5320 cell: 808-782-1734 http://www.pifsc.noaa.gov/fbsab/ benjamin.richards at noaa.gov Recent publications "Discovery consists of seeing what everybody has seen and thinking what nobody has thought." - Albert Szent-Gyorgyi - The views expressed in this message are my own and do not necessarily reflect any position of NOAA, the Department of Commerce, or the government of the United States. -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.zhang at sri.com Wed Aug 31 14:47:58 2016 From: david.zhang at sri.com (David Zhang) Date: Wed, 31 Aug 2016 18:47:58 +0000 Subject: [Viame] VIAME build error Message-ID: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com> Hi: This is David Zhang from SRI. I followed the instruction online and cloned VIAME to my laptop running 64-bit Ubuntu 14.04. I encountered building errors which I pasted a small section below: : david at M6700:~/projects/VIAME/build$ make -j8 [ 7%] Removing build stamp file for build update (forcebuild). [ 7%] Performing build step for 'fletch' [ 6%] Performing download step (download, verify and extract) for 'Snappy' [ 6%] Performing download step (download, verify and extract) for 'LMDB' [ 6%] Performing download step (download, verify and extract) for 'Protobuf' [ 6%] Performing download step (download, verify and extract) for 'GLog' [ 6%] Performing download step (download, verify and extract) for 'OpenBLAS' [ 6%] Performing download step (download, verify and extract) for 'ZLib' [ 6%] Built target OpenCV [ 6%] Performing download step (download, verify and extract) for 'Boost' -- downloading... src='https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/snappy-1.1.3.tar.gz' timeout='none' CMake Error at Snappy-stamp/download-Snappy.cmake:27 (message): error: downloading 'https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' failed status_code: 1 status_string: "Unsupported protocol" log: Protocol "https" not supported or disabled in libcurl Closing connection -1 -- downloading... src='https://github.com/google/glog/archive/v0.3.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.3.3.tar.gz' timeout='none' -- downloading... src='https://github.com/xianyi/OpenBLAS/archive/v0.2.15.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.2.15.tar.gz' timeout='none' make[5]: *** [build/src/Snappy-stamp/Snappy-download] Error 1 .............................................................................................................. I checked VIAME/packages/fletch/Downloads, I think all the third-party package downloads were successful. However, cmake setup still looks for these websites to downloading. The network connections were complained by the make build. I have not looked into CMake settings. If you find sometime useful, please let me know. By the way, from the make build, I am able to build opencv. It seems like just some downloaded packages were not able to build. Another question is: are all the built package, including VIAME, locally installed? I have other versions of opencv, eigen, boost and protobuf which are installed globally. I guess there is no conflict with these already installed packages from the VIAME. Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcline at mbari.org Wed Aug 31 15:06:38 2016 From: dcline at mbari.org (Danelle Cline) Date: Wed, 31 Aug 2016 12:06:38 -0700 Subject: [Viame] VIAME Docker build Message-ID: <2BF3ECA0-1505-4459-8BEF-D943F4B7B22B@mbari.org> Hi fellow developers, If you don?t use Docker, please disregard this message. If you do use Docker, FYI the following instructions in a Dockerfile work. You can probably use a newer version of ubuntu, but we need this one for our software: FROM ubuntu:15.04 MAINTAINER Danelle Cline # Install RUN \ apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git cmake g++ && \ apt-get clean # Check out VIAME and build WORKDIR /code RUN git clone https://github.com/Kitware/VIAME.git WORKDIR /code/VIAME/ RUN git submodule update --init RUN cmake -DCMAKE_BUILD_TYPE:STRING=Release /code/VIAME -Danelle Danelle Cline Software Engineer Monterey Bay Aquarium Research Institute 7700 Sandholdt Road Moss Landing, California 95039 831 775 1947; 831 775 1652 (fax) www.mbari.org; www.mbari.org/staff/dcline -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith.fieldhouse at kitware.com Wed Aug 31 15:19:02 2016 From: keith.fieldhouse at kitware.com (Keith Fieldhouse) Date: Wed, 31 Aug 2016 15:19:02 -0400 Subject: [Viame] VIAME Docker build In-Reply-To: <2BF3ECA0-1505-4459-8BEF-D943F4B7B22B@mbari.org> References: <2BF3ECA0-1505-4459-8BEF-D943F4B7B22B@mbari.org> Message-ID: Danelle, Nice. Thanks for this. Do you have any objection if we add this as a Dockerfile to the repo? To the list at large: would there be interest in a Vagrantfile as well? Keith On Wed, Aug 31, 2016 at 3:06 PM, Danelle Cline wrote: > Hi fellow developers, > > If you don?t use Docker, please disregard this message. > > If you do use Docker, FYI the following instructions in a Dockerfile work. > You can probably use a newer version of ubuntu, but we need this one for > our software: > > FROM ubuntu:15.04 > MAINTAINER Danelle Cline > > # Install > RUN \ > apt-get update -y && \ > apt-get upgrade -y && \ > apt-get install -y git cmake g++ && \ > apt-get clean > > > # Check out VIAME and build > WORKDIR /code > RUN git clone https://github.com/Kitware/VIAME.git > WORKDIR /code/VIAME/ > RUN git submodule update --init > RUN cmake -DCMAKE_BUILD_TYPE:STRING=Release /code/VIAME > > > -Danelle > > Danelle Cline > Software Engineer > Monterey Bay Aquarium Research Institute > 7700 Sandholdt Road > Moss Landing, California 95039 > 831 775 1947; 831 775 1652 (fax) > www.mbari.org; www.mbari.org/staff/dcline > > > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame > > -- Keith Fieldhouse Assistant Director of Computer Vision Kitware, Inc. E-mail: keith.fieldhouse at kitware.com Phone: (518) 836-2190 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcline at mbari.org Wed Aug 31 15:27:23 2016 From: dcline at mbari.org (Danelle Cline) Date: Wed, 31 Aug 2016 12:27:23 -0700 Subject: [Viame] VIAME Docker build In-Reply-To: References: <2BF3ECA0-1505-4459-8BEF-D943F4B7B22B@mbari.org> Message-ID: > Nice. Thanks for this. Do you have any objection if we add this as a Dockerfile to the repo? No problem at all. > On Aug 31, 2016, at 12:19 PM, Keith Fieldhouse wrote: > > Danelle, > > Nice. Thanks for this. Do you have any objection if we add this as a Dockerfile to the repo? > > To the list at large: would there be interest in a Vagrantfile as well? > > Keith > > On Wed, Aug 31, 2016 at 3:06 PM, Danelle Cline > wrote: > Hi fellow developers, > > If you don?t use Docker, please disregard this message. > > If you do use Docker, FYI the following instructions in a Dockerfile work. You can probably use a newer version of ubuntu, but we need this one for our software: > > FROM ubuntu:15.04 > MAINTAINER Danelle Cline > > > # Install > RUN \ > apt-get update -y && \ > apt-get upgrade -y && \ > apt-get install -y git cmake g++ && \ > apt-get clean > > > # Check out VIAME and build > WORKDIR /code > RUN git clone https://github.com /Kitware/VIAME.git > WORKDIR /code/VIAME/ > RUN git submodule update --init > RUN cmake -DCMAKE_BUILD_TYPE:STRING=Release /code/VIAME > > -Danelle > > Danelle Cline > Software Engineer > Monterey Bay Aquarium Research Institute > 7700 Sandholdt Road > Moss Landing, California 95039 > 831 775 1947 ; 831 775 1652 (fax) > www.mbari.org ; www.mbari.org/staff/dcline > > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame > > > > > -- > Keith Fieldhouse > Assistant Director of Computer Vision > Kitware, Inc. > E-mail: keith.fieldhouse at kitware.com > Phone: (518) 836-2190 -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.dawkins at kitware.com Wed Aug 31 15:30:02 2016 From: matt.dawkins at kitware.com (Matt Dawkins) Date: Wed, 31 Aug 2016 15:30:02 -0400 Subject: [Viame] VIAME build error In-Reply-To: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com> References: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com> Message-ID: Are the downloaded packages for snappy approximately 0 or 1 bytes? Can you click the above link and download the package in a browser on the same computer? If the answer is yes and yes, this is probably an issue of using a cmake not built with ssl support, and failing on all https links. Install openssl-devel (or -dev) from your package manager, and rebuild cmake with CMAKE_USE_OPENSSL=ON. Depending on your package manager on linux version, this may or may not have been done in your installed system cmake. If that's not the solution it might be a libcurl issue. I'll add a blurb about this on the build instructions. As for the second question, all of the packages built within VIAME are not installed globally, so they should not mess up any existing build setups. They are installed into [viame_build_dir]/install. There might still be some lingering issues with certain subpackages in VIAME picking up your system libraries instead of ones in the internal build, however, but we're trying to reduce these as possible so that it's a self contained environment. If you want to build all of the dependencies yourself (or alternatively, use installed system libraries) you can also set VIAME_BUILD_DEPENDENCIES=OFF, in which case you will need to manually build KWIVER and VIAME by pointing them both to the required libraries on your computer if they are not auto-detected. Best, Matt D. On Wed, Aug 31, 2016 at 2:47 PM, David Zhang wrote: > Hi: > > > > This is David Zhang from SRI. I followed the instruction online and cloned > VIAME to my laptop running 64-bit Ubuntu 14.04. > > > > I encountered building errors which I pasted a small section below: > > : > > david at M6700:~/projects/VIAME/build$ make -j8 > > [ 7%] Removing build stamp file for build update (forcebuild). > > [ 7%] Performing build step for 'fletch' > > [ 6%] Performing download step (download, verify and extract) for 'Snappy' > > [ 6%] Performing download step (download, verify and extract) for 'LMDB' > > [ 6%] Performing download step (download, verify and extract) for > 'Protobuf' > > [ 6%] Performing download step (download, verify and extract) for 'GLog' > > [ 6%] Performing download step (download, verify and extract) for > 'OpenBLAS' > > [ 6%] Performing download step (download, verify and extract) for 'ZLib' > > [ 6%] Built target OpenCV > > [ 6%] Performing download step (download, verify and extract) for 'Boost' > > -- downloading... > > src='https://github.com/google/snappy/releases/ > download/1.1.3/snappy-1.1.3.tar.gz' > > dst='/home/david/projects/VIAME/packages/fletch/ > Downloads/snappy-1.1.3.tar.gz' > > timeout='none' > > CMake Error at Snappy-stamp/download-Snappy.cmake:27 (message): > > error: downloading > > 'https://github.com/google/snappy/releases/download/1.1. > 3/snappy-1.1.3.tar.gz' > > failed > > > > status_code: 1 > > status_string: "Unsupported protocol" > > log: Protocol "https" not supported or disabled in libcurl > > > > Closing connection -1 > > > > -- downloading... > > src='https://github.com/google/glog/archive/v0.3.3.tar.gz' > > dst='/home/david/projects/VIAME/packages/fletch/ > Downloads/v0.3.3.tar.gz' > > timeout='none' > > -- downloading... > > src='https://github.com/xianyi/OpenBLAS/archive/v0.2.15.tar.gz' > > dst='/home/david/projects/VIAME/packages/fletch/ > Downloads/v0.2.15.tar.gz' > > timeout='none' > > make[5]: *** [build/src/Snappy-stamp/Snappy-download] Error 1 > > ............................................................ > .................................................. > > > > I checked VIAME/packages/fletch/Downloads, I think all the third-party > package downloads were successful. However, cmake setup still looks for > these websites to downloading. The network connections were complained by > the make build. I have not looked into CMake settings. If you find sometime > useful, please let me know. > > > > By the way, from the make build, I am able to build opencv. It seems like > just some downloaded packages were not able to build. > > > > Another question is: are all the built package, including VIAME, locally > installed? I have other versions of opencv, eigen, boost and protobuf which > are installed globally. I guess there is no conflict with these already > installed packages from the VIAME. > > > > Thanks, > > > > David > > > > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame > > -- Matthew Dawkins 1-518-881-4416 Senior R&D Engineer Kitware, Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: From duane at mbari.org Wed Aug 31 16:14:39 2016 From: duane at mbari.org (Duane Edgington) Date: Wed, 31 Aug 2016 13:14:39 -0700 Subject: [Viame] Slides for Today's T-Con In-Reply-To: References: Message-ID: <6FE038C9-7618-4F70-8668-1CEC16F72310@mbari.org> Colleagues, Sorry for the chatter. Danelle points out I messed up the link to AVED in the MBARI Quadrant slide It should be https://bitbucket.org/mbari/avedac The one I had put in was a link to a user?s fork? Look forward to seeing most of you in September! Duane Edgington > On Aug 31, 2016, at 9:46 AM, Keith Fieldhouse wrote: > > Folks, > > I've placed the slides for today's t-con at > > http://www.viametoolkit.org/wp-content/uploads/2016/08/VIAME_Hackathon_Day0_Kickoff.pptx > > Having them should serve as a backup in case you have difficulty with the WebEx connection. > > I'm looking forward to speaking with you all. > > Keith > > -- > Keith Fieldhouse > Assistant Director of Computer Vision > Kitware, Inc. > E-mail: keith.fieldhouse at kitware.com > Phone: (518) 836-2190 > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.dawkins at kitware.com Wed Aug 31 16:35:32 2016 From: matt.dawkins at kitware.com (Matt Dawkins) Date: Wed, 31 Aug 2016 16:35:32 -0400 Subject: [Viame] VIAME build error In-Reply-To: <05698F46-2992-4F26-AE68-0D249ED702BC@noaa.gov> References: <05698F46-2992-4F26-AE68-0D249ED702BC@noaa.gov> Message-ID: In hopes of keeping the repository small, and only pulling down dependencies which are required, VIAME only downloads and builds dependencies based on which enable flags are set (e.g. VIAME_ENABLE_OPENCV, VXL, CAFFE, SCALLOP_TK, [future modules here], etc...). To that end, it currently requires an internet connection the first time you build it or change enable flags to something that was never enabled before, though for Randy I'd envision us also putting up a tarbell/zip online that contains the source code for all possible dependencies (as well as Viame) in case the user wants to download the package once, then work offline. This could be done for periodic releases, though we'll have to discuss a little bit more first and check if that's the best solution longer term (short term for today, we'll post the standalone code package online with a link; note it is ~220mb with everything included, or 50mb for the core package with few of the enable options set). This will get a little bit more complicated down the line when you are talking about optional algorithm repositories (e.g. ENABLE_detector_1_from_group_a) which can contain model files that often large, think CNN classifiers which can be 100mb+ each, though they could be supplied separately in another tarbell. Also, looking a little further down the road here, we can probably provide compiled binaries as well (and automate their creation online), in case the user simply wants to link to the entire library or run something in it. On Wed, Aug 31, 2016 at 2:09 PM, Benjamin Richards - NOAA Federal < benjamin.richards at noaa.gov> wrote: > from Randy Cutter (george.cutter at noaa.gov) > > I cloned VIAME repository using git. > > Updated submodules using git. > > Used CMake to create Visual Studio solution. > > But when I tried to build the VS solution/projects, it seeks to download > various dependency sources. However, on my build machine is not connected > to the internet and cannot access them, therefore I get errors. > > Is it possible to convince git, CMake or some other process to download > the necessary dependency sources; perhaps CMake can include them in the VS > solution? > > > > ~ben > > <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< <>< > > *Benjamin L. Richards, PhD* > *Research Fishery Biologist* > *Lead Survey Scientist* > *Stock Assessment Program* > *Pacific Islands Fisheries Science Center* > *NOAA, Inouye Regional Center* > *1845 Wasp Blvd., Bldg. #176* > *Honolulu, HI 96818* > > *phone: 808-725-5320 <808-725-5320>* > *cell: 808-782-1734 <808-782-1734>* > > http://www.pifsc.noaa.gov/fbsab/ > benjamin.richards at noaa.gov > > Recent publications > > > "Discovery consists of seeing what everybody has seen and thinking what > nobody has thought." > - Albert Szent-Gyorgyi - > > The views expressed in this message are my own and do not necessarily > reflect any position of NOAA, the Department of Commerce, or the government > of the United States. > > > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame > > -- Matthew Dawkins 1-518-881-4416 Senior R&D Engineer Kitware, Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.zhang at sri.com Wed Aug 31 17:17:35 2016 From: david.zhang at sri.com (David Zhang) Date: Wed, 31 Aug 2016 21:17:35 +0000 Subject: [Viame] VIAME build error In-Reply-To: References: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com>, Message-ID: <34989D50-9FA8-40DD-8F36-A10BF7DF37C8@sri.com> Matt: Thanks for your quick response. I did try to build cmake with OpenSSL, however, that does not solve the problem. Snappy and other complained packages are all with zero byte downloaded. I took the link to the website using web browser to download, most of them are successfully downloaded, and at least one link is not longer available: Protobuf.googlecode.com/files/protobuf-2.5.0.tar2.b2 This causes the Downloading fail (one of the reasons). The other modules that I downloaded do not match the exact names that showed up in the Download folder. I have to rename them to match with the configuration. So this is what I have got so far. I suggest you take a look at these links and let us now if my find is correct. Thanks, David On Aug 31, 2016, at 3:29 PM, Matt Dawkins > wrote: Are the downloaded packages for snappy approximately 0 or 1 bytes? Can you click the above link and download the package in a browser on the same computer? If the answer is yes and yes, this is probably an issue of using a cmake not built with ssl support, and failing on all https links. Install openssl-devel (or -dev) from your package manager, and rebuild cmake with CMAKE_USE_OPENSSL=ON. Depending on your package manager on linux version, this may or may not have been done in your installed system cmake. If that's not the solution it might be a libcurl issue. I'll add a blurb about this on the build instructions. As for the second question, all of the packages built within VIAME are not installed globally, so they should not mess up any existing build setups. They are installed into [viame_build_dir]/install. There might still be some lingering issues with certain subpackages in VIAME picking up your system libraries instead of ones in the internal build, however, but we're trying to reduce these as possible so that it's a self contained environment. If you want to build all of the dependencies yourself (or alternatively, use installed system libraries) you can also set VIAME_BUILD_DEPENDENCIES=OFF, in which case you will need to manually build KWIVER and VIAME by pointing them both to the required libraries on your computer if they are not auto-detected. Best, Matt D. On Wed, Aug 31, 2016 at 2:47 PM, David Zhang > wrote: Hi: This is David Zhang from SRI. I followed the instruction online and cloned VIAME to my laptop running 64-bit Ubuntu 14.04. I encountered building errors which I pasted a small section below: : david at M6700:~/projects/VIAME/build$ make -j8 [ 7%] Removing build stamp file for build update (forcebuild). [ 7%] Performing build step for 'fletch' [ 6%] Performing download step (download, verify and extract) for 'Snappy' [ 6%] Performing download step (download, verify and extract) for 'LMDB' [ 6%] Performing download step (download, verify and extract) for 'Protobuf' [ 6%] Performing download step (download, verify and extract) for 'GLog' [ 6%] Performing download step (download, verify and extract) for 'OpenBLAS' [ 6%] Performing download step (download, verify and extract) for 'ZLib' [ 6%] Built target OpenCV [ 6%] Performing download step (download, verify and extract) for 'Boost' -- downloading... src='https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/snappy-1.1.3.tar.gz' timeout='none' CMake Error at Snappy-stamp/download-Snappy.cmake:27 (message): error: downloading 'https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' failed status_code: 1 status_string: "Unsupported protocol" log: Protocol "https" not supported or disabled in libcurl Closing connection -1 -- downloading... src='https://github.com/google/glog/archive/v0.3.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.3.3.tar.gz' timeout='none' -- downloading... src='https://github.com/xianyi/OpenBLAS/archive/v0.2.15.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.2.15.tar.gz' timeout='none' make[5]: *** [build/src/Snappy-stamp/Snappy-download] Error 1 .............................................................................................................. I checked VIAME/packages/fletch/Downloads, I think all the third-party package downloads were successful. However, cmake setup still looks for these websites to downloading. The network connections were complained by the make build. I have not looked into CMake settings. If you find sometime useful, please let me know. By the way, from the make build, I am able to build opencv. It seems like just some downloaded packages were not able to build. Another question is: are all the built package, including VIAME, locally installed? I have other versions of opencv, eigen, boost and protobuf which are installed globally. I guess there is no conflict with these already installed packages from the VIAME. Thanks, David _______________________________________________ Viame mailing list Viame at public.kitware.com http://public.kitware.com/mailman/listinfo/viame -- Matthew Dawkins 1-518-881-4416 Senior R&D Engineer Kitware, Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: From linus.sherrill at kitware.com Wed Aug 31 17:43:44 2016 From: linus.sherrill at kitware.com (Linus Sherrill) Date: Wed, 31 Aug 2016 17:43:44 -0400 Subject: [Viame] VIAME build error In-Reply-To: <34989D50-9FA8-40DD-8F36-A10BF7DF37C8@sri.com> References: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com> <34989D50-9FA8-40DD-8F36-A10BF7DF37C8@sri.com> Message-ID: David, It is possible that the system is still using the same old cmake binary. You could try running what cmake to see which version is being used. If it is still the old version, you can adjust your PATH to include the new cmake before the system version. We are working on the protobuf problem and will point to the new protobuf tar file. Google updated protobuf on August 25th and changed the old download URL. We will let you know when there is a new version to pull. -Linus On Wed, Aug 31, 2016 at 5:17 PM, David Zhang wrote: > Matt: > > Thanks for your quick response. I did try to build cmake with OpenSSL, > however, that does not solve the problem. > > Snappy and other complained packages are all with zero byte downloaded. I > took the link to the website using web browser to download, most of them > are successfully downloaded, and at least one link is not longer available: > > Protobuf.googlecode.com/files/protobuf-2.5.0.tar2.b2 > > This causes the Downloading fail (one of the reasons). The other modules > that I downloaded do not match the exact names that showed up in the > Download folder. I have to rename them to match with the configuration. > > So this is what I have got so far. I suggest you take a look at these > links and let us now if my find is correct. > > Thanks, > > David > > On Aug 31, 2016, at 3:29 PM, Matt Dawkins > wrote: > > Are the downloaded packages for snappy approximately 0 or 1 bytes? Can you > click the above link and download the package in a browser on the same > computer? > > If the answer is yes and yes, this is probably an issue of using a cmake > not built with ssl support, and failing on all https links. Install > openssl-devel (or -dev) from your package manager, and rebuild cmake with > CMAKE_USE_OPENSSL=ON. Depending on your package manager on linux version, > this may or may not have been done in your installed system cmake. If > that's not the solution it might be a libcurl issue. > > I'll add a blurb about this on the build instructions. > > > As for the second question, all of the packages built within VIAME are not > installed globally, so they should not mess up any existing build setups. > They are installed into [viame_build_dir]/install. There might still be > some lingering issues with certain subpackages in VIAME picking up your > system libraries instead of ones in the internal build, however, but we're > trying to reduce these as possible so that it's a self contained > environment. If you want to build all of the dependencies yourself (or > alternatively, use installed system libraries) you can also set > VIAME_BUILD_DEPENDENCIES=OFF, in which case you will need to manually build > KWIVER and VIAME by pointing them both to the required libraries on your > computer if they are not auto-detected. > > Best, > > Matt D. > > On Wed, Aug 31, 2016 at 2:47 PM, David Zhang wrote: > >> Hi: >> >> >> >> This is David Zhang from SRI. I followed the instruction online and >> cloned VIAME to my laptop running 64-bit Ubuntu 14.04. >> >> >> >> I encountered building errors which I pasted a small section below: >> >> : >> >> david at M6700:~/projects/VIAME/build$ make -j8 >> >> [ 7%] Removing build stamp file for build update (forcebuild). >> >> [ 7%] Performing build step for 'fletch' >> >> [ 6%] Performing download step (download, verify and extract) for >> 'Snappy' >> >> [ 6%] Performing download step (download, verify and extract) for 'LMDB' >> >> [ 6%] Performing download step (download, verify and extract) for >> 'Protobuf' >> >> [ 6%] Performing download step (download, verify and extract) for 'GLog' >> >> [ 6%] Performing download step (download, verify and extract) for >> 'OpenBLAS' >> >> [ 6%] Performing download step (download, verify and extract) for 'ZLib' >> >> [ 6%] Built target OpenCV >> >> [ 6%] Performing download step (download, verify and extract) for 'Boost' >> >> -- downloading... >> >> src='https://github.com/google/snappy/releases/download/1.1. >> 3/snappy-1.1.3.tar.gz' >> >> dst='/home/david/projects/VIAME/packages/fletch/Downloads/ >> snappy-1.1.3.tar.gz' >> >> timeout='none' >> >> CMake Error at Snappy-stamp/download-Snappy.cmake:27 (message): >> >> error: downloading >> >> 'https://github.com/google/snappy/releases/download/1.1.3/ >> snappy-1.1.3.tar.gz' >> >> failed >> >> >> >> status_code: 1 >> >> status_string: "Unsupported protocol" >> >> log: Protocol "https" not supported or disabled in libcurl >> >> >> >> Closing connection -1 >> >> >> >> -- downloading... >> >> src='https://github.com/google/glog/archive/v0.3.3.tar.gz' >> >> dst='/home/david/projects/VIAME/packages/fletch/Downloads/ >> v0.3.3.tar.gz' >> >> timeout='none' >> >> -- downloading... >> >> src='https://github.com/xianyi/OpenBLAS/archive/v0.2.15.tar.gz' >> >> dst='/home/david/projects/VIAME/packages/fletch/Downloads/ >> v0.2.15.tar.gz' >> >> timeout='none' >> >> make[5]: *** [build/src/Snappy-stamp/Snappy-download] Error 1 >> >> ............................................................ >> .................................................. >> >> >> >> I checked VIAME/packages/fletch/Downloads, I think all the third-party >> package downloads were successful. However, cmake setup still looks for >> these websites to downloading. The network connections were complained by >> the make build. I have not looked into CMake settings. If you find sometime >> useful, please let me know. >> >> >> >> By the way, from the make build, I am able to build opencv. It seems like >> just some downloaded packages were not able to build. >> >> >> >> Another question is: are all the built package, including VIAME, locally >> installed? I have other versions of opencv, eigen, boost and protobuf which >> are installed globally. I guess there is no conflict with these already >> installed packages from the VIAME. >> >> >> >> Thanks, >> >> >> >> David >> >> >> >> _______________________________________________ >> Viame mailing list >> Viame at public.kitware.com >> http://public.kitware.com/mailman/listinfo/viame >> >> > > > -- > Matthew Dawkins > 1-518-881-4416 > Senior R&D Engineer > Kitware, Inc > > > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame > > -- *Linus Sherrill - *Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.zhang at sri.com Wed Aug 31 17:55:06 2016 From: david.zhang at sri.com (David Zhang) Date: Wed, 31 Aug 2016 21:55:06 +0000 Subject: [Viame] VIAME build error In-Reply-To: References: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com> <34989D50-9FA8-40DD-8F36-A10BF7DF37C8@sri.com>, Message-ID: <53428D00-F69E-4D77-B4DA-BD17CB399393@sri.com> Linus: I am using cmake 3.4.1. I noticed VIAME suggested 3.6.1. Is the version making a difference? If it is, I can definitely upgrade cmake. Thanks, David On Aug 31, 2016, at 5:43 PM, Linus Sherrill > wrote: David, It is possible that the system is still using the same old cmake binary. You could try running what cmake to see which version is being used. If it is still the old version, you can adjust your PATH to include the new cmake before the system version. We are working on the protobuf problem and will point to the new protobuf tar file. Google updated protobuf on August 25th and changed the old download URL. We will let you know when there is a new version to pull. -Linus On Wed, Aug 31, 2016 at 5:17 PM, David Zhang > wrote: Matt: Thanks for your quick response. I did try to build cmake with OpenSSL, however, that does not solve the problem. Snappy and other complained packages are all with zero byte downloaded. I took the link to the website using web browser to download, most of them are successfully downloaded, and at least one link is not longer available: Protobuf.googlecode.com/files/protobuf-2.5.0.tar2.b2 This causes the Downloading fail (one of the reasons). The other modules that I downloaded do not match the exact names that showed up in the Download folder. I have to rename them to match with the configuration. So this is what I have got so far. I suggest you take a look at these links and let us now if my find is correct. Thanks, David On Aug 31, 2016, at 3:29 PM, Matt Dawkins > wrote: Are the downloaded packages for snappy approximately 0 or 1 bytes? Can you click the above link and download the package in a browser on the same computer? If the answer is yes and yes, this is probably an issue of using a cmake not built with ssl support, and failing on all https links. Install openssl-devel (or -dev) from your package manager, and rebuild cmake with CMAKE_USE_OPENSSL=ON. Depending on your package manager on linux version, this may or may not have been done in your installed system cmake. If that's not the solution it might be a libcurl issue. I'll add a blurb about this on the build instructions. As for the second question, all of the packages built within VIAME are not installed globally, so they should not mess up any existing build setups. They are installed into [viame_build_dir]/install. There might still be some lingering issues with certain subpackages in VIAME picking up your system libraries instead of ones in the internal build, however, but we're trying to reduce these as possible so that it's a self contained environment. If you want to build all of the dependencies yourself (or alternatively, use installed system libraries) you can also set VIAME_BUILD_DEPENDENCIES=OFF, in which case you will need to manually build KWIVER and VIAME by pointing them both to the required libraries on your computer if they are not auto-detected. Best, Matt D. On Wed, Aug 31, 2016 at 2:47 PM, David Zhang > wrote: Hi: This is David Zhang from SRI. I followed the instruction online and cloned VIAME to my laptop running 64-bit Ubuntu 14.04. I encountered building errors which I pasted a small section below: : david at M6700:~/projects/VIAME/build$ make -j8 [ 7%] Removing build stamp file for build update (forcebuild). [ 7%] Performing build step for 'fletch' [ 6%] Performing download step (download, verify and extract) for 'Snappy' [ 6%] Performing download step (download, verify and extract) for 'LMDB' [ 6%] Performing download step (download, verify and extract) for 'Protobuf' [ 6%] Performing download step (download, verify and extract) for 'GLog' [ 6%] Performing download step (download, verify and extract) for 'OpenBLAS' [ 6%] Performing download step (download, verify and extract) for 'ZLib' [ 6%] Built target OpenCV [ 6%] Performing download step (download, verify and extract) for 'Boost' -- downloading... src='https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/snappy-1.1.3.tar.gz' timeout='none' CMake Error at Snappy-stamp/download-Snappy.cmake:27 (message): error: downloading 'https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' failed status_code: 1 status_string: "Unsupported protocol" log: Protocol "https" not supported or disabled in libcurl Closing connection -1 -- downloading... src='https://github.com/google/glog/archive/v0.3.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.3.3.tar.gz' timeout='none' -- downloading... src='https://github.com/xianyi/OpenBLAS/archive/v0.2.15.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.2.15.tar.gz' timeout='none' make[5]: *** [build/src/Snappy-stamp/Snappy-download] Error 1 .............................................................................................................. I checked VIAME/packages/fletch/Downloads, I think all the third-party package downloads were successful. However, cmake setup still looks for these websites to downloading. The network connections were complained by the make build. I have not looked into CMake settings. If you find sometime useful, please let me know. By the way, from the make build, I am able to build opencv. It seems like just some downloaded packages were not able to build. Another question is: are all the built package, including VIAME, locally installed? I have other versions of opencv, eigen, boost and protobuf which are installed globally. I guess there is no conflict with these already installed packages from the VIAME. Thanks, David _______________________________________________ Viame mailing list Viame at public.kitware.com http://public.kitware.com/mailman/listinfo/viame -- Matthew Dawkins 1-518-881-4416 Senior R&D Engineer Kitware, Inc _______________________________________________ Viame mailing list Viame at public.kitware.com http://public.kitware.com/mailman/listinfo/viame -- Linus Sherrill - Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From linus.sherrill at kitware.com Wed Aug 31 18:35:56 2016 From: linus.sherrill at kitware.com (Linus Sherrill) Date: Wed, 31 Aug 2016 18:35:56 -0400 Subject: [Viame] VIAME build error In-Reply-To: <53428D00-F69E-4D77-B4DA-BD17CB399393@sri.com> References: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com> <34989D50-9FA8-40DD-8F36-A10BF7DF37C8@sri.com> <53428D00-F69E-4D77-B4DA-BD17CB399393@sri.com> Message-ID: Judging from your original report of (log: Protocol "https" not supported or disabled in libcurl) the problem may be with the cmake you are using. Usually the cmake that comes with a system distribution has SSL disabled. I have this problem every time a new version is released. You can build a new cmake from downloading the sources from https://cmake.org/files/v3.6/cmake-3.6.1.tar.gz When building thew new cmake, enter the commands $ ./bootstrap $ make" $ cmake -DCMAKE_USE_OPENSSL=ON $ make $ make install (if desired) The problem is that the default cmake options do not include building with OPENSSL which is needed to download external packages using https: protocol. The above commands make a new version of cmake with OPENSSL enabled. A fix has been pushed up that corrects the protobuf download URL. HTH -Linus On Wed, Aug 31, 2016 at 5:55 PM, David Zhang wrote: > Linus: > > I am using cmake 3.4.1. I noticed VIAME suggested 3.6.1. Is the version > making a difference? If it is, I can definitely upgrade cmake. > > Thanks, > > David > > On Aug 31, 2016, at 5:43 PM, Linus Sherrill > wrote: > > David, > > It is possible that the system is still using the same old cmake binary. > You could try running > what cmake > to see which version is being used. If it is still the old version, you > can adjust your PATH to include the new cmake before the system version. > > We are working on the protobuf problem and will point to the new protobuf > tar file. Google updated protobuf on August 25th and changed the old > download URL. > We will let you know when there is a new version to pull. > > -Linus > > On Wed, Aug 31, 2016 at 5:17 PM, David Zhang wrote: > >> Matt: >> >> Thanks for your quick response. I did try to build cmake with OpenSSL, >> however, that does not solve the problem. >> >> Snappy and other complained packages are all with zero byte downloaded. I >> took the link to the website using web browser to download, most of them >> are successfully downloaded, and at least one link is not longer available: >> >> Protobuf.googlecode.com/files/protobuf-2.5.0.tar2.b2 >> >> This causes the Downloading fail (one of the reasons). The other modules >> that I downloaded do not match the exact names that showed up in the >> Download folder. I have to rename them to match with the configuration. >> >> So this is what I have got so far. I suggest you take a look at these >> links and let us now if my find is correct. >> >> Thanks, >> >> David >> >> On Aug 31, 2016, at 3:29 PM, Matt Dawkins >> wrote: >> >> Are the downloaded packages for snappy approximately 0 or 1 bytes? Can >> you click the above link and download the package in a browser on the same >> computer? >> >> If the answer is yes and yes, this is probably an issue of using a cmake >> not built with ssl support, and failing on all https links. Install >> openssl-devel (or -dev) from your package manager, and rebuild cmake with >> CMAKE_USE_OPENSSL=ON. Depending on your package manager on linux version, >> this may or may not have been done in your installed system cmake. If >> that's not the solution it might be a libcurl issue. >> >> I'll add a blurb about this on the build instructions. >> >> >> As for the second question, all of the packages built within VIAME are >> not installed globally, so they should not mess up any existing build >> setups. They are installed into [viame_build_dir]/install. There might >> still be some lingering issues with certain subpackages in VIAME picking up >> your system libraries instead of ones in the internal build, however, but >> we're trying to reduce these as possible so that it's a self contained >> environment. If you want to build all of the dependencies yourself (or >> alternatively, use installed system libraries) you can also set >> VIAME_BUILD_DEPENDENCIES=OFF, in which case you will need to manually build >> KWIVER and VIAME by pointing them both to the required libraries on your >> computer if they are not auto-detected. >> >> Best, >> >> Matt D. >> >> On Wed, Aug 31, 2016 at 2:47 PM, David Zhang wrote: >> >>> Hi: >>> >>> >>> >>> This is David Zhang from SRI. I followed the instruction online and >>> cloned VIAME to my laptop running 64-bit Ubuntu 14.04. >>> >>> >>> >>> I encountered building errors which I pasted a small section below: >>> >>> : >>> >>> david at M6700:~/projects/VIAME/build$ make -j8 >>> >>> [ 7%] Removing build stamp file for build update (forcebuild). >>> >>> [ 7%] Performing build step for 'fletch' >>> >>> [ 6%] Performing download step (download, verify and extract) for >>> 'Snappy' >>> >>> [ 6%] Performing download step (download, verify and extract) for 'LMDB' >>> >>> [ 6%] Performing download step (download, verify and extract) for >>> 'Protobuf' >>> >>> [ 6%] Performing download step (download, verify and extract) for 'GLog' >>> >>> [ 6%] Performing download step (download, verify and extract) for >>> 'OpenBLAS' >>> >>> [ 6%] Performing download step (download, verify and extract) for 'ZLib' >>> >>> [ 6%] Built target OpenCV >>> >>> [ 6%] Performing download step (download, verify and extract) for >>> 'Boost' >>> >>> -- downloading... >>> >>> src='https://github.com/google/snappy/releases/download/1.1. >>> 3/snappy-1.1.3.tar.gz' >>> >>> dst='/home/david/projects/VIAME/packages/fletch/Downloads/sn >>> appy-1.1.3.tar.gz' >>> >>> timeout='none' >>> >>> CMake Error at Snappy-stamp/download-Snappy.cmake:27 (message): >>> >>> error: downloading >>> >>> 'https://github.com/google/snappy/releases/download/1.1.3/sn >>> appy-1.1.3.tar.gz' >>> >>> failed >>> >>> >>> >>> status_code: 1 >>> >>> status_string: "Unsupported protocol" >>> >>> log: Protocol "https" not supported or disabled in libcurl >>> >>> >>> >>> Closing connection -1 >>> >>> >>> >>> -- downloading... >>> >>> src='https://github.com/google/glog/archive/v0.3.3.tar.gz' >>> >>> dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0 >>> .3.3.tar.gz' >>> >>> timeout='none' >>> >>> -- downloading... >>> >>> src='https://github.com/xianyi/OpenBLAS/archive/v0.2.15.tar.gz' >>> >>> dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0 >>> .2.15.tar.gz' >>> >>> timeout='none' >>> >>> make[5]: *** [build/src/Snappy-stamp/Snappy-download] Error 1 >>> >>> ............................................................ >>> .................................................. >>> >>> >>> >>> I checked VIAME/packages/fletch/Downloads, I think all the third-party >>> package downloads were successful. However, cmake setup still looks for >>> these websites to downloading. The network connections were complained by >>> the make build. I have not looked into CMake settings. If you find sometime >>> useful, please let me know. >>> >>> >>> >>> By the way, from the make build, I am able to build opencv. It seems >>> like just some downloaded packages were not able to build. >>> >>> >>> >>> Another question is: are all the built package, including VIAME, locally >>> installed? I have other versions of opencv, eigen, boost and protobuf which >>> are installed globally. I guess there is no conflict with these already >>> installed packages from the VIAME. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> David >>> >>> >>> >>> _______________________________________________ >>> Viame mailing list >>> Viame at public.kitware.com >>> http://public.kitware.com/mailman/listinfo/viame >>> >>> >> >> >> -- >> Matthew Dawkins >> 1-518-881-4416 >> Senior R&D Engineer >> Kitware, Inc >> >> >> _______________________________________________ >> Viame mailing list >> Viame at public.kitware.com >> http://public.kitware.com/mailman/listinfo/viame >> >> > > > -- > *Linus Sherrill - *Staff R&D Engineer > Kitware, Inc. > 28 Corporate Drive > Clifton Park, NY 12065-8662 > E: linus.sherrill at kitware.com > P: 518.881.4400 > > -- *Linus Sherrill - *Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.zhang at sri.com Wed Aug 31 18:52:38 2016 From: david.zhang at sri.com (David Zhang) Date: Wed, 31 Aug 2016 22:52:38 +0000 Subject: [Viame] VIAME build error In-Reply-To: References: <687E061382DFB14ABA0DB8A3997BD52401AA69E5C1@exchange-db13.sri.com> <34989D50-9FA8-40DD-8F36-A10BF7DF37C8@sri.com> <53428D00-F69E-4D77-B4DA-BD17CB399393@sri.com>, Message-ID: <0E613264-3E8C-48FC-B4FB-A074E7BC3151@sri.com> Thanks, will give it a try! David On Aug 31, 2016, at 6:35 PM, Linus Sherrill > wrote: Judging from your original report of (log: Protocol "https" not supported or disabled in libcurl) the problem may be with the cmake you are using. Usually the cmake that comes with a system distribution has SSL disabled. I have this problem every time a new version is released. You can build a new cmake from downloading the sources from https://cmake.org/files/v3.6/cmake-3.6.1.tar.gz When building thew new cmake, enter the commands $ ./bootstrap $ make" $ cmake -DCMAKE_USE_OPENSSL=ON $ make $ make install (if desired) The problem is that the default cmake options do not include building with OPENSSL which is needed to download external packages using https: protocol. The above commands make a new version of cmake with OPENSSL enabled. A fix has been pushed up that corrects the protobuf download URL. HTH -Linus On Wed, Aug 31, 2016 at 5:55 PM, David Zhang > wrote: Linus: I am using cmake 3.4.1. I noticed VIAME suggested 3.6.1. Is the version making a difference? If it is, I can definitely upgrade cmake. Thanks, David On Aug 31, 2016, at 5:43 PM, Linus Sherrill > wrote: David, It is possible that the system is still using the same old cmake binary. You could try running what cmake to see which version is being used. If it is still the old version, you can adjust your PATH to include the new cmake before the system version. We are working on the protobuf problem and will point to the new protobuf tar file. Google updated protobuf on August 25th and changed the old download URL. We will let you know when there is a new version to pull. -Linus On Wed, Aug 31, 2016 at 5:17 PM, David Zhang > wrote: Matt: Thanks for your quick response. I did try to build cmake with OpenSSL, however, that does not solve the problem. Snappy and other complained packages are all with zero byte downloaded. I took the link to the website using web browser to download, most of them are successfully downloaded, and at least one link is not longer available: Protobuf.googlecode.com/files/protobuf-2.5.0.tar2.b2 This causes the Downloading fail (one of the reasons). The other modules that I downloaded do not match the exact names that showed up in the Download folder. I have to rename them to match with the configuration. So this is what I have got so far. I suggest you take a look at these links and let us now if my find is correct. Thanks, David On Aug 31, 2016, at 3:29 PM, Matt Dawkins > wrote: Are the downloaded packages for snappy approximately 0 or 1 bytes? Can you click the above link and download the package in a browser on the same computer? If the answer is yes and yes, this is probably an issue of using a cmake not built with ssl support, and failing on all https links. Install openssl-devel (or -dev) from your package manager, and rebuild cmake with CMAKE_USE_OPENSSL=ON. Depending on your package manager on linux version, this may or may not have been done in your installed system cmake. If that's not the solution it might be a libcurl issue. I'll add a blurb about this on the build instructions. As for the second question, all of the packages built within VIAME are not installed globally, so they should not mess up any existing build setups. They are installed into [viame_build_dir]/install. There might still be some lingering issues with certain subpackages in VIAME picking up your system libraries instead of ones in the internal build, however, but we're trying to reduce these as possible so that it's a self contained environment. If you want to build all of the dependencies yourself (or alternatively, use installed system libraries) you can also set VIAME_BUILD_DEPENDENCIES=OFF, in which case you will need to manually build KWIVER and VIAME by pointing them both to the required libraries on your computer if they are not auto-detected. Best, Matt D. On Wed, Aug 31, 2016 at 2:47 PM, David Zhang > wrote: Hi: This is David Zhang from SRI. I followed the instruction online and cloned VIAME to my laptop running 64-bit Ubuntu 14.04. I encountered building errors which I pasted a small section below: : david at M6700:~/projects/VIAME/build$ make -j8 [ 7%] Removing build stamp file for build update (forcebuild). [ 7%] Performing build step for 'fletch' [ 6%] Performing download step (download, verify and extract) for 'Snappy' [ 6%] Performing download step (download, verify and extract) for 'LMDB' [ 6%] Performing download step (download, verify and extract) for 'Protobuf' [ 6%] Performing download step (download, verify and extract) for 'GLog' [ 6%] Performing download step (download, verify and extract) for 'OpenBLAS' [ 6%] Performing download step (download, verify and extract) for 'ZLib' [ 6%] Built target OpenCV [ 6%] Performing download step (download, verify and extract) for 'Boost' -- downloading... src='https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/snappy-1.1.3.tar.gz' timeout='none' CMake Error at Snappy-stamp/download-Snappy.cmake:27 (message): error: downloading 'https://github.com/google/snappy/releases/download/1.1.3/snappy-1.1.3.tar.gz' failed status_code: 1 status_string: "Unsupported protocol" log: Protocol "https" not supported or disabled in libcurl Closing connection -1 -- downloading... src='https://github.com/google/glog/archive/v0.3.3.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.3.3.tar.gz' timeout='none' -- downloading... src='https://github.com/xianyi/OpenBLAS/archive/v0.2.15.tar.gz' dst='/home/david/projects/VIAME/packages/fletch/Downloads/v0.2.15.tar.gz' timeout='none' make[5]: *** [build/src/Snappy-stamp/Snappy-download] Error 1 .............................................................................................................. I checked VIAME/packages/fletch/Downloads, I think all the third-party package downloads were successful. However, cmake setup still looks for these websites to downloading. The network connections were complained by the make build. I have not looked into CMake settings. If you find sometime useful, please let me know. By the way, from the make build, I am able to build opencv. It seems like just some downloaded packages were not able to build. Another question is: are all the built package, including VIAME, locally installed? I have other versions of opencv, eigen, boost and protobuf which are installed globally. I guess there is no conflict with these already installed packages from the VIAME. Thanks, David _______________________________________________ Viame mailing list Viame at public.kitware.com http://public.kitware.com/mailman/listinfo/viame -- Matthew Dawkins 1-518-881-4416 Senior R&D Engineer Kitware, Inc _______________________________________________ Viame mailing list Viame at public.kitware.com http://public.kitware.com/mailman/listinfo/viame -- Linus Sherrill - Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -- Linus Sherrill - Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From prasad at lanl.gov Wed Aug 31 19:20:42 2016 From: prasad at lanl.gov (Prasad, Lakshman) Date: Wed, 31 Aug 2016 23:20:42 +0000 Subject: [Viame] issue downloading Message-ID: <1472685642046.76142@lanl.gov> Hi, I went to the link https://github.com/Kitware/VIAME? and under the dropdown menu 'Clone or download' I chose Download ZIP to get a file named VIAME-master.zip (30 KB). Upon unarchiving to VIAME-master in my home directory , I notice that folders ( kitware, fletch, scallops-tk) under packages were all empty. If I run the super-build on the command line in a terminal,? I get the following error: pn1246609:~ prasad$ git clone https://github.com/Kitware/VIAME.git VIAME-source Cloning into 'VIAME-source'... fatal: unable to access 'https://github.com/Kitware/VIAME.git/': Failed to connect to github.com port 443: Connection refused even though I created a github account. However, if I look in the subfolders of packages on the repository, they are nonempty. Thanks, Lakshman ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From yogi at whoi.edu Wed Aug 31 19:44:33 2016 From: yogi at whoi.edu (Yogesh Girdhar) Date: Wed, 31 Aug 2016 19:44:33 -0400 Subject: [Viame] issue downloading In-Reply-To: <1472685642046.76142@lanl.gov> References: <1472685642046.76142@lanl.gov> Message-ID: Laxman after you git clone VIAME do: $ cd VIAME $ git submodule update --init that will download code for all those folders that you see as being empty. On Wed, Aug 31, 2016 at 7:20 PM, Prasad, Lakshman wrote: > Hi, > > > I went to the link https://github.com/Kitware/VIAME? and under the > dropdown menu 'Clone or download' I chose Download ZIP to get a file named > VIAME-master.zip (30 KB). Upon unarchiving to VIAME-master in my home > directory , I notice that folders ( kitware, fletch, scallops-tk) under > packages were all empty. If I run the super-build on the command line in a > terminal,? I get the following error: > > > pn1246609:~ prasad$ git clone https://github.com/Kitware/VIAME.git > VIAME-source > > Cloning into 'VIAME-source'... > > fatal: unable to access 'https://github.com/Kitware/VIAME.git/': Failed > to connect to github.com port 443: Connection refused > > even though I created a github account. > > However, if I look in the subfolders of packages on the repository, they > are nonempty. > > Thanks, > Lakshman > ? > > > > > > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame > > -- Yogesh Girdhar Assistant Scientist Blake 209, MS 7 Applied Ocean Physics & Engineering Woods Hole Oceanographic Institution http://www.whoi.edu/people/ygirdhar +1-508-289-2932 -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.dawkins at kitware.com Wed Aug 31 20:17:41 2016 From: matt.dawkins at kitware.com (Matt Dawkins) Date: Wed, 31 Aug 2016 20:17:41 -0400 Subject: [Viame] issue downloading In-Reply-To: References: <1472685642046.76142@lanl.gov> Message-ID: If "git clone [any git repo] [source dir]" for all git repos is not working (not just for VIAME) you might need to check to see if you have heavy firewall settings enabled that are blocking git, or other internet connectivity issues. For just cloning a repository using https, you should not need a github account - though it definitly doesn't hurt to have one. Once the git clone is successful, the submodule command that Yogesh pointed out is what actually initializes those folders, as they're just links to exact versions of other repositories on github. If all else fails, or your IT department is blocking git somehow (in which case I would break out the pitch forks) you can use the full source download package I'm putting together for the people on the boat. On Wed, Aug 31, 2016 at 7:44 PM, Yogesh Girdhar wrote: > Laxman > > after you git clone VIAME > > do: > $ cd VIAME > $ git submodule update --init > > that will download code for all those folders that you see as being empty. > > > > On Wed, Aug 31, 2016 at 7:20 PM, Prasad, Lakshman wrote: > >> Hi, >> >> >> I went to the link https://github.com/Kitware/VIAME? and under the >> dropdown menu 'Clone or download' I chose Download ZIP to get a file named >> VIAME-master.zip (30 KB). Upon unarchiving to VIAME-master in my home >> directory , I notice that folders ( kitware, fletch, scallops-tk) under >> packages were all empty. If I run the super-build on the command line in a >> terminal,? I get the following error: >> >> >> pn1246609:~ prasad$ git clone https://github.com/Kitware/VIAME.git >> VIAME-source >> >> Cloning into 'VIAME-source'... >> >> fatal: unable to access 'https://github.com/Kitware/VIAME.git/': Failed >> to connect to github.com port 443: Connection refused >> >> even though I created a github account. >> >> However, if I look in the subfolders of packages on the repository, they >> are nonempty. >> >> Thanks, >> Lakshman >> ? >> >> >> >> >> >> _______________________________________________ >> Viame mailing list >> Viame at public.kitware.com >> http://public.kitware.com/mailman/listinfo/viame >> >> > > > -- > Yogesh Girdhar > Assistant Scientist > Blake 209, MS 7 > Applied Ocean Physics & Engineering > Woods Hole Oceanographic Institution > http://www.whoi.edu/people/ygirdhar > +1-508-289-2932 > > _______________________________________________ > Viame mailing list > Viame at public.kitware.com > http://public.kitware.com/mailman/listinfo/viame > > -- Matthew Dawkins 1-518-881-4416 Senior R&D Engineer Kitware, Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: