-
Notifications
You must be signed in to change notification settings - Fork 2
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
testting summary stats #6
Comments
Comment by richfitz from Wednesday Dec 11, 2013 at 08:29 GMT Right, following on from what happened in #64, can I suggest that we take the same approach as what we did with #57 and do some redundant implementation? That way we won't rely on specific numbers. I'll update the numbers here for now, but this won't be a big deal to get right. |
Hi @richfitz and @mwpennell just a dumb question: What do the abbreviations of the summary statistics stand for, as returned by function arbutus? |
Not a dumb question, this is the same problem as #17 -- be nice to have this info somewhere easy to find |
Yes, the way the help file of the function is written now doesn't facilitate this. Maybe having a "Value" section in the help explaining this would be nice indeed. Thanks! |
Issue by mwpennell from Friday Sep 27, 2013 at 02:19 GMT
Originally opened as traitecoevo/modeladequacy#15
I am not sure of the best way to evaluate the summary statistic fxn. Currently just using expected values on the geospiza dataset. This will only help if I change things as the calculations are based on current code. However, difficult to test independently because involves some complicated fxns like lm and ks.test. not sure best way to do this.
The text was updated successfully, but these errors were encountered: