Recherche avancée

Sur d’autres sites (9716)

• Logic and lawyers

  22 mai 2013, par Mans — Law and liberty

  Reading about various patent litigation cases, I am struck by the frequency with which common logical fallacies such as the Appeal to Consequences are committed. We shall look at a couple of recent examples.

  In conjunction with the Federal Circuit ruling in CLS Bank v. Alice Corp., Judge Moore, joined by three others, filed a dissenting opinion wherein we find the following :

  I am concerned that the current interpretation of § 101, and in particular the abstract idea exception, is causing a free fall in the patent system. [...] And let’s be clear : if all of these claims, including the system claims, are not patent-eligible, this case is the death of hundreds of thousands of patents [...].

  A footnote adds :

  If the reasoning of Judge Lourie’s opinion were adopted, it would decimate the electronics and software industries. [...] There has never been a case which could do more damage to the patent system than this one.

  From the above, I get the impression Moore is primarily concerned with protecting the system, maintaining the status quo, less with ruling in line with the logical consequences of statute and case law. Furthermore, her argument rests on the premise that a weaker patent system would “decimate the industries,” a notion supported by little evidence, yet presented by Moore as an obvious truth. In fact, research exists suggesting that many important innovations are never actually patented. Let us also not overlook the fact that European companies do not appear to be suffering from the much weaker patent protection for software afforded there.

  Judge Moore’s reasoning can be summarised in three steps :

  1. Ruling this way could be disruptive to the patent system.
  2. The industry relies on patents.
  3. Therefore we must not rule this way.

  Not only does she commit the aforementioned logical fallacy, she does so by way of invalid arguments.

  The second example of such fallacious reasoning comes from the Supreme Court ruling in Bowman v. Monsanto :

  We have always drawn the boundaries of the exhaustion doctrine to exclude that activity [copying], so that the patentee retains an undiminished right to prohibit others from making the thing his patent protects. [...] That is because, once again, if simple copying were a protected use, a patent would plummet in value after the first sale of the first item containing the invention. The undiluted patent monopoly, it might be said, would extend not for 20 years (as the Patent Act promises), but for only one transaction. And that would result in less incentive for innovation than Congress wanted. Hence our repeated insistence that exhaustion applies only to the particular item sold, and not to reproductions.

  Here we find the same pattern repeated. The aim of the court appears to have been ensuring the continued validity of this class of patents, not reaching a logical conclusion regarding the question of infringement. Once again, we can break the reasoning down into three steps :

  1. A non-infringement ruling would weaken the patent.
  2. Weaker patents would provide less incentive for innovation.
  3. Therefore we must rule infringement.

  As in the first example, the argument presented in step two is at best questionable, and no supporting evidence is provided.

  These are, unfortunately, not the only examples of such fallacies ; one might even describe them as ubiquitous. Does a law education not include any material on logical reasoning ? Ought it not ? While we can never hope to find any kind of universal truth on which to base our laws, we should at least strive to make our system logically consistent. If we do not, notions such as fairness and justice lose their meanings.

• Opencv crosscompile with ffmpeg and other 3rdparty for arm board

  16 juin 2017, par Little Tooth

  After buliding Qt5.5.1 for my arm board sucessfully, I am taking up to crosscompile opencv. Here are the steps :

  First, I crosscompile 3rdparty :

  a.libz

  lmk@lmk-virtual-machine:/home/newdisk$ sudo tar -zvxf zlib-1.2.8.tar.gz
  
  lmk@lmk-virtual-machine:/home/newdisk$ cd zlib-1.2.8
  
  lmk@lmk-virtual-machine:/home/newdisk/zlib-1.2.8$ sudo ./configure --prefix=/home/newdisk/optnew/opencv-rely -shared
  
  lmk@lmk-virtual-machine:/home/newdisk/zlib-1.2.8$ sudo vi Makefile

  and etit Makefile in some details :

  #Makefile
  
  CC=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc
  
  LDSHARED= /home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc -shared -Wl,-soname,libz.so.1,--version-script,zlib.map
  
  AR=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-ar
  
  RANLIB=arm-linux-ranlib

  the last step is run make and make install :

  lmk@lmk-virtual-machine:/home/newdisk/zlib-1.2.8$ sudo make
  
  lmk@lmk-virtual-machine:/home/newdisk/zlib-1.2.8$ sudo make install

  b.libjpeg

  lmk@lmk-virtual-machine:/home/newdisk$ sudo tar -zvxf jpegsrc.v9.tar.gz
  
  lmk@lmk-virtual-machine:/home/newdisk$ cd jpeg-9
  
  lmk@lmk-virtual-machine:/home/newdisk/jpeg-9$ sudo CC=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc ./configure --host=arm-linux --prefix=/home/newdisk/optnew/opencv-rely --enable-shared --enable-static
  
  lmk@lmk-virtual-machine:/home/newdisk/jpeg-9$ sudo make
  
  lmk@lmk-virtual-machine:/home/newdisk/jpeg-9$ sudo make install

  c.libpng

  lmk@lmk-virtual-machine:/home/newdisk$ sudo xz -d libpng-1.6.29.tar.xz
  
  lmk@lmk-virtual-machine:/home/newdisk$ sudo tar -xvf libpng-1.6.29.tar
  
  lmk@lmk-virtual-machine:/home/newdisk$ cd libpng-1.6.29
  
  lmk@lmk-virtual-machine:/home/newdisk/libpng-1.6.29$ sudo CC=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc ./configure --host=arm-linux --prefix=/home/newdisk/optnew/opencv-rely --enable-shared --enable-static
  
  lmk@lmk-virtual-machine:/home/newdisk/libpng-1.6.29$ sudo make
  
  lmk@lmk-virtual-machine:/home/newdisk/libpng-1.6.29$ sudo make install

  d.yasm

  lmk@lmk-virtual-machine:/home/newdisk$ sudo tar -zvxf yasm-1.3.0.tar.gz
  
  lmk@lmk-virtual-machine:/home/newdisk$ cd yasm-1.3.0
  
  lmk@lmk-virtual-machine:/home/newdisk/yasm-1.3.0$ sudo CC=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc ./configure --prefix=/home/newdisk/optnew/opencv-rely --host=arm-linux
  
  lmk@lmk-virtual-machine:/home/newdisk/yasm-1.3.0$ sudo make
  
  lmk@lmk-virtual-machine:/home/newdisk/yasm-1.3.0$ sudo make install

  e.libx264

  lmk@lmk-virtual-machine:/home/newdisk$ sudo tar -jxvf last_x264.tar.bz2
  
  lmk@lmk-virtual-machine:/home/newdisk$ cd x264-snapshot-20170612-2245 
  
  lmk@lmk-virtual-machine:/home/newdisk/x264-snapshot-20170612-2245$ sudo CC=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc ./configure --enable-shared --host=arm-linux --disable-asm --prefix=/home/newdisk/optnew/opencv-rely
  
  lmk@lmk-virtual-machine:/home/newdisk/x264-snapshot-20170612-2245$ sudo make
  
  lmk@lmk-virtual-machine:/home/newdisk/x264-snapshot-20170612-2245$ sudo make install

  f.libxvid

  lmk@lmk-virtual-machine:/home/newdisk$ cd xvidcore-1.3.3
  
  lmk@lmk-virtual-machine:/home/newdisk/xvidcore-1.3.3$ cd build/generic
  
  lmk@lmk-virtual-machine:/home/newdisk/xvidcore-1.3.3/build/generic$ sudo CC=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc ./configure --prefix=/home/newdisk/optnew/opencv-rely --host=arm-linux  --disable-assembly
  
  lmk@lmk-virtual-machine:/home/newdisk/xvidcore-1.3.3/build/generic$ sudo make
  
  lmk@lmk-virtual-machine:/home/newdisk/xvidcore-1.3.3/build/generic$ sudo make install

  g.ffmpeg

  lmk@lmk-virtual-machine:/home/newdisk$ sudo tar -jvxf ffmpeg-3.3.2.tar.bz2
  
  lmk@lmk-virtual-machine:/home/newdisk$ cd ffmpeg-3.3.2
  
  lmk@lmk-virtual-machine:/home/newdisk/ffmpeg-3.3.2$
  
  sudo ./configure --prefix=/home/newdisk/optnew/opencv-rely --enable-shared --disable-static --enable-gpl --enable-cross-compile  --arch=arm --disable-stripping --target-os=linux --enable-libx264 --enable-libxvid --cc=/home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc --enable-swscale --extra-ldflags=-L/home/newdisk/optnew/opencv-rely/lib --extra-cflags=-I/home/newdisk/optnew/opencv-rely/include
  
  lmk@lmk-virtual-machine:/home/newdisk/ffmpeg-3.3.2$ sudo make
  
  lmk@lmk-virtual-machine:/home/newdisk/ffmpeg-3.3.2$ sudo make install

  There is no problem in 3rdparty crosscompile.
  Next, opencv crosscompile :

  lmk@lmk-virtual-machine:/home/newdisk$ sudo unzip opencv-3.1.0.zip
  
  lmk@lmk-virtual-machine:/home/newdisk$ cd opencv-3.1.0
  
  lmk@lmk-virtual-machine:/home/newdisk/opencv-3.1.0$ sudo mkdir BuildOpencv
  
  lmk@lmk-virtual-machine:/home/newdisk/opencv-3.1.0$ cd BuildOpencv
  
  lmk@lmk-virtual-machine:/home/newdisk/opencv-3.1.0/BuildOpencv$ sudo vim toolchain.cmake
  
  #toolchain.cmake
  
  ###########user defined#############
  
  set( CMAKE_SYSTEM_NAME Linux )
  
  set( CMAKE_SYSTEM_PROCESSOR arm )
  
  set( CMAKE_C_COMPILER /home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-linux-gcc )
  
  set( CMAKE_CXX_COMPILER /home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-linux-g++ )
  
  ###########user defined#############
  
  set( CMAKE_FIND_ROOT_PATH /home/newdisk/optnew/opencv-rely)
  
  set( CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER )
  
  set( CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
  
  set( CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
  
  ######################################

  Then I run cmake :

  lmk@lmk-virtual-machine:/home/newdisk/opencv-3.1.0/BuildOpencv$ sudo cmake -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake ../

  Here is the result：

  -- Detected version of GNU GCC: 45 (405)
  
  -- Found ZLIB: /home/newdisk/optnew/opencv-rely/lib/libz.so (found suitable version "1.2.8", minimum required is "1.2.3") 
  
  -- Could NOT find TIFF (missing:  TIFF_LIBRARY TIFF_INCLUDE_DIR) 
  
  -- Could NOT find Jasper (missing:  JASPER_LIBRARIES) (found version "1.900.1")
  
  -- Found ZLIB: /home/newdisk/optnew/opencv-rely/lib/libz.so (found version "1.2.8") 
  
  -- checking for module 'gtk+-3.0'
  
  --   package 'gtk+-3.0' not found
  
  -- checking for module 'gstreamer-base-1.0'
  
  --   package 'gstreamer-base-1.0' not found
  
  -- checking for module 'gstreamer-video-1.0'
  
  --   package 'gstreamer-video-1.0' not found
  
  -- checking for module 'gstreamer-app-1.0'
  
  --   package 'gstreamer-app-1.0' not found
  
  -- checking for module 'gstreamer-riff-1.0'
  
  --   package 'gstreamer-riff-1.0' not found
  
  -- checking for module 'gstreamer-pbutils-1.0'
  
  --   package 'gstreamer-pbutils-1.0' not found
  
  -- checking for module 'gstreamer-base-0.10'
  
  --   package 'gstreamer-base-0.10' not found
  
  -- checking for module 'gstreamer-video-0.10'
  
  --   package 'gstreamer-video-0.10' not found
  
  -- checking for module 'gstreamer-app-0.10'
  
  --   package 'gstreamer-app-0.10' not found
  
  -- checking for module 'gstreamer-riff-0.10'
  
  --   package 'gstreamer-riff-0.10' not found
  
  -- checking for module 'gstreamer-pbutils-0.10'
  
  --   package 'gstreamer-pbutils-0.10' not found
  
  -- Looking for linux/videodev.h
  
  -- Looking for linux/videodev.h - found
  
  -- Looking for linux/videodev2.h
  
  -- Looking for linux/videodev2.h - found
  
  -- Looking for sys/videoio.h
  
  -- Looking for sys/videoio.h - not found
  
  -- checking for module 'libavresample'
  
  --   package 'libavresample' not found
  
  -- Looking for libavformat/avformat.h
  
  -- Looking for libavformat/avformat.h - not found
  
  -- Looking for ffmpeg/avformat.h
  
  -- Looking for ffmpeg/avformat.h - not found
  
  -- checking for module 'libgphoto2'
  
   --   package 'libgphoto2' not found
  
  -- Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE) 
  
  -- To enable PlantUML support, set PLANTUML_JAR environment variable or pass -DPLANTUML_JAR=<filepath> option to cmake
  
  -- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.6", minimum required is "2.7") 
  
  -- Could NOT find PythonLibs (missing:  PYTHON_LIBRARIES) (found suitable version "2.7.6", minimum required is "2.7")
  
  -- Cannot probe for Python/Numpy support (because we are cross-compiling OpenCV)
  
  -- If you want to enable Python/Numpy support, set the following variables:
  
  --   PYTHON2_INCLUDE_PATH
  
  --   PYTHON2_LIBRARIES
  
  --   PYTHON2_NUMPY_INCLUDE_DIRS
  
  --   PYTHON3_INCLUDE_PATH
  
  --   PYTHON3_LIBRARIES
  
  --   PYTHON3_NUMPY_INCLUDE_DIRS
  
  -- Found PythonInterp: /usr/bin/python3.4 (found suitable version "3.4.3", minimum required is "3.4") 
  
  -- Could NOT find PythonLibs (missing:  PYTHON_LIBRARIES) (Required is at least version "3.4")
  
  -- Cannot probe for Python/Numpy support (because we are cross-compiling OpenCV)
  
  -- If you want to enable Python/Numpy support, set the following variables:
  
  --   PYTHON2_INCLUDE_PATH
  
  --   PYTHON2_LIBRARIES
  
  --   PYTHON2_NUMPY_INCLUDE_DIRS
  
  --   PYTHON3_INCLUDE_PATH
  
  --   PYTHON3_LIBRARIES
  
  --   PYTHON3_NUMPY_INCLUDE_DIRS
  
  -- Could NOT find JNI (missing:  JAVA_AWT_LIBRARY JAVA_JVM_LIBRARY JAVA_INCLUDE_PATH JAVA_INCLUDE_PATH2 JAVA_AWT_INCLUDE_PATH) 
  
  -- Could NOT find Matlab (missing:  MATLAB_MEX_SCRIPT MATLAB_INCLUDE_DIRS MATLAB_ROOT_DIR MATLAB_LIBRARIES MATLAB_LIBRARY_DIRS MATLAB_MEXEXT MATLAB_ARCH MATLAB_BIN) 
  
  -- 
  
  -- General configuration for OpenCV 3.1.0 
  
  =====================================
  
  --   Version control:               unknown
  
  -- 
  
  --   Platform:
  
  --     Host:                        Linux 3.16.0-77-generic i686
  
  --     Target:                      Linux arm
  
  --     CMake:                       2.8.12.2
  
  --     CMake generator:             Unix Makefiles
  
  --     CMake build tool:            /usr/bin/make
  
  --     Configuration:               Release
  
  -- 
  
  --   C/C++:
  
  --     Built as dynamic libs?:      YES
  
  --     C++ Compiler:                /home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-linux-g++  (ver 4.5.1)
  
  --     C++ flags (Release):         -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fvisibility=hidden -fvisibility-inlines-hidden -O3 -DNDEBUG  -DNDEBUG
  
  --     C++ flags (Debug):           -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fvisibility=hidden -fvisibility-inlines-hidden -g  -O0 -DDEBUG -D_DEBUG
  
  --     C Compiler:                  /home/newdisk/optnew/opt/FriendlyARM/toolschain/4.5.1/bin/arm-linux-gcc
  
  --     C flags (Release):           -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fvisibility=hidden -O3 -DNDEBUG  -DNDEBUG
  
  --     C flags (Debug):             -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fvisibility=hidden -g  -O0 -DDEBUG -D_DEBUG
  
  --     Linker flags (Release):      
  
  --     Linker flags (Debug):        
  
  --     Precompiled headers:         YES
  
  --     Extra dependencies:          /home/newdisk/optnew/opencv-rely/lib/libjpeg.so /home/newdisk/optnew/opencv-rely/lib/libpng.so /home/newdisk/optnew/opencv-rely/lib/libz.so gtk-x11-2.0 gdk-x11-2.0 atk-1.0 gio-2.0 pangoft2-1.0 pangocairo-1.0 gdk_pixbuf-2.0 cairo pango-1.0 fontconfig gobject-2.0 freetype gthread-2.0 glib-2.0 dc1394 v4l1 v4l2 avcodec avformat avutil swscale dl m pthread rt
  
  --     3rdparty dependencies:       libwebp libtiff libjasper IlmImf
  
  -- 
  
  --   OpenCV modules:
  
  --     To be built:                 core flann imgproc ml photo video imgcodecs shape videoio highgui objdetect superres ts features2d calib3d stitching videostab
  
  --     Disabled:                    world
  
  --     Disabled by dependency:      -
  
  --     Unavailable:                 cudaarithm cudabgsegm cudacodec cudafeatures2d cudafilters cudaimgproc cudalegacy cudaobjdetect cudaoptflow cudastereo cudawarping cudev java python2 python3 viz
  
  -- 
  
  --   GUI: 
  
  --     QT:                          NO
  
  --     GTK+ 2.x:                    YES (ver 2.24.23)
  
  --     GThread :                    YES (ver 2.40.2)
  
  --     GtkGlExt:                    NO
  
  --     OpenGL support:              NO
  
  --     VTK support:                 NO
  
  -- 
  
  --   Media I/O: 
  
  --     ZLib:                        /home/newdisk/optnew/opencv-rely/lib/libz.so (ver 1.2.8)
  
  --     JPEG:                        /home/newdisk/optnew/opencv-rely/lib/libjpeg.so (ver 90)
  
  --     WEBP:                        build (ver 0.3.1)
  
  --     PNG:                         /home/newdisk/optnew/opencv-rely/lib/libpng.so (ver 1.6.29)
  
  --     TIFF:                        build (ver 42 - 4.0.2)
  
  --     JPEG 2000:                   build (ver 1.900.1)
  
  --     OpenEXR:                     build (ver 1.7.1)
  
  --     GDAL:                        NO
  
  -- 
  
  --   Video I/O:
  
  --     DC1394 1.x:                  NO
  
  --     DC1394 2.x:                  YES (ver 2.2.1)
  
  --     FFMPEG:                      YES
  
  --       codec:                     YES (ver 54.35.1)
  
  --       format:                    YES (ver 54.20.4)
  
  --       util:                      YES (ver 52.3.0)
  
  --       swscale:                   YES (ver 2.1.1)
  
  --       resample:                  NO
  
  --       gentoo-style:              YES
  
  --     GStreamer:                   NO
  
  --     OpenNI:                      NO
  
  --     OpenNI PrimeSensor Modules:  NO
  
  --     OpenNI2:                     NO
  
  --     PvAPI:                       NO
  
  --     GigEVisionSDK:               NO
  
  --     UniCap:                      NO
  
  --     UniCap ucil:                 NO
  
  --     V4L/V4L2:                    Using libv4l1 (ver 0.8.8) / libv4l2 (ver 0.8.8)
  
  --     XIMEA:                       NO
  
  --     Xine:                        NO
  
  --     gPhoto2:                     NO
  
  -- 
  
  --   Parallel framework:            pthreads
  
  -- 
  
  --   Other third-party libraries:
  
  --     Use IPP:                     NO
  
  --     Use VA:                      NO
  
  --     Use Intel VA-API/OpenCL:     NO
  
  --     Use Eigen:                   NO
  
  --     Use Cuda:                    NO
  
  --     Use OpenCL:                  YES
  
  --     Use custom HAL:              NO
  
  -- 
  
  --   OpenCL:
  
  --     Version:                     dynamic
  
  --     Include path:                /home/newdisk/opencv-3.1.0/3rdparty/include/opencl/1.2
  
  --     Use AMDFFT:                  NO
  
  --      Use AMDBLAS:                 NO
  
  -- 
  
  --   Python 2:
  
  --     Interpreter:                 /usr/bin/python2.7 (ver 2.7.6)
  
  -- 
  
  --   Python 3:
  
  --     Interpreter:                 /usr/bin/python3.4 (ver 3.4.3)
  
  -- 
  
  --   Python (for build):            /usr/bin/python2.7
  
  -- 
  
  --   Java:
  
  --     ant:                         NO
  
  --     JNI:                         NO
  
  --     Java wrappers:               NO
  
  --     Java tests:                  NO
  
  -- 
  
  --   Matlab:                        Matlab not found or implicitly disabled
  
  -- 
  
  --   Documentation:
  
  --     Doxygen:                     NO
  
  --     PlantUML:                    NO
  
  -- 
  
  --   Tests and samples:
  
  --     Tests:                       YES
  
  --     Performance tests:           YES
  
  --     C/C++ Examples:              NO
  
  -- 
  
  --   Install path:                  /home/newdisk/opencv-3.1.0/BuildOpencv/install
  
  -- 
  
  --   cvconfig.h is in:              /home/newdisk/opencv-3.1.0/BuildOpencv
  
  -- -----------------------------------------------------------------
  
  -- 
  
  -- Configuring done
  
  -- Generating done
  
  -- Build files have been written to: /home/newdisk/opencv-3.1.0/BuildOpencv
  
  </filepath>

  After configuring and generating, run cmake-gui :

  lmk@lmk-virtual-machine:/home/newdisk/opencv-3.1.0/BuildOpencv$ sudo cmake-gui
  
  
  
  Src:/home/newdisk/opencv-3.1.0
  
  Build:/home/newdisk/opencv-3.1.0/BuildOpencv
  
  
  
  CMAKE_INSTALL_PREFIX:/home/newdisk/optnew/opencv-arm
  
  
  
  Don't choose these items:
  
  WITH_CUDA
  
  WITH_GTK
  
  WITH_1394
  
  WITH_GSTREAMER
  
  WITH_LIBV4L 
  
  WITH_TIFF
  
  BUILD_OPENEXR
  
  WITH_OPENEXR
  
  WITH_OPENCL
  
  
  
  Configure and generate.
  
  
  
  lmk@lmk-virtual-machine:/home/newdisk/opencv-3.1.0/BuildOpencv$ sudo vi CMakeCache.txt
  
  #CMakeCache.txt
  
  //Flags used by the linker.
  
  CMAKE_EXE_LINKER_FLAGS:STRING=-lpthread -lrt
  
  
  
  lmk@lmk-virtual-machine:/home/newdisk/opencv-3.1.0/BuildOpencv$ sudo make

  Fianlly,I got these errors :

  [ 27%] Building CXX object modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_mjpeg_decoder.cpp.o
  
  [ 27%] Building CXX object modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_v4l.cpp.o
  
  [ 27%] Building CXX object modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_ffmpeg.cpp.o
  
  In file included from /home/newdisk/opencv-3.1.0/modules/videoio/src/cap_ffmpeg_impl.hpp:65:0,
  
               from /home/newdisk/opencv-3.1.0/modules/videoio/src/cap_ffmpeg.cpp:45:
  
  /home/newdisk/opencv-3.1.0/modules/videoio/src/ffmpeg_codecs.hpp:77:36: fatal error: libavformat/avformat.h: No such file or directory
  
  compilation terminated.
  
  make[2]: *** [modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_ffmpeg.cpp.o] Error 1
  
  make[1]: *** [modules/videoio/CMakeFiles/opencv_videoio.dir/all] Error 2
  
  make: *** [all] Error 2

  While the file libavformat/avformat.h does exits in my directory
  /home/newdisk/optnew/opencv-rely/include

  Why can cmake find lib directory

  -- Found ZLIB: /home/newdisk/optnew/opencv-rely/lib/libz.so (found suitable version "1.2.8", minimum required is "1.2.3")

  but cannot find include directory ?

  /home/newdisk/optnew/opencv-rely/include

  Do you have any idea ?

• How to configure and validate a Funnel in Piwik Analytics

  16 janvier 2017, par InnoCraft — Community

  In the last blog post we have covered how the conversion Funnel plugin enriches your Piwik experience. This post will focus on how to configure and validate your funnel in Piwik so you get the correct data when you view the funnel reports. When you set up a funnel, it is crucial to have it configured correctly as the funnel report will be only as good as its configuration. When we built this Funnel feature, we focused on making the configuration and validation real simple because it is so important to get it right.

  To recap quickly : A Funnel defines a series of steps that you expect your visitors to take on their way to converting a goal or a sale. Funnels, a premium feature for Piwik developed by InnoCraft, lets you define funnels so you can improve your websites and mobile apps based on this data. Learn more about Funnel.

  Configuring a funnel

  As you will notice Funnels integrates nicely into the Piwik Goals management. You can configure a funnel whenever you create or update a goal. You can access the Goals Management either via “Administration => Goals” or via the reporting menu “Goals => Manage”. Then click on either “Add a new goal” or select an existing goal to edit it. At the bottom of the goal form, you will see a new row letting you configure a funnel. As with all our premium features we focused on displaying lots of inline help and explain directly in the UI what a funnel is about, what the steps are in order to configure a funnel, how a funnel helps you and more. This lets you use the Funnel feature even if you have never created or analyzed a funnel before.

  Preparing your Funnel configuration

  Before starting to configure a Funnel we usually have a brainstorm session identifying the funnels on a website or app and the paths we expect users to take there. Once we have identified each step, we click through those identified pages in our website and we note the URLs for each page as the URLs will be needed when you configure a funnel.

  Setting up a Goal

  Once we have finished the planning phase it is time to log into Piwik. We start by either adding a new goal or selecting an existing goal. If you are unfamiliar with setting up goals, have a look at the Piwik Goals user guide. At the bottom of a goal form when you create or update a goal, you can configure your funnel. The UI will first explain you everything about Funnels, what they are, how they help you and which steps you need to take in order to configure it.

  Configuring Funnel steps

  We start by configuring the steps we have identified in the planning phase. Those are the steps we expect our users to take when they convert a goal or purchase something. Now we need to add a step for each page we expect users to take, each step consists of a name and a pattern.

  The name will be shown to you in the funnel reporting so think of a good name that describes each step best, for example “Product”, “Cart”, “Checkout” and “Order”.

  The pattern is needed to define when a visitor will enter this step. Here it comes in handy to have already notes for each URL from the planning phase. You can select lots of different patterns based on “URL Path”, “URL” and “URL parameter”. For example “URL starts with”, “Path ends with”, “URL contains”, “URL matches the regular expression”, and more. Most tools make this configuration unnecessarily hard because they only allow you to choose from one or two patterns (only complicated pattern like regular expressions) and they don’t let you validate whether the URL you have in mind actually matches the pattern. There are three ways to validate your step configurations.

  

  Validating funnel steps

  When we configure a funnel, we validate our steps in the following three ways.

  1. Via the help icon next to the step configuration

  When you click on the help icon, you will receive valuable tips about configuring steps, what “required” means and how to match popular pages. It will also show you a list of all URLs that were tracked in your Piwik in the past and match your specified pattern. For example say you specify a pattern “Path starts with /products”, then Piwik will list all URLs that were tracked in the past matching this pattern. This lets you validate whether your pattern actually matches the URLs you had in mind. It will also show you if the pattern doesn’t match any known URL which can indicate that your configuration may be wrong.

  

  2. Via the URL validator

  Below the steps configuration you find a form field that lets you enter any URL.

  

  We recommend to enter each URL that you have noted before in the planning phase. Once you enter a URL, the configurations will be validated immediately and the result will be shown to you in the step configuration. When a step matches your specified URL, the background will become green, when a step does not match the URL, the background will be red.

  

  If the URL does not match the expected step, simply change your step configuration and the steps will be re-validated as you change the configuration. This way you will see instantly as soon as you got the configuration right.

  What you don’t want is that either all of your steps don’t match (red background) or that several steps match a certain URL (green background). When several step match one URL, then one visitor might enter several funnel steps on just one page. This usually indicates a problem with the step configuration.

  3. Manual funnel validation

  After we have created or updated the goal (more about this soon), we always test a funnel configuration manually. This means we now open our website and click through the pages that we hand in mind and check afterwards whether the steps we took actually appear in the funnel report as expected. This is just another safety net to make sure your funnel configuration is right.

  It is really crucial to have a correct funnel configuration as otherwise the shown data in the funnel reports might not be as helpful. That’s why we focused so much on making the validation part real easy.

  Activating and saving the funnel

  Once you are happy with your configuration, it is time to activate your funnel. As soon as you activate your funnel, a report for this funnel will be generated and the links and reports for this funnel will be visible in the UI. If you are later no longer interested in the funnel, simply deactivate the funnel so it won’t appear in the reporting UI anymore.

  

  To save your funnel configuration simply click on either “Add goal” or “Update goal”. The funnel will be automatically saved whenever you update your goal.

  Goals Management

  The funnel plugin also enriches the list of goals in the Piwik goal management. At a glance you can see whether a funnel for a goal is configured and activated (green tick in the funnel column), whether a funnel is configured but not activated (grey tick in the funnel column) or whether no funnel is configured for a goal (no tick at all).

  

  How to get Funnels and related features

  You can get Funnels on the Piwik Marketplace. If you want to learn more about Funnels you might be also interested in the Funnel User Guide and the Funnel FAQ.

  Similar to Funnels we also offer Users Flow which lets you visualize the flow of your users and visitors across several interactions.