-
Notifications
You must be signed in to change notification settings - Fork 11
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
mstop = 1 should be possible for non-cyclical fitting #22
Comments
Why do we force update all boosting parameters in the first iteration? Is this really necessary? I know that we need to build up all mboost objects but couldn't we (and don't we have to) just use the best update already in this first step? (i.e. alway refit already the first step if necessary???) |
In the current implementation we have to initialize all models before the noncyclical model can run. But in general you are completely right that it should work like you suggested. I'm not sure how easy it would be to change it like that. This is something that I would like to solve together with #24. |
@hofnerb is there a way to create a mboost object with 0 iterations? So basically a intercept only model, with mstop = 0 |
No, this is currently not possible. We should have a look at mboost to fix this. Shouldn't we? |
That's imo the smartest way to fix this, I'll open an issue there |
Acutally this might be pretty easy. I just have a look at it. We simply might skip this line. Just need to make sure that no unwanted side effects are induced. |
Should be working now. Both, subsetting ( Please go ahead (and let me now if you spot an open issue regarding |
Awesome! Thanks a lot |
@ja-thomas I hope you always use I think we should also allow |
I modified |
So I changed the behavior of gamboostLSS to work with It just seems that the focus on location parameter is even stronger. For the old version mstop = 90/10 on the cars dataset for the new version after 700 iterations 678/22 while for mstop=600 it is still 600/0. There shouldn't be such a huge difference I think. My current theory is that the initialization is wrong (thats why I opened #69 in mboost. |
Did you also have a look at coefficients and/or coefficient paths? It could be that by forcing mstop = 1, we need the next iterations to revert this effect, which wouldn't be necessary if it wasn't included in the first place. |
@ja-thomas Please also check that mstop = 0 etc. works, also subsetting and increasing afterwards (see also #33). Perhaps you can recycle (some of) the code from boost-R/mboost:regtest-gamboost.R |
Hm, so you actually mean that now we are doing the right thing...
|
which means that you think that with |
Ok there is definitely some more testing required. In principle everything seems to work, it is just highly depending on the dataset. Let's see what is going to happen in some simulated scenarios. |
@ja-thomas This should be working in devel, now? |
Seems like it. Tests are included in tests/regtest-noncyclic_fitting.R |
currently gives the errror
and if one fits a larger model and reduces it to 1, one gets
Does this really make sense for non-cyclical models?
The text was updated successfully, but these errors were encountered: