Km compactify rectify - #101
Conversation
…side this project.
… being redundant.
…es as to check if it works.
|
Closes #62. |
|
Okay, discussing with Ryan, we might need to roll back some of my changes, at least. |
|
The pull request is filled with random changes, which makes it hard to track down what had actually been changed within this pull request rather than outside of it. I may have overlooked something that should be updated/fixed, especially here with the clutter. |
|
The To try to prevent this from continuing to get out of hand, I'll try to do the minimal immediate edits from Ryan's feedback and file others in issues. |
Always introduce version-wise LOCF as "last observation of each observation carried forward (LOCF)" or something quite similar. Clarify time-wise LOCF in one place.
|
It noticed that by fixing the conflicts, the tests fail. Did I wrongly use the bottom part rather than the top part of the conflict? |
Merge branch 'main' of https://github.com/cmu-delphi/epiprocess into km-compactify_rectify # Conflicts: # R/archive.R # tests/testthat/test-methods-epi_archive.R
Merge branch 'km-compactify_rectify' of https://github.com/dajmcdon/epiprocess into km-compactify_rectify # Conflicts: # R/archive.R # tests/testthat/test-methods-epi_archive.R
|
I'm looking at |
- max(self$DT$time_value) -> max_time - merge updates to as_of test: both - test that doesn't mutate key - use custom test archive, not archive_cases_dv_subset
I rectified compactify by overhauling it.