You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SINGA committers are members that have write access to SINGA code and documentation repositories. They can contribute by themselves and accept other contributions.
92
+
93
+
Becoming a SINGA committer requires understanding the Apache Way and being an active member in the SINGA project. An active member participates on mailing lists, answers questions, contributes code, tests and documentation, presents SINGA in talks and seminars, verifies releases and report issues or feature requests.
94
+
95
+
New committers can be suggested by current committers or PPMC members, and voted upon by the PPMC according to Apache guidelines. You can start by talking to other committers and ask for their advice and guidance.
To make the installation command simple, we create the following additional packages which depend on the latest CPU and GPU SINGA packages.
82
+
To make the installation command simple, you can create the following additional packages which depend on the latest CPU and GPU SINGA packages.
63
83
64
84
# for singa-cpu
65
85
conda build tool/conda/cpu/ --python=3.6
@@ -88,7 +108,7 @@ To build SINGA with GPU, MKLDNN, Python and unit tests, run the following instru
88
108
pip install .
89
109
90
110
The details of the CMake options are explained in the last section of this page.
91
-
The last command install the Python package. You can also run `pip install -e .`, which creates symlinks instead of copying files into python the site-package folder.
111
+
The last command install the Python package. You can also run `pip install -e .`, which creates symlinks instead of copying the Python files into the site-package folder.
92
112
93
113
If SINGA is compiled with ENABLE_TEST=ON, you can run the unit tests by
94
114
@@ -97,10 +117,13 @@ If SINGA is compiled with ENABLE_TEST=ON, you can run the unit tests by
97
117
You can see all the testing cases with testing results. If SINGA passes all
98
118
tests, then you have successfully installed SINGA.
99
119
120
+
100
121
## Use native tools to Build SINGA on Centos7
122
+
101
123
Building from source will be different for Centos7 as package names differ.Follow the instructions given below.
@@ -142,7 +165,7 @@ Instructions for building on Windows with Python support can be found [here](ins
142
165
143
166
## More details about the compilation options
144
167
145
-
### USE_MODULES
168
+
### USE_MODULES (deprecated)
146
169
147
170
If protobuf and openblas are not installed, you can compile SINGA together with them
148
171
@@ -164,7 +187,7 @@ the following environment variables
164
187
165
188
### USE_PYTHON
166
189
167
-
Similar to compile CPP code, PySINGA is compiled by
190
+
Option for compiling the Python wrapper for SINGA,
168
191
169
192
$ cmake -DUSE_PYTHON=ON ..
170
193
$ make
@@ -178,7 +201,7 @@ Users are encouraged to install the CUDA and
178
201
[cuDNN](https://developer.nvidia.com/cudnn) for running SINGA on GPUs to
179
202
get better performance.
180
203
181
-
SINGA has been tested over CUDA 9, and cuDNN 7. If cuDNN is
204
+
SINGA has been tested over CUDA 9/10, and cuDNN 7. If cuDNN is
182
205
installed into non-system folder, e.g. /home/bob/local/cudnn/, the following
183
206
commands should be executed for cmake and the runtime to find it
184
207
@@ -249,19 +272,14 @@ This setting is used to build the Debian package. Set PACKAGE=ON and build the p
249
272
250
273
## FAQ
251
274
252
-
* Q: Error from 'import singa' using PySINGA installed from wheel.
275
+
* Q: Error from 'import singa'
253
276
254
-
A: Please check the detailed error from `python -c "from singa import _singa_wrap"`. Sometimes it is
255
-
caused by the dependent libraries, e.g. there are multiple versions of protobuf, missing of cudnn, numpy version mismatch. Following
256
-
steps show the solutions for different cases
257
-
1. Check the cudnn and cuda and gcc versions, cudnn5 and cuda7.5 and gcc4.8/4.9 are preferred. if gcc is 5.0, then downgrade it.
258
-
If cudnn is missing or not match with the wheel version, you can download the correct version of cudnn into ~/local/cudnn/ and
277
+
A: Please check the detailed error from `python -c "from singa import _singa_wrap"`. Sometimes it is caused by the dependent libraries, e.g. there are multiple versions of protobuf, missing of cudnn, numpy version mismatch. Following steps show the solutions for different cases
278
+
1. Check the cudnn and cuda. If cudnn is missing or not match with the wheel version, you can download the correct version of cudnn into ~/local/cudnn/ and
2. If it is the problem related to protobuf, then download the newest whl files which have [compiled protobuf and openblas into the whl](https://issues.apache.org/jira/browse/SINGA-255) file of PySINGA.
263
-
Or you can install protobuf from source into a local folder, say ~/local/;
264
-
Decompress the tar file, and then
282
+
2. If it is the problem related to protobuf. You can install protobuf (3.6.1) from source into a local folder, say ~/local/; Decompress the tar file, and then
265
283
266
284
$ ./configure --prefix=/home/<yourname>local
267
285
$ make && make install
@@ -366,7 +384,7 @@ This setting is used to build the Debian package. Set PACKAGE=ON and build the p
366
384
367
385
After this, you can build glog again.
368
386
369
-
* Q: When using virtual environment, everytime I run pip install, it would reinstall numpy. However, the numpy would not be used when I `import numpy`
387
+
* Q: When using virtual environment, every time I run pip install, it would reinstall numpy. However, the numpy would not be used when I `import numpy`
370
388
371
389
A: It could be caused by the `PYTHONPATH` which should be set to empty when you are using virtual environment to avoid the conflicts with the path of
372
390
the virtual environment.
@@ -377,7 +395,7 @@ This setting is used to build the Debian package. Set PACKAGE=ON and build the p
* Q: When I run PySINGA in Mac OS X, I got the error "Fatal Python error: PyThreadState_Get: no current thread Abort trap: 6"
398
+
* Q: When I run SINGA in Mac OS X, I got the error "Fatal Python error: PyThreadState_Get: no current thread Abort trap: 6"
381
399
382
400
A: This error happens typically when you have multiple version of Python on your system and you installed SINGA via pip (this problem is resolved for installation via conda),
383
401
e.g, the one comes with the OS and the one installed by Homebrew. The Python linked by PySINGA must be the same as the Python interpreter.
@@ -387,4 +405,4 @@ This setting is used to build the Debian package. Set PACKAGE=ON and build the p
If installed PySINGA from binary packages, e.g. debian or wheel, then you need to change the python interpreter, e.g., reset the $PATH to put the correct path of Python at the front position.
408
+
If installed PySINGA from binary packages, e.g. debian or wheel, then you need to change the python interpreter, e.g., reset the $PATH to put the correct path of Python at the front position.
0 commit comments