[caffe] 01/03: README.Debian: update
Zhou Mo
cdluminate-guest at moszumanska.debian.org
Mon Jul 4 14:48:24 UTC 2016
This is an automated email from the git hooks/post-receive script.
cdluminate-guest pushed a commit to branch master
in repository caffe.
commit c88c736cb5701c8cf699fd036f43bac88516f221
Author: Zhou Mo <cdluminate at gmail.com>
Date: Mon Jul 4 14:46:33 2016 +0000
README.Debian: update
---
debian/README.Debian | 75 +++++++++++-----------------------------------------
1 file changed, 16 insertions(+), 59 deletions(-)
diff --git a/debian/README.Debian b/debian/README.Debian
index 56dfadc..17fe399 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -7,7 +7,7 @@
Last update: May. 18 2016
Package Scheme
---------------
+==============
Caffe supports 2 modes: CPU_ONLY mode and CUDA mode, and actually the
caffe configureed in CUDA mode can run in CPU_ONLY mode. So providing
@@ -22,26 +22,28 @@ Both of the sources are hosted on Alioth, debian-science.
Here is what binary package can be built from the sources:
* CPU_ONLY set from source "caffe"
- - caffe-cpu -- command line utilities
+ - caffe-cpu -- metapackage, pulls tools and python3 interface
+ - caffe-tools-cpu -- command line utilities
- libcaffe-cpu* -- core library
- libcaffe-cpu-dev -- development files
- - python-caffe-cpu -- python2 interface
+ - python3-caffe-cpu -- python3 interface
* CUDA set from source "caffe-contrib"
- - caffe-cuda
- - libcaffe-cuda*
- - libcaffe-cuda-dev
- - python-caffe-cuda
+ - caffe-cuda -- ...
+ - caffe-tools-cuda -- ...
+ - libcaffe-cuda* -- ...
+ - libcaffe-cuda-dev -- ...
+ - python3-caffe-cuda -- ...
-Just choose one and enjoy Deep Learning, then good luck in
-tweaking parameters and writing papers!
+Just choose one that fits your need and enjoy Deep Learning,
+then good luck in research or playing around!
Why do We Link Caffe Against libblas.so.3 ?
--------------------------------------------
+===========================================
Well this is neither accidental nor awkward. This is due to a
-Debian feature called `alternatives`.
+Debian feature called `alternatives`. (So does Ubuntu)
`libblas.so.3` is a symbol link, you can make it point to
either `atlas` or `openblas` without rebuilding Caffe.
@@ -62,58 +64,13 @@ then update the alternatives:
$ sudo update-alternatives --config libblas.so
Finally you run Caffe again. Is it faster as you expected?
-
-
-Custom Build of Caffe
----------------------
-
-How to compile these packages by myself?
-
-0. choose and download source package with `apt-get source <source>`,
- available sources are "caffe" and "caffe-contrib".
-
-1. Install Build-Dependencies, including Debian packaging utils.
-
- $ apt install build-essential debhelper devscripts
- $ apt-get build-dep [caffe | caffe-contrib]
-
-2. [Optional] Change CMAKE flags in debian/rules if you wish,
- but there is no promise whether your customized build will pass.
-
- If you are familiar with CMAKE and able to read debian/rules,
- you might hack this variable
- * CONFFLAG_*
-
-3. Start compiling, make sure you are in the root of source tree.
-
- $ dpkg-buildpackage -us -uc -j4
-
- This will start the compiling process with 4 threads in parallel.
-
-4. Install the resulting .deb packages.
-
- * Check the resulting packages
- $ ls ../*.deb
-
- * If nothing went wrong, install them. I recommend you
- to first install the libcaffe package.
- $ sudo dpkg -i libcaffe-*.deb
- $ sudo dpkg -i <others>
-
-5. Grab some datasets, set up your network and see if it works as
- you expected. If you can't be lazier, run this script
-
- $ debian/tests/simple
-
- If it doesn't explode, then we can conclude that it works, at
- least for Convolution layer, Pooling layer, InnerProduct layer,
- ReLU layer and Softmax layer.
+For more detail pleese see update-alternatives(8).
Notes for Package Maintainer
============================
-1. Testing whether the program works, apart from the test programs?
+1. Testing whether the program works, apart from the gtest test programs?
$ caffe time -model examples/mnist/lenet.prototxt
@@ -125,5 +82,5 @@ Notes for Package Maintainer
requires no dataset, which may be useful for some maintainers
who are not familiar with Caffe.
- If you want to test Caffe on some real dataset, you can take
+ If you want to test Caffe on some real dataset e.g. MNIST, you can take
a closer look at `examples/mnist/readme.md`.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-science/packages/caffe.git
More information about the debian-science-commits
mailing list