Thanks for posting this, I’m very excited to see the discussion it generates! One note: in the Acute Malnutrition Treatment section under Treatment effects, the sheet linked on “relatively steep discount” is currently private.
Hi there—thanks so much for catching this! Our malnutrition CEA is not yet public because it’s still a work-in-progress. I’ve removed the hyperlink accordingly. Thanks again!
[btw, this is a common problem when using spreadsheets rather than when modeling in a software development environment—the software space has a lot of experience in working in (partially-) open source settings]
The main point is that access management is more natively associated with the structure of the model in software settings. Say, you are less likely to release a model without its prerequisites.
But I agree that this could also be messed up in software environments, and that it’s mainly an issue of UI and culture. I guess I generally argue for a modeling environment that is “modeling-first” rather than something like “explainable-results-first”.
Thanks for posting this, I’m very excited to see the discussion it generates! One note: in the Acute Malnutrition Treatment section under Treatment effects, the sheet linked on “relatively steep discount” is currently private.
Hi there—thanks so much for catching this! Our malnutrition CEA is not yet public because it’s still a work-in-progress. I’ve removed the hyperlink accordingly. Thanks again!
[btw, this is a common problem when using spreadsheets rather than when modeling in a software development environment—the software space has a lot of experience in working in (partially-) open source settings]
Could you expand on this please? Isn’t this going to be roughly equivalent to “we kept our GitHub repo private”?
The main point is that access management is more natively associated with the structure of the model in software settings. Say, you are less likely to release a model without its prerequisites.
But I agree that this could also be messed up in software environments, and that it’s mainly an issue of UI and culture. I guess I generally argue for a modeling environment that is “modeling-first” rather than something like “explainable-results-first”.