Fix to read in Legacy versus Updated Consumables RF #1791
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR #1743 added a functionality to choose between the original consumable availability ResourceFile (
ResourceFile_Consumables_availability_small_original.csv) and the updated RF (ResourceFile_Consumables_availability_small.csv), where the former is calibrated to Malawi data and the latter updated the availability at level 1b to be a weighted average of availability at levels 1b and 2.However, the argument "data_source_for_cons_availability_estimates" did not seem to take effect because it was being overriden by what was in
ResourceFile_HealthSystem_parameters.csv.This PR fixes the issue by moving the read consumable availability RF script from the
read_parameters()function topre_initialise_population()