Users of the current version of the lme4 package have reported several problems and, for some time, I have been unresponsive about such reports or I have made reference to the development version of the package. Let me emphasize that I am grateful for the reports and, indeed, have fixed several of these problems in the development version of the package. However, I have held off releasing the development version because of one small problem - it doesn't fit generalized linear mixed models correctly. I have had to go back and reformulate the model from scratch so that I can understand it and design the code. As anyone who has developed and maintained a large project can attest, the only way to build trustworthy code (and to maintain your sanity) is to modularize the code. It goes without saying that before you can decide how to modularize the code you must be able to decompose the steps in the computation. The development version is designed to handle linear mixed models, generalized linear mixed models, nonlinear mixed models and generalized nonlinear mixed models with nested or crossed or partially crossed random factors. It has taken me a long time to decide how all those pieces fit together. Only in the last couple of weeks have I have managed to convince myself that I know how it all fits together. The task of convincing others remains, and is decidedly non-trivial, but I feel that I can decompose the computational steps now. It will take a while to move from the equations in my lab notebook to released code and, during that process, I will probably need to reformulate the slots in the S4 classes. My method of getting to the final design of the data structures and algorithms is to keep doing it wrong 'til I do it right. So that others have easy access to the development version of the package I have moved the repository for the development version of the package to http://R-forge.R-project.org/packages/lme4 Martin and I had planned to do this move in a way that would preserve the history of the changes from the current repository but that is not easy to do because of the way that the Matrix and lme4 packages were merged then un-merged. Thus I have made a clean break and installed the development version (the one known as gappy-lmer) on R-forge. You can access it at the URL given above or as http://lme4.r-forge.r-project.org/, at the expense of one additional click. Starting tomorrow you should also be able to install the development version of the package with install.packages("lme4", repos = "http://r-forge.r-project.org") Please be aware that the class representations can change so when using the development version you should not count on being able to re-use a fitted model after installing a new version. You should retain the original data so you can refit the model if necessary.
lme4 is now on R-forge
6 messages · Douglas Bates, Dan Wright, Dieter Menne +2 more
5 days later
Hi Everyone, I was wanting to write my own cor structure for the nlme package to put into a gls. Does anybody have a good place to look for how to do this? I think I remember it being in the handouts from a course with Jose Pinheiro, but I lent them to doctoral student who graduated and it does seem to be in that section of their book. Thanks in advance Dan Daniel B. Wright Psychology Department University of Sussex BN1 9QH, UK danw at sussex.ac.uk http://www.sussex.ac.uk/Users/danw/
14 days later
Douglas Bates <bates at ...> writes:
Starting tomorrow you should also be able to install the development
version of the package with
install.packages("lme4", repos = "http://r-forge.r-project.org")
When I try this, I get:
install.packages("lme4", repos = "http://r-forge.r-project.org")
Warning: unable to access index for repository http://r-forge.r-project.org/bin/windows/contrib/2.6 Warning message: package ?lme4? is not available Dieter
"DM" == Dieter Menne <dieter.menne at menne-biomed.de>
on Fri, 30 Nov 2007 14:35:41 +0000 (UTC) writes:
DM> Douglas Bates <bates at ...> writes:
>> Starting tomorrow you should also be able to install the development
>> version of the package with
>>
>> install.packages("lme4", repos = "http://r-forge.r-project.org")
>>
DM> When I try this, I get:
>> install.packages("lme4", repos = "http://r-forge.r-project.org")
DM> Warning: unable to access index for repository
DM> http://r-forge.r-project.org/bin/windows/contrib/2.6
DM> Warning message:
DM> package ?lme4? is not available
I see a severe problem with R-forge at the moment :
The 2.6 bin/windows/ directory looks completely empty.
Martin
On Nov 30, 2007 11:26 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote:
"DM" == Dieter Menne <dieter.menne at menne-biomed.de>
on Fri, 30 Nov 2007 14:35:41 +0000 (UTC) writes:
DM> Douglas Bates <bates at ...> writes:
>> Starting tomorrow you should also be able to install the development
>> version of the package with
>>
>> install.packages("lme4", repos = "http://r-forge.r-project.org")
>>
DM> When I try this, I get:
>> install.packages("lme4", repos = "http://r-forge.r-project.org")
DM> Warning: unable to access index for repository
DM> http://r-forge.r-project.org/bin/windows/contrib/2.6
DM> Warning message:
DM> package 'lme4' is not available
I see a severe problem with R-forge at the moment :
The 2.6 bin/windows/ directory looks completely empty.
Martin
Also, the link labeled win32-latest.zip on the SCM page for the lme4 package on R-forge does not contain a Win32 binary package. Instead it is the build log. The source package, labelled src-latest.tar.gz, does appear to be intact. I will be updating the sources for the package this afternoon. I finally got generalized linear mixed models working in the development version. If the problem for Windows binary packages on R-forge is resolved (it does look as if they are being built - I think the problem is that the wrong file is being returned from the build process) soon I will just ask Windows users to wait for a day or two. If it is still a problem early next week I will create a Windows binary package using win-builder.r-project.org and make it available via http.
Hello Doug, We had troubles with disk space on R-Forge. Among others this caused the website to malfunction. It is possible that the windows binary build process had been affected too. However, everything should be OK by now except that the win binaries are not available yet. I try to trigger the windows build process from home, but this implies a remote desktop connection which is rather slow. Nevertheless, if I have no success with rdesktop tonight, tomorrow at 6 am CET, the packages will be built automatically. Best, Stefan
Douglas Bates wrote:
On Nov 30, 2007 11:26 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote:
"DM" == Dieter Menne <dieter.menne at menne-biomed.de>
on Fri, 30 Nov 2007 14:35:41 +0000 (UTC) writes:
DM> Douglas Bates <bates at ...> writes:
>> Starting tomorrow you should also be able to install the development
>> version of the package with
>>
>> install.packages("lme4", repos = "http://r-forge.r-project.org")
>>
DM> When I try this, I get:
>> install.packages("lme4", repos = "http://r-forge.r-project.org")
DM> Warning: unable to access index for repository
DM> http://r-forge.r-project.org/bin/windows/contrib/2.6
DM> Warning message:
DM> package 'lme4' is not available
I see a severe problem with R-forge at the moment :
The 2.6 bin/windows/ directory looks completely empty.
Martin
Also, the link labeled win32-latest.zip on the SCM page for the lme4 package on R-forge does not contain a Win32 binary package. Instead it is the build log. The source package, labelled src-latest.tar.gz, does appear to be intact. I will be updating the sources for the package this afternoon. I finally got generalized linear mixed models working in the development version. If the problem for Windows binary packages on R-forge is resolved (it does look as if they are being built - I think the problem is that the wrong file is being returned from the build process) soon I will just ask Windows users to wait for a day or two. If it is still a problem early next week I will create a Windows binary package using win-builder.r-project.org and make it available via http.