-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CAPEX documentation issue #817
Comments
Hey @Alex-Neve, thank you for your suggestion. I am not sure whether the proposed description is general enough. Assume you have a time horizon of less or more than one year. Then the term |
Hi @FabianHofmann , Would you prefer "periodized costs"? This would leave it to the user to pick his/her preferred time-scale. In my sector of the industry we use annualized costs because the investment periods are so long that monthly discounting of the costs would not make sense, but other users may work at different time-scales. If you prefer "periodized costs", I might leave an indication in the CSV files that if periods are defined as years, these periodized costs are identical to annualized costs. Kr, |
Here are the CSV files that I have reworded to avoid the terms "annual" and "annualized". generators.csv |
You can via a fork. |
These CSV files fix the PyPSA issue PyPSA#817 with a corrected description for the capex attribute.
These CSV files fix the PyPSA issue PyPSA#817 with a corrected description for the capex attribute. These files versions are cleaned up from unrelated elements.
These CSV files fix the PyPSA issue PyPSA#817 with a corrected description for the capex attribute. These files versions are cleaned up from unrelated elements.
This reverts commit 8b600df.
Checklist
master
branch or the latest release. Please indicate:Describe the Bug
transformers.csv
generators.csv
lines.csv
links.csv
storage_units.csv
stores.csv
The text was updated successfully, but these errors were encountered: