-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of Tableregressionmodel
#194
Conversation
Codecov Report
@@ Coverage Diff @@
## master #194 +/- ##
==========================================
+ Coverage 86.25% 86.32% +0.06%
==========================================
Files 29 30 +1
Lines 12560 12562 +2
==========================================
+ Hits 10834 10844 +10
+ Misses 1726 1718 -8
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
This is fantastic, thank you so much for getting the hard work done!
julia> modelmatrix(fitBM)
ERROR: type PhyloNetworkLinearModel has no field pp A bigger issue that I noticed after checking the documentation build is that the coefficient table doesn't have the good formula terms. Example from julia> fitBM = phylolm(@formula(trait ~ shift_1 + shift_8), dfr, net; reml=false) # actual fit I get this table:
instead of this expected table:
I will need to look into GLM more to see if they have a work around the issue. |
Coefficient names are now correct in the coefficient table & summary, and methods are added for |
useful link: how JuliaStats/GLM.jl#339 got rid of |
I think it looks good. I only see some deprecation notice or some warning somewhere that we may try to add. But these changes will go v0.16.0 (increase from v0.15) anyway, because of breaking changes from a previous PR. @pbastide : please "squash & merge" if you're happy with this. |
…rks.jl into tableregressionmodel
Good catch for the I added deprecation notices as in JuliaStats/GLM.jl#339 as the previous documentation referred to If tests still pass and you are ok with this, I think it's ready for a "squash and merge". |
See issue #185.
I added a
formula
field to thePhyloNetworkLinearModel
as suggested, and changed functions accordingly.I also changed the field
model
toevomodel
for the evolutionary model, to avoid any confusion between objects.This is just a first attempt, I see at least a few TODOs:
object.mm.m
for the model matrix. We might need some dedicated functions to access what we really need, with functions such asformula
,modelmatrix
,modelframe
, ...