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
Closes#4455
hi @jangorecki tagging you for a review since this is a fix for #4455 which you labeled.
Turns out the fix was really easy, just had to delete two lines of code.
I had to update the expected values for two existing tests, which I suspect were created based on the empirical output of melt, rather than the theoretically expected values.
In the linked issue the example code which illustrates the problem is:
This is problematic for downstream applications such as tdhock/nc#11 which need variable to be the corresponding index of the measure.vars list elements. In the example above we need variable=2 in both cases so that we know the data come from child2.
hi again @mattdowle@arunsrinivasan please consider merging this simple fix for melt for the next release, thanks! (sorry if I'm being annoying, I know there are a lot of other PRs to examine, I just wanted to make clear that my suggestion for prioritizing my melt-related PRs should be first this one, then #4720, then #4731, then #4737)
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
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.
Closes #4455
hi @jangorecki tagging you for a review since this is a fix for #4455 which you labeled.
Turns out the fix was really easy, just had to delete two lines of code.
I had to update the expected values for two existing tests, which I suspect were created based on the empirical output of melt, rather than the theoretically expected values.
In the linked issue the example code which illustrates the problem is:
on current master we get results that are inconsistent (na.rm=TRUE gives variable=1, but na.rm=FALSE gives variable=2).
This is problematic for downstream applications such as tdhock/nc#11 which need variable to be the corresponding index of the measure.vars list elements. In the example above we need variable=2 in both cases so that we know the data come from child2.
After applying this PR I get
All tests pass on my computer (R-4.0.2, Ubuntu 18.04), please code review.