Affordability KPI "income" column & Total Monetary Cost

arup-group / gelato

Gelato turns MATSim outputs into transport sustainability KPI metrics

GNU General Public License v3.0

9 stars 1 forks source link

Affordability KPI "income" column & Total Monetary Cost #72

Open divyasharma-arup opened 6 months ago

divyasharma-arup commented 6 months ago

Looking at the implementation for writing this KPI, I think it's looking for a column name income, but in the Paris East sim, it is actually labelled householdIncome. Is there a standard MATSim input column for income? Perhaps we should use that, or ask the user to enter what the column should be. Because it is householdIncome in the Paris East sim, the user only receives intermediate outputs by subpopulation, so we can't validate the percentile income functionality.

divyasharma-arup commented 6 months ago

Also, a note that when trying this on the leg_logs from: gelato alpha 0.03, with outputs saved here: /mnt/efs/analysis/ds/gelato_outputs/baseline_30pct, I get a total_daily_monetary_cost of €523,450 as a straight sum from the legs table, which I think is what Gelato is doing too. But Gelato returns €4,711,058, so there's some sort of discrepancy here in method that makes the average daily cost in Gelato outputs much higher than what I'm calculating from legs table.

KasiaKoz commented 6 months ago

Some notes after a chat on slack:

for the income column, we could just look to find a column that has a mention of income in the name, so it could be income, householdIncome, hhld_income etc.
I think the second point might be the same problem as here: https://github.com/arup-group/gelato/issues/73. I think we should have a separate table for people, their attributes, income etc. and then a separate ones for their scoring params.