This hasn't changed the behaviour of the optimizations or model, just simply fixed bugs and added additional outputs
Fix 'cascade' plot labels overlapping when downloaded from FE
Fix 0/0 error in money optimization
Ensure programset and optimization constraints are in the same order by reordering the progamset to match optim.constraints
Make optimization more bug-proof by using program keys eg "ART" instead of optiminds [0,1,2...] (maintained backwards compatibility)
when optiminds are used, calcoptimindsoptimkeys() ensures they match the optimkeys
Add fixproppmtct to the model so it is actually used
Note that fixproppmtct is based off calcproppmtct which is: number of mothers on PMTCT / number of mothers who know their status - This may need to be changed...
note that there is no targetted testing of pregnant women, so the number on PMTCT may be too low if not enough women know their status.
Fix bug where 'numpmtct' wasn't annualised in the results, giving "HIV+ women receiving PMTCT" plot was 5 times too low
Add data points to "HIV+ women receiving PMTCT" (note that the model may not have as many mothers on PMTCT see above)
Add proppmtct to the results.main: the proportion of HIV+ mothers that are on PMTCT. Again, if you fixproppmtct, this might not stay constant because fixproppmtct fixes: num on PMTCT / num of mothers who know their status
Remove 'ageing rate' from the list of parameters that programs can affect
Improve error message in the FE Cost Functions tab when partnerships change
Propcare now brings people from both dx (and not in care) and lost into care, puts them down into lost if too many in care. (previously brought up only from dx, down back dx if too many in care)
Fixed when propcare was set, people weren't getting linked to care because there were enough in care.
Unfinished:
Warning when optimization and budget scenario is run with parset that has fixed proportions
PMTCT currently has proppmtct = numpmtct / hiv+dxmothers, which is less intuitive than numpmtct / allhiv+mothers
Questions:
Should 'ageing rate' be removed from parameter scenarios as well?
Removing ageing rate from programs was done with a list in the code for the backend - other option is to make a new column in model-inputs.xlsx but that seems a little bit overkill for just one or two parameters. Is the current fix ok
Should clicking the FE warning do anything in particular? eg. the help buttons take you to a location in the User Guide
This hasn't changed the behaviour of the optimizations or model, just simply fixed bugs and added additional outputs
Fix 'cascade' plot labels overlapping when downloaded from FE
Fix 0/0 error in money optimization
Ensure programset and optimization constraints are in the same order by reordering the progamset to match optim.constraints
Make optimization more bug-proof by using program keys eg "ART" instead of optiminds [0,1,2...] (maintained backwards compatibility)
when optiminds are used, calcoptimindsoptimkeys() ensures they match the optimkeys
Add fixproppmtct to the model so it is actually used
Note that fixproppmtct is based off calcproppmtct which is: number of mothers on PMTCT / number of mothers who know their status - This may need to be changed...
Fix bug where 'numpmtct' wasn't annualised in the results, giving "HIV+ women receiving PMTCT" plot was 5 times too low
Add data points to "HIV+ women receiving PMTCT" (note that the model may not have as many mothers on PMTCT see above)
Add proppmtct to the results.main: the proportion of HIV+ mothers that are on PMTCT. Again, if you fixproppmtct, this might not stay constant because fixproppmtct fixes: num on PMTCT / num of mothers who know their status
Unfinished:
Questions: