User Tools

Site Tools


getting_started_with_capri

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
getting_started_with_capri [2020/05/20 15:59]
davits [Download the current release]
getting_started_with_capri [2020/06/02 19:05] (current)
matsz
Line 54: Line 54:
  
 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 ​ 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''​. 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:+''​C:​/CAPRI_STAR_2.5/output/results''​. The following files and folders should be extracted:
  
-{{::​installation_result_files_and_folders.png?​400|List of result folders and files extracted and placed in .\output\results}}+{{::​installation_result_files_and_folders.png?​400|List of result folders and files extracted and placed in ./output/results}}
  
 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: 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:
Line 121: Line 121:
   * Changing the order of work steps and tasks in the GUI to reflect the order in which the steps can be carried out (e.g. FAOSTAT first)   * Changing the order of work steps and tasks in the GUI to reflect the order in which the steps can be carried out (e.g. FAOSTAT first)
   * An issue with price experiments in Threads-mode was resolved   * An issue with price experiments in Threads-mode was resolved
-  * Start at an infrastructure to report the results of the fertilizer allocation to DATAOUT (reports\fert_dist_results.gms)+  * Start at an infrastructure to report the results of the fertilizer allocation to DATAOUT (reports/fert_dist_results.gms)
   * Relaxing the winter cover requirement in one Finnish region to avoid infeasibility in baselines.   * Relaxing the winter cover requirement in one Finnish region to avoid infeasibility in baselines.
   * The income computations for EAA had inconsistent prices for FODDER, so that the regional farms had costs <> revenues for fodder, which should not be possible.   * The income computations for EAA had inconsistent prices for FODDER, so that the regional farms had costs <> revenues for fodder, which should not be possible.
Line 161: Line 161:
 A maintenance release addressing two minor problems encountered in STAR 1.1. A maintenance release addressing two minor problems encountered in STAR 1.1.
  
-  *A bug fix in the rural development policy logic (gams\policy\rd_logic.gms). The bug may have caused problems when building a regionalized database if a particular folder (results_out\capmod) was missing.+  *A bug fix in the rural development policy logic (gams/policy/rd_logic.gms). The bug may have caused problems when building a regionalized database if a particular folder (results_out/capmod) was missing.
   *A bug in the batch execution file "​build_database_and_baseline.txt"​ that prevented the farm type databases from being built.   *A bug in the batch execution file "​build_database_and_baseline.txt"​ that prevented the farm type databases from being built.
  
Line 169: Line 169:
   *The scaling of Japanese prices was wrong, leading to biased results in the market model   *The scaling of Japanese prices was wrong, leading to biased results in the market model
   *Several issues relating to the implementation of the second pillar payments, causing them to be missing or wrong in CAPMOD (simulation) and also CAPREG (regional database)   *Several issues relating to the implementation of the second pillar payments, causing them to be missing or wrong in CAPMOD (simulation) and also CAPREG (regional database)
-  *Renaming all the standard scenario files in the folder pol_input\CAP_AFTER_2014,​ so that the (CAPMOD) result file names become shorter and more instructive+  *Renaming all the standard scenario files in the folder pol_input/CAP_AFTER_2014,​ so that the (CAPMOD) result file names become shorter and more instructive
   *A randomly appearing issue with farm type trends. GAMS had problems deleting grid computing handles under full system load (parallel computing)   *A randomly appearing issue with farm type trends. GAMS had problems deleting grid computing handles under full system load (parallel computing)
   *A bug in the user interface that caused the batch execution (e.g. build_database_and_baseline.txt) to launch Turkey (only!) in the wrong way   *A bug in the user interface that caused the batch execution (e.g. build_database_and_baseline.txt) to launch Turkey (only!) in the wrong way
getting_started_with_capri.txt · Last modified: 2020/06/02 19:05 by matsz