-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add business plan plot #11
Comments
@TomFer97 , we discussed about this, may you be interested in addressing this issue? :) |
Absolutely, I'll open a Pull request asap |
Awesome! :) As a guideline, I feel like the procedure could be as follows:
Both functions created in 3 and 4 shall have an optional argument to describe what user the business plan belongs to, as described in the introduction of this issue |
Which is the differences between? - C_REP_tot_us[y, u] # Replacement costs+ R_RV_tot_us[y, u] # Residual valueI do not understand the differences |
REP stands for replacement. They are the costs to replace the components once they reach their lifetime. RV stands for recover value. They represent equivalent revenues for the components that at the end of the project could last longer. For example, if PVs last 25y but the project last 20, at the end of the project a 20% (5/25) of the value of the PV is reimbursed |
RV is always 0 for all years but the last |
Closed by #12 |
It is useful to add a function into ECModel.jl to show the business plan.
Something like the following image:
The function shall have as mandatory argument only the ECModel, as optional arguments an object that specifies what user shall be plotted and a second object representing the specific final distribution allocation of the total profit.
This last parameter by default is nothing, which means that the overall costs are highlighted, whereas if a specific user is requested the plot the business plan of that specific user is plotted.
As a remark, when a specific user is requested, the additional input of the final distribution allocation is needed to specify how to distribute the rewards across the users
The text was updated successfully, but these errors were encountered: