-
Notifications
You must be signed in to change notification settings - Fork 4
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
Which functions to export? #7
Comments
I thought you might object to that move 8) I personally found the exercise of documenting and commenting on these auxiliary functions, and using them interactively (which is aided by exporting), to be educational, which is a primary goal of I guess one issue could be that the help index has more entries and looks more intimidating. But we could use I really liked the parallelism you set up between creating the diagonal blocks of the relative covariance factor and the sections of the random effects design matrix. Both of these are created from a (1) grouping factor for each term and a (2) dense design matrix for each term. I personally think that exposing this underlying simplicity (by exporting these functions) would have value. I guess my argument just comes down to the fact that I found it enlightening to work with those functions interactively. |
Whoops...I mean four help files, including plsform.Rd |
I'm okay with having the functions documented in a single .Rd file. I just didn't want to end up with a whole raft of functions that could cause confusion about what were the primary functions and what were the secondary ones, Now that you mention the parallel approaches of creating a horizontal slice of Zt and creating a diagonal block of Lambdat I wonder if those should be collapsed into a single function. |
@stevencarlislewalker I notice that you have exported functions like
Zsection
. It wasn't my intention that those utilities would get exported. I wrote them a short functions so that it would be follow the logic in the creation of the representation.The thing that I would like to avoid with
lme4pureR
is having it morph into a large, essentially unintelligible code base likelme4
.The text was updated successfully, but these errors were encountered: