Conversation
Co-authored-by: smartie2076 <[email protected]>
Co-authored-by: smartie2076 <[email protected]>
Co-authored-by: smartie2076 <[email protected]>
|
All suggestions applied @smartie2076 :) |
|
@ciaradunks @Bachibouzouk is this explaination for the sunk cost workaround understandable for you? |
|
@TheOneAndra, @smartie2076 - I would structure the narrative differently, stating
I would also not hide the title "Including sunk costs for previous investments into specific assets" under "Tips & Tricks". I would simply not have "Tips & Tricks" as a title, rather direcly "Including sunk costs for previous investments into specific assets" (shouldn't it be from instead of for?) |
Would result in something like: Usually, the investments into existing capacities are neglected and assumed to be sunk costs of the system. The existing capacity :code: When optimizing a system with pre-existing capacities of certain assets, it can be usefull for the user to implement the installation costs of these assets in the economic evaluation. With this, it is possible to optimize a system with a specific or a specific minimal capacity of a certain asset and still account for installation costs of the asset at the beginning of the project (in the idea of a greenfield / brownfield optimization). This can work for energy production assets as well as energy conversion assets. For this, following trick can be applied to the input data of the asset in question, by setting:
Previous investment costs into now pre-existing asset capacities are now taken into account in the economic evaluation of a scenario.
That was the original idea but @smartie2076 didn't like it. |
|
@TheOneAndra - can you implement the changes you proposed so we can discuss individual sentences within the github interface :) ? |
I think that the list of tips & tricks can get really expansive, so I am not really favouring to have a lot of files and a lot of sections in the |
I agree. However, right now there is only one tip in "Tips and Tricks", what is the likelyhood that you have more than 2 before the report is submitted? We can leave it as is, the final decision is up to you |
|
@TheOneAndra can you follow up with the comments of @Bachibouzouk? |
Bachibouzouk
left a comment
There was a problem hiding this comment.
Thanks @TheOneAndra , can you rebase on the latest stand of dev? Then you can merge :)
|
Changelog updated @smartie2076 |
Fix #828 #699
Changes proposed in this pull request:
The following steps were realized, as well (if applies):
black . --exclude docs/)EXECUTE_TESTS_ON=master pytest)Please mark above checkboxes as following:
❌ Check not applicable to this PR
For more information on how to contribute check the CONTRIBUTING.md.