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
So far in the model, household benefit are calculated using the "loyer" variable.
It is assumed that each familiy pay the rent of its household (men) but in case of more than one family that rent should be shared into the families.
You can think about house-sharing to be convinced.
By the way, if I'm not wrong, there is a special legislation in that case.
The text was updated successfully, but these errors were encountered:
Comment by benjello from Tuesday Apr 16, 2013 at 15:40 GMT
Yes, we should do something for both splitting the loyer and house sharing (variable coloc).
I think we included the variable (but it is fixed to False) and wrote the legislation to take care of it.
But we didn't do the entire work since we usually excluded student from our analyis.
If you have an idea to fix that please do not hesitate to share ypur thoughts (remember that loyer are imputed ...)
Comment by AlexisEidelman from Wednesday Apr 17, 2013 at 13:00 GMT
The simplest and safest way to do it should be to deal with that issue during the imputation.
The rent value maybe be imputed only at a house level I presume but as families are already in input dataset, we can share that rent between them.
Then "loyer" become an family-entity variable. The sum over families get the household real rent.
Issue by AlexisEidelman from Tuesday Apr 16, 2013 at 08:23 GMT
Originally opened as https://github.com/openfisca/openfisca/issues/159
So far in the model, household benefit are calculated using the "loyer" variable.
It is assumed that each familiy pay the rent of its household (men) but in case of more than one family that rent should be shared into the families.
You can think about house-sharing to be convinced.
By the way, if I'm not wrong, there is a special legislation in that case.
The text was updated successfully, but these errors were encountered: