CAPRI
images/capri_pic_01.jpg images/capri_pic_02.jpg images/capri_pic_03.jpg

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
capri:gui:gui [2021/06/08 11:30] – Change to DokuWIki matszcapri:gui:gui [2023/06/02 10:28] (current) – [Overview] gocht
Line 3: Line 3:
 ==== Overview ==== ==== Overview ====
  
-[[https://www.capri-model.org/docs/Gui2013.pdf|CAPRI user manual (pdf, 6 MB, 146 pages)]]+{{ :docs:gui2013.pdf |The Graphical User Interface for CAPRI version 2013 (pdf, 6 MB, 146 pages)}}
  
 {{ :capri:gui:gui.jpg?600|}}The aim of the Graphical User Interface (GUI) is threefold. Firstly, it serves as a tool to support the user in **controlling** the different work steps in CAPRI:  {{ :capri:gui:gui.jpg?600|}}The aim of the Graphical User Interface (GUI) is threefold. Firstly, it serves as a tool to support the user in **controlling** the different work steps in CAPRI: 
 +
   * Data base generation, from global to regional, and to 1x1 km grid scale    * Data base generation, from global to regional, and to 1x1 km grid scale 
   * Generation of the [[:capri:concept:refrun|baseline]]    * Generation of the [[:capri:concept:refrun|baseline]] 
-  * Defining and running scenarios \\ +  * Defining and running scenarios  
-That task is eased by the storing [[https://www.capri-model.org/docs/meta.pdf|meta-data information]] along with the quantitative results of the different work steps. \\ \\ + 
-Secondly, it allows to **exploit** the results via tables, graphs and maps. \\ \\ +That task is eased by the storing {{ :docs:meta.pdf | meta-data information}} along with the quantitative results of the different work steps.  
-And thirdly, it offers **certain services** as [[https://www.capri-model.org/docs/batch.pdf|batch execution]], checking meta data, viewing GDX files, [[https://www.capri-model.org/docs/javadoc.pdf|generation of HTML base documentation for the GAMS code]] or integrating GIS geometries into the exploitation tools. \\ \\ + 
-Technically, in order to steer the different working steps, the GUI generates small snippets of GAMS code which are specific for a specific run such as the Member States included, or the base year chosen, and then starts GAMS. That concept allows to run CAPRI completely outside the GUI, e.g. in [[https://www.capri-model.org/docs/batch.pdf|batch mode]]\\ \\ +Secondly, it allows to **exploit** the results via tables, graphs and maps.  
-The different tasks are defined as objects with specific properties (base year, simulation year, scenario ..) which can be modified by the user. Methods allow to retrieve the quantitative results generated by the task as well as meta information.[[https://www.capri-model.org/docs/refactoringGUI.pdf|Read more ..]]\\+And thirdly, it offers **certain services** as {{ :docs:batch.pdf |batch execution}}, checking meta data, viewing GDX files, {{ :docs:javadoc.pdf |generation of HTML base documentation for the GAMS code}} or integrating GIS geometries into the exploitation tools.  
 + 
 + 
 +Technically, in order to steer the different working steps, the GUI generates small snippets of GAMS code which are specific for a specific run such as the Member States included, or the base year chosen, and then starts GAMS. That concept allows to run CAPRI completely outside the GUI, e.g. in {{ :docs:batch.pdf |batch mode}}
 +The different tasks are defined as objects with specific properties (base year, simulation year, scenario ..) which can be modified by the user. Methods allow to retrieve the quantitative results generated by the task as well as meta information.{{ :docs:refactoringgui.pdf |Read more ..}} 
  
 ==== Exploitation tools ==== ==== Exploitation tools ====
Line 21: Line 27:
 Each //view// is firstly characterised by a selection or filter for the different dimensions such as regions, activities, items or scenarios. Secondly, a pivot is defined which maps the data base dimension to viewport dimensions, such as the columns or rows of a table, or the regions shown in a map. And thirdly, it defines the view type: a table, different type of graphs or a map. Fourthly, views may comprise links to other views, similar to the concept of hyperlinks in WEB pages, which allows a "drill-down" like exploitation from general to specific aspects, or vice versa. The hyperlinks can also be used to refer to tables with supporing information. And lastly, the view may comprise supporting information as e.g. units used for specific elements or long text descriptions. Each //view// is firstly characterised by a selection or filter for the different dimensions such as regions, activities, items or scenarios. Secondly, a pivot is defined which maps the data base dimension to viewport dimensions, such as the columns or rows of a table, or the regions shown in a map. And thirdly, it defines the view type: a table, different type of graphs or a map. Fourthly, views may comprise links to other views, similar to the concept of hyperlinks in WEB pages, which allows a "drill-down" like exploitation from general to specific aspects, or vice versa. The hyperlinks can also be used to refer to tables with supporing information. And lastly, the view may comprise supporting information as e.g. units used for specific elements or long text descriptions.
  
-But the user maintains his freedom: he may tune the view to his own needs, by adding his own selections, change the pivot or the view type. Equally, fonts, color, cell sizes or properties of the graphs may be set by the user. His personal settings can be stored for future session. And finally, the mapping viewer allows for rather flexible classifications and coloring options. The details with examples are discussed in a chapter of the [[https://www.capri-model.org/docs/capri_documentation.pdf|CAPRI documentation]].+But the user maintains his freedom: he may tune the view to his own needs, by adding his own selections, change the pivot or the view type. Equally, fonts, color, cell sizes or properties of the graphs may be set by the user. His personal settings can be stored for future session. And finally, the mapping viewer allows for rather flexible classifications and coloring options. The details with examples are discussed in a chapter of the {{:docs:capri-documentation.pdf|CAPRI documentation 2005}}.
  
 ==== Data base concept ==== ==== Data base concept ====
   
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International