pik-piam / edgeTransport

A detailed transport sector model.
5 stars 15 forks source link

Unit of Capital Cost variables #237

Closed orichters closed 2 weeks ago

orichters commented 9 months ago
jmuessel commented 9 months ago

If I am not mistaken, in EDGET we usually use as a cost unit $2005/(p or t)km, which we do not change in the reporting script. But, in the reporting you are referring to it is different: Overview:

capCosts <- loadCapCosts(demand_km)
repCapCosts <- reporting(dt = capCosts, mode = "CC")

We then add repCapCosts to the mif file.

In detail: loadCapCosts multiplies costs in $2005/km with demand_km

So capCosts is in $2005

reporting takes capCosts [$2005] as an input, makes no unit changes --> so we end up with $2005

orichters commented 9 months ago

But isn't demand_km in km/yr, and therefore capCost in $2005/yr?

robertpietzcker commented 9 months ago

yes, I agree with Oliver - the unit of the aggregate value calculated from (cost per km) times (km per year) should be bn$2005/yr

Also on the first part - for harmonizing variable names and reducing the potential for misunderstandings, I would call this absolute value something like Energy Investments|Demand|xxx to be in line with current REMIND naming (the IAMC uses Investment|Energy Demand|xxx, but I would prefer to be consistent within REMIND on this)

jmuessel commented 9 months ago

@robertpietzcker I wrote on my non-urgent todo list "Rename CC in reporting, example: Capital Cost|Transport|Pass|Rail --> Energy Investments|Demand|Transport|Pass|Rail"

Could you quickly confirm that this is, what I am supposed to do?

robertpietzcker commented 9 months ago

yes, that would be perfect.

and similarly, check if the units are correct - so "$2005/[p/t]km" for the intensive variable handed to REMIND (in case that is ever reported), and "bn $2005/yr" for the extensive variable that you get when multiplying the intensive variable by the transport volume

orichters commented 2 weeks ago

The variable has been removed in EDGE-T 2.0.0