-
Notifications
You must be signed in to change notification settings - Fork 25
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
Inconsistent output of FoodExpanditure() and consumptionValue(..., type="food") functions #2
Comments
FoodExpanditure()
and consumptionValue(..., type="food")
functions
FoodExpanditure()
and consumptionValue(..., type="food")
functions
has this been fixed yet? |
I do not understand the issue, and miskos answer.. |
ok, this is the issue:
|
the food expenditure function calculates expenditure based on calories and calorie-prices: p15_prices_kcal(t,iso,kfo)=sum(i_to_iso(i,iso), q15_food_demand.m(i,kfo)); the consumption value function receives its prices from the equation: |
So i see one bug in the food expenditure function, because it omits the multiplication by 365. |
ah, no. the multiplication by 365 is done. |
ah, the food expenditure is by default as per-capita. a = FoodExpenditure(gdx,per_capita=FALSE)[,2050,]
b=consumptionValue("../../inputdata/fulldata.gdx", type="food")[,"y2050",] so everything is fine, no bugs :) |
Ideally this should be the same. For the difference between the output of
FoodExpenditure()
andconsumptionValue(..., type="food")
, it basically comes from usage of different approaches for calculation of prices and quantities, the former using prices per kcal and caloric intake and the latter using prices per tones DM and tDM consumption. Since prices in both case are calculated as Lagrangian multipliers, it could be that the difference in output of functions comes from a general equation system setup in magpie and related interplay between demand variables.The text was updated successfully, but these errors were encountered: