| 1 |
Common problems/troubleshooting |
| 2 |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 3 |
.. _lnxtrb: |
| 4 |
|
| 5 |
* Sometimes, compilers can have trouble if there are spaces in the filepath. Try |
| 6 |
installing RAW so that there are no spaces in the file path (navigate the folder |
| 7 |
in the terminal, type ``pwd`` and see what the result is). |
| 8 |
|
| 9 |
* If you have installed a standalone python distribution (such miniconda/anaconda), |
| 10 |
it is possible that it isn’t set to default, so when you run ``python RAW.py``, |
| 11 |
you are using the wrong python. |
| 12 |
|
| 13 |
* You can verify which python you are using the command ``which python`` in the terminal. |
| 14 |
|
| 15 |
* You can set the correct python to default by modifying your appropriate profile |
| 16 |
file (such as the .bash_profile), or setting the :envvar:`$PATH` environmental variable. |
| 17 |
|
| 18 |
* You can also specify the full path to the version of python you want to use in |
| 19 |
the command, such as ``~/miniconda3/bin/python`` |
| 20 |
|
| 21 |
* Note that when you change environmental variables in one terminal window, you need to |
| 22 |
restart other windows for this to take effect. If you aren’t using the right python |
| 23 |
(or compiler, etc), trying closing all of your terminal windows and opening a new one. |
| 24 |
|
| 25 |
* If you fail to build the extensions before running RAW, RAW will crash at some point. |
| 26 |
Be sure to run the ``python setup.py build_ext --inplace`` before starting RAW. |
| 27 |
|
| 28 |
* Using the RAW autorg function requires a relatively recent version of numba. |
| 29 |
If you get an error running this function update your numba version to the |
| 30 |
most recent. |
| 31 |
|