It might still be useful to code in 'both'! Python is still far more easier for the programmer for quick and easy stuff. But is a bit annoying to code the GUI. So a workflow, where we test out the math first in python, and then move on to coffeescript so that the 'poets' can play with the model, without needing to touch the code!
Assumption 1 : The parent is the decision maker to decide whether or not send the child to school.
This gives rise to the following possibilities:
1.0 The parent wants to send/continue sending the child to school
1.1 The parent wants to but cannot
1.2. The parent wants to and does.
2.0 The parent does not want to send/continue sending the child to school
There would be potential reasons (perhaps nested in a causes-effect relationship) for each of these three possibilities.
The reasons can be social or economic. The reasons that sound even remotely plausible, given the expertise of (everyone else in) the group, can be worked in as assumptions into the model.
I would have these as the start points. In my mind, community issues are the result of aggregation and infrastructural issues are part of what interventions will work and therefore should be outputs of the model.
Just my two bits.
regards
kalyanaraman
Assumption 1 : The parent is the decision maker to decide whether or not send the child to school.
This gives rise to the following possibilities:
1.0 The parent wants to send/continue sending the child to school
1.1 The parent wants to but cannot
1.2. The parent wants to and does.
2.0 The parent does not want to send/continue sending the child to school