Version 28 (modified by tcbennun, 5 months ago) (diff)

add GNU Make and VC++ 2015 detail

Easy Developer Setup Using Anaconda

Step 1 - Install Anaconda

Download the latest 64-Bit Python 2.7 Installer from and run it.

  • The recommended destination folder is as good as any. If you deviate from this then it's probably worthwhile to make sure the path is short and contains no spaces, and is not the same as any previous installation (one reader installed 64 bit on top of previous 32 bit, not a good idea).
  • At the Advanced Options screen, you need to consider whether or not you want to make Anaconda your default version of Python. Developers who do not work on multiple Python projects can just accept the defaults here.
  • By default of Windows anaconda is installed for single user and not "everyone", which means you cannot run the conda command from an arbitrary command window. If you proceeded with default installation, you need to open Anaconda Prompt from Menu Start. Otherwise you can install anaconda for everyone, which requires root privlidges. If "conda" is not a recognised command then add the install directory to your Windows user Path variable.
  • If you have a failing reference to a "" file, then edit this out of the anaconda start up file at users/username/.condarc as you may still have left it there from an older sasview installation system.

Step 2 - Download SasView and sasmodels from github

If you don't have git installed, go to the GIT section below (Step 7) for instructions, otherwise simply run

git clone sasview
git clone sasmodels

Step 3 - Install dependencies

Go to folder:


and create conda enviroment using yml specific for your platform (needs to be run from top-level not within a conda virtual environment)

conda env create -f sasview-env-build_win.yml

#Mac OSX
conda env create -f sasview-env-build_osx.yml

conda env create -f sasview-env-build_linux.yml

Other dependencies

Note that in order to build the documentation, you will require a version of GNU Make (the make command). On Linux, you can obtain this with your package manager. On Windows 7, activate your new conda environment and run the following:

conda install -c conda-forge make

On Windows 10, you may find that the make command does not work with the above method. You can find a Windows-compatible build of GNU Make here: Ensure that you add the install directory to your PATH.

TODO Mac instructions?

Step 4 - activate conda enviroment

activate sasview

else if running from inside a Git Bash shell then use: source activate sasview.

#Mac OSX and Linux
source activate sasview

Step 5 - run SasView

You should be ready to run sasview. Go to sasview directory and run


#Mac OSX and Linux

To build the documentation you will still first need to do:

python docs 

Step 6 - try the new qt gui (work in progress)

Some notes, updated 5th June 2018, based on a Windows 7 install. If you just want to see what the new GUI looks like, Piotr may have a downloadable installer.

SasView? is being reworked, in the ESS_GUI git branch, to use PyQT 5.0 for the GUI. Please note that this branch uses exclusively Python 3. There is no need to install Anaconda again, though, because the environment YAML file (see below) will ensure that Python 3 is installed.

Using Git Bash, cd to your sasview directory and run:

git checkout ESS_GUI

Look for sasview/build_tools/conda_py3_qt5_env.yml, open it in an editor, save it somewhere else outside of git control, remove in the pip section the lines for sasview and sasmodels, then add there: - tinycc==1.1 (the compiler for the models).

[Note - if later whilst running sasview you have problems with models not compiling or loading, close sasview, delete the contents of the directory users/your-user-name/sasmodels/compiled_models, then re-start, which will force re-compilation using the current compiler.]

In an Anaconda prompt (or equivalently in Git Bash, if your Anaconda installation is in your $PATH), run:

conda env create -f=/path-to-your-new-yml-file/conda_py3_qt5_env_new.yml
conda activate qt5

On Windows, as of July 2018, you will need to install Build Tools for Visual Studio 2015. This is found under the 2017 label, confusingly: Download the installer and run it. Find "Visual Studio Build Tools 2017" and click Install. In the window that appears, navigate to "Individual components" and ensure that "VC++ 2015.3 v14.00 (v140) toolset for desktop" and a relevant Windows SDK (e.g. Windows 10 SDK, if you are using Windows 10) are selected. Finally, click Install.

You can now run python as usual to start the application.

If gives an error from line 1140 in readCategoryInfo, you likely have the old version of the categories file. Delete the file serial_cat.json from your user directory ( c:/users/username/.sasview in Windows) and then run the latest *release* version of sasview. This will automatically generate the correct categories.json file.

If qt5 sasview does not run the first time through, try going back to the normal sasview master (git checkout master), then repeat the steps above once more (trust me it may then work!). Piotr and others will be making this easier in the future.

Other useful conda commands

conda info --envs This will show that you now have both sasview and qt5 environments.

conda env remove --name qt5 This will remove the qt5 environment, though the files involved seem to stay on your hard drive so a new conda env create is much faster than the first time.

If something fails part way through creating an environment, such as not removing the pip install for sasview & sasmodels, then "update" will be faster e.g.

conda env update -f=/path to your new yml file/conda_py3_qt5_env_new.yml --name qt5

Step 7 - Install Git (Optional)

Install Git for your platform by following instructions:

When installing on Windows, it may be worthwhile to make sure "Use Git from the Windows Command Prompt" is selected, rather than "Use Git from Bash only". This way you can use git from the same command line as you will use Anaconda.

Set up your credentials:

git config --global "John Doe"
git config --global

If you work behind proxy remmber to configure

e.g. git config --global http.proxy