PardeeCenterDU / IFs-Issues-Tracking

This repository only holds the list of bugs that have been reported for IFs. Anyone may add a bug report, but please look to see if your issue has already been added!
2 stars 0 forks source link

Driver Diagram #201

Open PardeeCenterIFs opened 2 years ago

PardeeCenterIFs commented 2 years ago

Reflecting all drivers and forward linkages in the driver diagram has always been challenging, and we should consider the option to manually add relationships that are difficult to campture to help the diagram display those, for example the case of WATSAFE:

The path from WATSAN to MFP in the Health model is:

  1. WATSAFE and SANITATION affect Mortality (Diarrhea), which affects Morbidity (HLYLDWORK), which represents the disability contribution to MFPHC.
  2. WATSAFE and SANITATION drive Child Malnutrition (MALNCHP), which drives Stunting, which has a direct contribution to MFPHC. MALCHP also affects Mortality (Diarrhea, Malaria, Resp. Infections and Other CDs for children under 5), which affects Morbidity, which after a few years will affect working age disability too.

During the modeling pod we discussed that WATSAN also affects MFPPC though the infrastructure module, traditional infrastructure contribution (INFRAINDTRAD, which includes INFRAINDWATSAN).

But the diagram only shows:

image

I see that it correctly picks up MALNCHP, but it misses the connection to mortality/morbidity, mostly I think because the direct connection is to internal variables that are age specific, and not the summary variables, like DEATHS or HLYLL, HLYLD. Furthermore shouldn’t we also have a forward linkage showing INFRAINDWATSAN OR INFRAINDTRAD?