Generate chain of events for individuals inc. for mni dataframe #1753
Conversation
Merged master in branch
…intained is generate_event_chains is None
…Log changes to logger.
…th, label what is only used for ddebugging and will be later removed
…ible to all modules. For now add person_ID to the dict of info printed as the outer dictionary key logging seems to have a problem.
…lysis file now collects all relevant info and prints them
…rected analysis file such as for small number of cases where the DALYs are not explicitly resolved the average DALYs are still computed correctly [skip ci]
Fix wrong dispatch identifier name in if statement Co-authored-by: Asif Tamuri <[email protected]>
…nning the same day
Thanks @tamuri, I have now included a sim-wide counter of events being ran that is appended as a unique identifier to the event name when logged (this doesn't apply to birth events, which I think we can safely assume only occur once per individual!) I have additionally included a similar counter - which in this case is however reset for each event - which tracks the instance of consumable requests within that HSI, ensuring that if multiple consumable calls occur within the same HSI_Event these can be logged separately. |
Looks good, though better to put the identifier as a new, separate, column in the row, which would allow the use of the event name for any purpose. |
| output = parse_log_file(sim.log_filepath, level=logging.DEBUG) | ||
| output_chains = parse_log_file(sim.log_filepath, level=logging.INFO) |
tamuri
left a comment
tamuri
left a comment
There was a problem hiding this comment.
I think this is good to merge!
|
Some checks failing |
src/scripts/track_individual_histories/analysis_extract_data.py
Outdated
Show resolved
Hide resolved
…github.com/UCL/TLOmodel into molaro/harvest-training-data-including-mni
This PR updates previous PR draft #1468
Now includes changes in the mother_and_newborn_info dataframe.