Not normal floating (glm) #244
Closed
wkitlasten
started this conversation in
General
Replies: 2 comments
-
Hmm. Usually this happens with log pars when the upgrade is extreme (large residuals) and lots of singular components are being used. You can try smaller maxsing and or larger eigthresh- that will usually stabilize things. Can you send me your master dir so I can have a look? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Doh, I forgot to unweight my extreme obs ('less_') that I was using to drop bad reals in ies. Error makes sense now. Sorry. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm doing a quick glm run to try to get a "better" starting point before my ies run. 263 pars are listed under the following errors. What are the implications of this? Should I be worried?
Maybe something wrong with my jcb?
Parval1, parbnds, and derinc all seem legit and jcb.isnull().any().any()=False, but maybe I need to adjust those a little?
Maybe I need to set lambda bigger (smaller)? Maybe something more insidious in my builds?
Any other suggestions or insights appreciated.
Beta Was this translation helpful? Give feedback.
All reactions