Use tidy version of coords (xrobin/pROC#54) #19
Merged
Conversation
This file contains 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.
An upcoming version of pROC (1.16) will feature backward incompatible changes in the coords function. In order to adhere to the principles of tidy datasets, the output will be transposed, and a data.frame returned instead of a matrix.
This PR sets the 'transpose' argument to 'coords' explicitly to ensure proper operation with current (1.15) and future versions of pROC.
I couldn't find any usage of the results, it seems they are only returned invisibly and not used anywhere in the package. However please note that they are now in a data.frame, and in transposed form. Scripts that would source this function outside of the package may have to be adapted too.