Starting 2016, the CAPRI model shall be made more accessible to the scientific community by the provision of supported stable releases, a.k.a. Stars. The first Star was published at the end of November 2016. The idea behind the Star is to provide a well tested version of the model, that does not change over time save, and where maintenance releases address critical issues. The release notes are updated in a cumulative fashion.

From release 2.0 we decided to make all releases of CAPRI publicly available without going through a developer. Please refer to the release notes for more information about each release.

Star 2.3

Star 2.2

Star 2.1

Star 2.0

Star 1.4

Star 1.3

Star 1.2

Star 1.1

Star 1.0

Users that have participated in the CAPRI training courses will have access to the code base and the model via the Subversion Numbering system (SVN), and the instructions here do not apply to such users. They should point their SVN client to the tags “STAR_N.N” on the SVN server to obtain the release versions (N.N) of CAPRI.

Please refer to the release notes for more information about each release.

The model code contains all raw data and routines for building the CAPRI data sets needed to run the system. However, doing so can be tedious, technical and error prone. Here, we therefore provide a standard data base for selected releases.

Data bases for selected releases, doing away with the need to build all databases if extracted into the *results* directory of your model installation.

Database and results for STAR 2.3

Database and results for STAR 2.2

Database and results for STAR 2.1

Results from STAR 1.4, including scenarios for use with the CAPRI tutorial (2018 training session material)

Results from STAR 1.3

CAPRI requires that you have a windows computer with Java runtime environment (64-bit) and GAMS (distribution 24.7 or later, http://www.gams.com) installed. You need a license for the CONOPT solver.

Using CAPRI requires extensive knowledge of how the system works. Please look out for CAPRI training courses on the page of upcoming events. The following bare-bone instructions may nevertheless be sufficient to get the system up and technically running.

1. Create an installation folder to hold model source files on your local hard drive such that the path does not contain spaces. Thus, it will not work to install the model in “My Documents” (path containing space) or on a network drive (the access will be too slow).
2. Extract the files of the compressed archive into the folder you just created.
3. Go to the subfolder GUI, double-click “start_capri.bat”. That should open the graphical user interface (GUI). If not, something is wrong with your Java-installation.
4. In the menu settings, choose Edit settings.
   1. In the first tab: enter your name
   2. In the second tab: verify that the paths to result and restart folders are set to ..\output\results and ..\output\restart. The GAMS directory should read ..\gams and the data directory should read ..\dat.
   3. In the third tab: enter the complete path to the GAMS executable. Probably it is c:\gams\win64\24.7\gams.exe. Also verify that the path to the Scratch directory is ..\output\temp. Click the button to “get number of processors”.
   4. In the fourth tab: do nothing.
   5. In the final tab: do nothing.
5. Click “Save in caprinew.ini” and accept the file name suggested for your settings.
6. Close the GUI, then start it again (using start_capri.bat), to make it process your settings.

Now you need to build all databases of CAPRI. This takes a very long time. Depending on the hardware you use, it can take up to several days.

1. In the GUI, choose the workstep “Installation” and then execute the GAMS program. It will create the necessary sub-directories to hold result and restart files.
2. In the GUI, choose the menu GUI –> Batch execution
3. In the dialogue, choose the file “<gamsdir>\GUI\batchfiles\build_database_and_baseline.txt”
4. Uncheck the option “Only compile the GAMS programs”
5. Click “Start batch execution”.
6. Wait for the program to finish (hours, days).
7. Click “Open HTML report” and verify that all steps were completed without errors (RC=0).