Skip to content
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

REEMForest() 'Error in solve.default(S1) : Lapack routine dgesv: system is exactly singular:' #3

Open
JustGettinStarted opened this issue Feb 14, 2021 · 3 comments

Comments

@JustGettinStarted
Copy link

JustGettinStarted commented Feb 14, 2021

REEMForest() consistently produces an error with with several different datasets. Seems to be coming from solve() in moy() functions. This appears to be common problem. See https://stackoverflow.com/questions/66188123/implementing-longitudinal-random-forest-with-longiturf-package-in-r and answer 1 to https://stats.stackexchange.com/questions/103730/how-can-i-include-random-effects-or-repeated-measures-into-a-randomforest

@JustGettinStarted JustGettinStarted changed the title Error in solve.default(S1) : Lapack routine dgesv: system is exactly singular: U[12,12] = 0 REEMForest() 'Error in solve.default(S1) : Lapack routine dgesv: system is exactly singular:' Apr 27, 2021
@Chhr1s
Copy link

Chhr1s commented Aug 20, 2021

Hi @JustGettinStarted,

I've been working with LongituRF for a project over the past week and had the same problem as you.

I modified the function and had it print in-between steps. It seems (for me) the issue was with the output from calling the internal function LongituRF:::logV().

I looked at the data from the simulated case, as that was working just fine for me. I tried centering and scaling the continuous predictors and everything worked for me! Try applying that.

If you're trying to be very rigorous, care should be taken to prevent leakage of information between training and test sets during the scaling process.

More helpful warning messages would be a big improvement here.

@Chhr1s
Copy link

Chhr1s commented Aug 31, 2021

I'm going to come back to this and say I got REEMforest() to work in really specific cases, but I've run into this many more (if not most) times as I keep working with it. Same error @JustGettinStarted described above.

MERF() appears to have fewer problems.

@isaactpetersen
Copy link

I run into this issue every time as well, including with MERF().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants