You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new scenarios for consumables availability work well if set at initialisation, however they are not switching consumables availability correctly when using cons_availability_postSwitch. The initial cons availability remains throughout the full simulation.
Note, existing scenarios all_vital_available, all_medicines_available etc do work with the switch.
In tests/test_consumables.py, there is a new test (test_check_consumables_modified_correctly) which initially sets the consumables availability to 'none', then switches it to scenario6 (all consumables at or above 75th percentile).
Currently, the final assertion fails. This is because after the switch, the consumables availability is still set to 'none'.
Once the consumables scenarios are correctly modifying availability, we expect this test to pass.
PR #1495 (#1495) originally proposed a fix for this which has already been merged into this working branch.
The text was updated successfully, but these errors were encountered:
The new scenarios for consumables availability work well if set at initialisation, however they are not switching consumables availability correctly when using cons_availability_postSwitch. The initial cons availability remains throughout the full simulation.
Note, existing scenarios all_vital_available, all_medicines_available etc do work with the switch.
This is the working branch for the GF and FCDO scenarios:
https://github.com/UCL/TLOmodel/tree/tara/gf_hss_and_htm_scale_up
In tests/test_consumables.py, there is a new test (test_check_consumables_modified_correctly) which initially sets the consumables availability to 'none', then switches it to scenario6 (all consumables at or above 75th percentile).
Currently, the final assertion fails. This is because after the switch, the consumables availability is still set to 'none'.
Once the consumables scenarios are correctly modifying availability, we expect this test to pass.
PR #1495 (#1495) originally proposed a fix for this which has already been merged into this working branch.
The text was updated successfully, but these errors were encountered: