Economic performance of electricity storage technologies #3268
Conversation
kaskranenburgQ
changed the title
kaskranenburgQ
force-pushed
the
economic-insights-1b
branch
from
4798f79 to
f5d25ee
Compare
| @@ -0,0 +1,2 @@ | |||
| - query = V(transport_bus_flexibility_p2p_electricity, capital_expenditures_per(:mwh_electricity)) | |||
There was a problem hiding this comment.
When I run this query, I get the following error undefined method 'zero?' for nil:NilClass. @kaskranenburgQ did you test this query yourself? Am I doing something wrong?
I think the reason why it might be failing is because the costs parameters are not specified on the node transport_bus_flexibility_p2p_electricity, but on the node transport_bus_using_electricity. Note that just swithcing the nodes probably does not work either, because the flexible behaviour (and therefore the output of electricity), is defined on the node transport_bus_flexibility_p2p_electricity.
| @@ -0,0 +1,2 @@ | |||
| - query = V(transport_car_flexibility_p2p_electricity, full_load_hours) | |||
There was a problem hiding this comment.
Does the issue #3242 play a role here as well?
There was a problem hiding this comment.
Yes, until we fix the issue the full_load_hours will be incorrectly calculated.
We should use the regular transport car electricity node in this query.
There was a problem hiding this comment.
Actually, the p2p nodes do have the full_load_hours specified, which is also queried in the table 'Flexible electricity demand technologies'. Therefore, it's correct to query the flh of the p2p nodes in the flh queries, no need to change this.
| @@ -0,0 +1,2 @@ | |||
| - query = V(transport_bus_flexibility_p2p_electricity, "electricity_output_capacity * number_of_units") | |||
There was a problem hiding this comment.
Similar to my comment below, concerning the electricity output capacity and number of units are not specified on the node transport_bus_flexibility_p2p_electricity, but on the node transport_bus_using_electricity.
There was a problem hiding this comment.
In addition, there are no costs on the electric cars, busses, vans, and trucks nodes.
For the CAPEX, OPEX and economic viability, I propose we leave these technologies out of the table.
For the other columns (Capacity, Full load hours, Revenue), we can show the proper values.
There was a problem hiding this comment.
@kaskranenburgQ let's discuss how we can best cope with this. I see two options:
- If we include them in the table, we should still calculate OPEX since it does consume electricity for a certain electricity price, similarly to the revenue as it sells electricity for a certain price. Then, we can also determine profit based on these OPEX and revenue. We should clearly state in the documentation and perhaps chart description that this is the case for batteries in transport.
- We can choose to leave the batteries in transport technologies out of the table, since as they are currently defined in the model (without investment costs, etc.), it's not possible to calculate a realistic CAPEX, OPEX and profit for now.
...c_performance_storage/batteries_electric_buses_wtp_in_storage_economic_performance_table.gql
Outdated
Show resolved
Hide resolved
kaskranenburgQ
changed the title
This reverts commit b3c01d5.
The node setup and relevant attributes of the deployable capacity of electric vehicles for storage is spread over the regular electric vehicle node and the p2p node. Therefore, applying the cost methods for OPEX and revenue will probably cause issues here. A pragmatic approach is taken here by manually calculating the OPEX and revenue based on electricity in- and output of the p2p nodes and the electricity price curve
|
I've now changed some the capacity, CAPEX, OPEX and revenue queries of storage in electric vehicles, where above mentioned comments regarding the regular and p2p nodes are processed. I expect that the defined cost methods for OPEX and revenue will result in issues for the electric vehicles, due to where cost attributes are defined. Therefore, in this commit I applied a manual approach here to determine OPEX and revenue. @kaskranenburgQ please review this thoroughly and see if you agree with this approach. Otherwise, we can always revert this. |
This PR adds the queries for the table Economic performance of electricity production technologies.
The queries for the revenue are not working at this time.
This column is hidden for now on the ETModel branch.
For testing purposes please use the following branches:
To test the sorting on the WTP, please view the ETModel branch: economic-insights-sorting