Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upissue #129: glmer bug (requires merge of PR in prediction repo) #138
Conversation
codecov-io
commented
Mar 6, 2020
Codecov Report
@@ Coverage Diff @@
## master #138 +/- ##
==========================================
- Coverage 77.96% 77.91% -0.05%
==========================================
Files 39 39
Lines 1207 1209 +2
==========================================
+ Hits 941 942 +1
- Misses 266 267 +1
Continue to review full report at Codecov.
|
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.
vincentarelbundock commentedMar 6, 2020
Please ensure the following before submitting a PR:
R CMD check
runs without error before submitting the PRIn combination with my concurrent PR at leeper/prediction this fixes Issue #129.
Here, I am simply adding another fallback option when variable classes cannot be extracted easily from
term(model)[['dataClasses']]
. I useterms(model.frame(model))
to get the info we need.