Update FAQ authored by Leonie Plaga's avatar Leonie Plaga
...@@ -3,18 +3,14 @@ ...@@ -3,18 +3,14 @@
* If you are using windows, you have to add the option --keep-target-files for snakemake. * If you are using windows, you have to add the option --keep-target-files for snakemake.
* **I want to calculate something new with snakemake, but it tells me "nothing to be done".** * **I want to calculate something new with snakemake, but it tells me "nothing to be done".**
* Snakemake does not recalculate files, which are already there. You must delete the file, which has the name of your desired output. * Snakemake does not recalculate files, which are already there. You must delete the file, which has the name of your desired output.
# Common Backbone Error messages
* If GAMS studio shows you an error, you can click on the error message and see in which backbone line the error occured. Helpful to find the cause of the error.
* **Domain Violation Error**
* All grids, nodes, units etc. must be defined in the first sheets of the excel file (grid/node/unit etc.). A domain violation error indicates that in a later sheet (e.g. p_gnu_io), something was referenced, which was not defined in the first sheets. This can be either caused by a missing definition or by a spelling mistake (pay attention here: powerplant is for example not the same as power-plant). When clicking on the error message in GAMS studio, you can find the sheet that causes this error.
* **gdxxrw failed**
* The tool, that converts your excel sheet into GAMS data failed. That is usually caused by mistakes in the backbone command line (Did you spell the pathes right? Did you use the right amount of quotation marks?). Gdxxrw can also fail, if you have double entries in your excel sheet (e.g. twice the unit "lignite powerplant 1" in the unit sheet).
# Backbone # Backbone
* **I have recently downloaded backbone, but it does not work with the Input files from the backbone Wiki** * **I have recently downloaded backbone, but it does not work with the Input files from the backbone Wiki**
* The example data is prepared for the dev-branch of backbone. How to download it, you find here: https://gitlab.vtt.fi/backbone/backbone/-/wikis/Getting-started/Quick-Start * The example data is prepared for the dev-branch of backbone. How to download it, you find here: https://gitlab.vtt.fi/backbone/backbone/-/wikis/Getting-started/Quick-Start
* The newest VTT-files do not use "--input_file" to mark the input-file, but "--input_file_excel". Try using this parameter instead. * The newest VTT-files do not use "--input_file" to mark the input-file, but "--input_file_excel". Try using this parameter instead.
* **When typing in the path to my input data in the command line of GAMS studio, the font becomes red and I get an error when executing backbone.** * **When typing in the path to my input data in the command line of GAMS studio, the font becomes red and I get an error when executing backbone.**
* Check your command for spelling mistakes and unwanted spaces. The path to your data may also not contain spaces. * Check your command for spelling mistakes and unwanted spaces. The path to your data may also not contain spaces.
* **I get really high costs/objective function values.**
* Check your results for dummy generation. Dummy generation occurs, when your system is not sufficient to meet the demand. You find in in the results under r_qGen. If you have dummy generation you have to change your model.
* **I set a constraint (like emissionCap) to 0, but backbone seems to ignore it.** * **I set a constraint (like emissionCap) to 0, but backbone seems to ignore it.**
* GAMS does read parameters with the value 0 as if they were not there. To set a constraint to 0, set it to "eps" instead. * GAMS does read parameters with the value 0 as if they were not there. To set a constraint to 0, set it to "eps" instead.
* **There are no renewable powerplants in my results, although I have set them up in the input file.** * **There are no renewable powerplants in my results, although I have set them up in the input file.**
...@@ -40,6 +36,12 @@ ...@@ -40,6 +36,12 @@
* **The value op01 is not respected as the maximum operation point of a unit.** * **The value op01 is not respected as the maximum operation point of a unit.**
* op01*capacity is not the maximum capacity of the unit - that´s simply "capacity". Just ignore the misleading VTT Wiki "On *p_unit* set *availability* to "1" and define *op00* and *op01* as the limits for operating shares, e.g. if the unit can operate at 40-100 % of maximum capasity, set *op00*=0,40 and *op01*=1,00." * op01*capacity is not the maximum capacity of the unit - that´s simply "capacity". Just ignore the misleading VTT Wiki "On *p_unit* set *availability* to "1" and define *op00* and *op01* as the limits for operating shares, e.g. if the unit can operate at 40-100 % of maximum capasity, set *op00*=0,40 and *op01*=1,00."
# Common Backbone Error messages
* If GAMS studio shows you an error, you can click on the error message and see in which backbone line the error occured. Helpful to find the cause of the error.
* **Domain Violation Error**
* All grids, nodes, units etc. must be defined in the first sheets of the excel file (grid/node/unit etc.). A domain violation error indicates that in a later sheet (e.g. p_gnu_io), something was referenced, which was not defined in the first sheets. This can be either caused by a missing definition or by a spelling mistake (pay attention here: powerplant is for example not the same as power-plant). When clicking on the error message in GAMS studio, you can find the sheet that causes this error.
* **gdxxrw failed**
* The tool, that converts your excel sheet into GAMS data failed. That is usually caused by mistakes in the backbone command line (Did you spell the pathes right? Did you use the right amount of quotation marks?). Gdxxrw can also fail, if you have double entries in your excel sheet (e.g. twice the unit "lignite powerplant 1" in the unit sheet).
# Pypsa-eur # Pypsa-eur
* **When using pypsa-eur, I get the error "symbolic privilege not held".** * **When using pypsa-eur, I get the error "symbolic privilege not held".**
* You must run the shell you are using as administrator. * You must run the shell you are using as administrator.
... ...
......