Install Python 2.7.x and pip¶
- Linux – likely to be installed already
- Windows – instructions and downloads are available at python.org
Add Python and the scripts folder to the path¶
Windows only – this is usually automatic in linux
During the Windows Python 2.7 installation, ‘install’ Add Python.exe to Path:
If Python is already installed, you can add Python to Path yourself:
Add the following to the end of the
pathenvironment variable (to see how to edit the environment variables, see http://www.computerhope.com/issues/ch000549.htm):;C:\Python27\;C:\Python27\Scripts\
Setuptools and pip¶
Install setuptools and pip – for details go to http://www.pip-installer.org/en/latest/installing.html. The quick version is as follows:
Download the latest version using the same method as for Windows, or get the version in your package manager, for example:sudo apt-get install python-pip
Pip is normally installed with Python. If it hasn’t been, download the installer script get-pip.py and save it locally – right click and Save link as… or equivalent.
Open a command window (Start menu, cmd.exe) and navigate to the place you saved the get‑pip.py file:python get-pip.py
Quick check of python and pip¶
To check everything is installed correctly so far, type the following in a command window/shell. You should have the version number of pip returned to you:
- Linux - Follow the guide at http://www.rabbitmq.com/install-debian.html
- Windows - Follow the guide at http://www.rabbitmq.com/install-windows.html
For either install, just follow the defaults – no special configurations required.
If you encounter problems running RabbitMQ as a service under Windows then try the following:
Create a folder called
From an administrator command prompt run Advanced System Properties by typing
Create a new system environment variable called
RABBITMQ_BASEand set its value to
In the command prompt navigate to the folder containing the RabbitMQ commands and run:
rabbitmq_service.bat remove rabbitmq_service.bat install rabbitmq_service.bat start
Before continuing, consider virtualenv
Numpy is required for charts.
sudo apt-get install python-numpy # If using a virtualenv, you might need to also do: pip install numpy
Download NumPy from http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy
- Find the right version - look for numpy-X+mkl-cp27-cp27m-win32.whl for 32-bit Windows or
- numpy-X+mkl-cp27-cp27m-win_amd64.whl for 64-bit Windows.
- At the time of writing,
1.14.0- choose the latest version
- Install using pip:
pip install numpy‑1.14.0+mkl‑cp27-cp27m‑win32.whl # update the version number # or pip install numpy‑1.14.0+mkl‑cp27‑cp27m‑win_amd64.whl # update the version number # changing the filename appropriately
Install pynetdicom (edited version)¶
Pynetdicom is used for the DICOM Store SCP and Query Retrieve SCU functions. See DICOM Store and QR for details.
pip install https://bitbucket.org/edmcdonagh/pynetdicom/get/default.tar.gz#egg=pynetdicom-0.8.2b2
Install PostgreSQL database¶
For production use, you will need to install and configure a database. We strongly recommend PostgreSQL, but you can use any of the databases listed on the Django website such as MySQL, Oracle or MS SQL Server, with the limitations listed there. There is one additional limitation - the calculation of median values for charts in OpenREM is dependent on using PostgreSQL.
If this is your first time installing OpenREM and you just want to test it out, you can skip this step and make use of the in-built SQLite database. However, you should expect to start again when you move to a production grade database.
Resources for creating RDSR for older Toshiba CT scanners¶
New in version 0.8.0
If you need to import data from older Toshiba CT scanners into OpenREM then the following tools need to be available on the same server as OpenREM:
For more information see For CT dose summary files from older Toshiba CT scanners. The locations of these executables needs to be configured in the
local_settings.py - see Toshiba CT RDSR creation.
Virtualenv and virtualenvwrapper¶
If the server is to be used for more than one python application, or you wish to be able to test different versions of OpenREM or do any development, it is highly recommended that you use virtualenv or maybe virtualenvwrapper
Virtualenv sets up an isolated python environment and is relatively easy to use.
If you do use virtualenv, all the paths referred to in the documentation will be changed to:
In Windows, even when the virtualenv is activated you will need to call python and provide the full path to script in the Scripts folder. If you call the script (such as openrem_rdsr.py) without prefixing it with python, the system wide Python will be used instead. This doesn’t apply to Linux, where once activated, the scripts can be called without a python prefix from anywhere.