From 2016, the CAPRI model was made more accessible to the scientific community by the provision of supported stable releases. The stable releases are tagged and “frozen” versions of the model that can be referenced to and that will not change. The bug fixes and other code updates result in new releases with updated revision numbers. The release versions have been subjected to extensive testing, ensuring that all supported features technically work under different hardware/software settings.
The stable release consists of (a) the model code including raw data and (b) the compiled data base including calibrated baselines. The model is really self contained in (a), since all software and raw data needed to compile the data bases and construct the baselines is found there. Albeit (b), the databases, can be derived from (a), doing so is a somewhat complicated process. Therefore, we provide (b) as a shortcut. Furthermore, it turns out that generating (b) may generate slightly different results on different hardware/software combinations, and therefore it is convenient to use a common versioned database release.
The current release and selected previous releases can be downloaded as compressed (zipped) archives using the links in the following table. Note that the item “SVN-tag” only are available to developers with a an account in the SVN database. Information about each release is found in the release notes, Release notes (cumulative) and in each release code base.
CAPRI requires that you have a windows computer with Java runtime environment (64-bit) and GAMS (http://www.gams.com, distribution 28.2 or later is recommended) installed. You need a license for the CONOPT solver. Many tasks in CAPRI utilize parallel computing. It is therefore an advantage if you have a machine that can run many threads in parallel.
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.
The stable releases are shipped with only input data, but not with any of the consistent model databases needed to run the model. As mentioned above, there are two options for obtaining the complete and consistent databases needed by and fitting with the CAPRI model.
If you download the data as a compressed archive, you decompress the archive and place all the files and folders in the result directory of your capri model installation. For example, assume you installed the model in the directory
C:/CAPRI_STAR_2.5. Then you place the files and folders extracted (see below) in the folder
C:/CAPRI_STAR_2.5/output/results. The following files and folders should be extracted:
Those are created by tasks executable from the GUI. So, now you need to build all databases of CAPRI. This takes a long time. Depending on the hardware you use, it can take up to several days. In order to keep track of all the various settings required for completing all the steps, the release contains a “batch execution file” that instructs the GUI how to carry out a sequence of tasks without intervention of the user. Here is what you need to do:
The current batch execution file (STAR 2.5) does not take over the path to your GAMS installation as entered in the settings dialogue during installation, but you will have to open the text file and enter the appropriate path manually.
Update of the graphical user interface (GUI) to allow the use of the policy editor.
Several modifications of the premium payments, for the Basic Payment Schemes, where the results were found not to fit observations.
This maintenance release addresses …
This maintenance release addresses stability of feeding, reporting for fertilizers, and also includes some cleaning up of code:
This maintenance release resolves several important calibration issues.
This maintenance release implements the revised treatment of fertilizers and feed. For fertilizers, a bi-level programming approach has been implemented, where the flows of fertilizers are modelled as a Bayesian estimator ensuring an interior solution that is “close to” the calibrated flows when simulating and close to a prior distribution when calibrating. For feed, the distribution of feeding stuffs to animals was revised to improve plausibility and stability, but without principal changes of the way the model works.
In addition to the feed and fertilizer modifications, the following bugs or minor issues were addressed:
Finally, the testing routines were augmented and slightly revised, to include individual testing of simulations with supply and market models standalone.
This new series of releases contains two key modifications:
Some modifications that were scheduled for this release were not included, because they were not sufficiently stable in testing at the key date for the release. In particular, the following components are essentially unchanged from STAR 1.3 but scheduled for inclusion in a subsequent release.
Finally, this release has some known issues in addition to the points mentioned above:
A maintenance release addressing the following issue in STAR 1.2:
It was observed that when the GUI batch execution file “build_database_and_baseline.txt” was executed with this model version, the baseline calibration of the market model sometimes failed.In that case, a manual re-start of that task directly from the GUI using the default settings worked. Furthermore, it was observed that the baseline reproduction run (i.e. calibrating to mtr_rd_cal and then simulating mtr_rd_ref) resulted in small changes in some of the “new” member states, in particular Serbia.
A maintenance release addressing two minor problems encountered in STAR 1.1.
This is a maintenance release addressing some issues that surfaced since STAR 1.0 was published.
This release attempts to provide a CAPRI model where a wide selection of tasks from baseline construction to simulation can be carried out. With other versions of CAPRI, it has been a general feature that when some tasks were maintained, others ceased to work, so that there were multiple model versions where some problems had been resolved but where not everything worked properly.
Since it is utopic to aspire that all mechanisms ever built into CAPRI would work simultaneously, a selection of “supported features” was created. Features of the model that are not “supported” are simply not tested, and so they may or may not perform as intended. The list of supported features is documented in programmatic form in the GUI batch execution file “supported_features.txt”.
Some features that should be supported still fail to work properly. In particular, we note that the following technical problems persist:
The release has not been systematically tested from a content point of view. Nevertheless, release candidates have been used in a few applications, where some issues have surfaced. In particular, the distribution of rural development funds needs to be revised. Such revision has partially been done already in various projects, but the modifications need to be consolidated and integrated into a maintenance release. Similar improvements have accumulated in the areas of market model tariff data and greenhouse gas emissions, also foreseen to be integrated in a future maintenance release, after thorough testing.