You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a new global electrification scenario by describing more ambitious electrification levels in every sectors within SSP scenarios. And I've checked previous discussions about share-weights, which are very helpful. And I noticed that adjusting fuel preference elasticity is a more common choice, especially in different sector-SSP.xml. Using Building_SSP1.xml and Building_SSP3.xml as examples, fuel preference elasticity is respectively -1.5 and 0 applying fill-out rule. I didnt find anyting helpful about explaining it in the documentary but a simplified definition "Elasticity dictating how share weights change with GDP per capita". But I dont know how model uses it or mathematical formulas. And how to calibrate the fuel preference elasticity if I want to increase the share of electrification? I would be very grateful for any help offered.
The text was updated successfully, but these errors were encountered:
Dear all,
I'm working on a new global electrification scenario by describing more ambitious electrification levels in every sectors within SSP scenarios. And I've checked previous discussions about share-weights, which are very helpful. And I noticed that adjusting fuel preference elasticity is a more common choice, especially in different sector-SSP.xml. Using Building_SSP1.xml and Building_SSP3.xml as examples, fuel preference elasticity is respectively -1.5 and 0 applying fill-out rule. I didnt find anyting helpful about explaining it in the documentary but a simplified definition "Elasticity dictating how share weights change with GDP per capita". But I dont know how model uses it or mathematical formulas. And how to calibrate the fuel preference elasticity if I want to increase the share of electrification? I would be very grateful for any help offered.
The text was updated successfully, but these errors were encountered: