tag:blogger.com,1999:blog-4113082053753185517.post2559516412977873564..comments2023-07-02T13:50:28.495+02:00Comments on Samuel Bosch: Workaround "n.trees" is missing in R package gbm version 2.1.1Samuel Boschhttp://www.blogger.com/profile/00902576471871535529noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4113082053753185517.post-35798727399221950442017-04-18T11:25:11.469+02:002017-04-18T11:25:11.469+02:00I'm afraid maxlike is no longer actively suppo...I'm afraid maxlike is no longer actively supported.Samuel Boschhttps://www.blogger.com/profile/00902576471871535529noreply@blogger.comtag:blogger.com,1999:blog-4113082053753185517.post-17067879803467532017-03-31T09:11:12.896+02:002017-03-31T09:11:12.896+02:00Thanks.
I suggest add
else {
gbm::predict.gb...Thanks. <br />I suggest add <br />else {<br /> gbm::predict.gbm(object, newdata, n.trees, type, single.tree, ...)<br />}<br />outside the if clause so it will work in any situation.<br /><br />Besides, I noticed that <br />"X-CRAN-Comment: Orphaned on 2017-03-21 as long-standing errors were not<br /> corrected. NMU by CRAN team."<br />from the help page of gbm-package of the newest released version 2.1.3.<br />You mentioned above that "This issue will be fixed in the next version", so do you have any idea about the active maintainer of "gbm"? Or is there a community that I could know the current bugs? Thanks. Tiny Oceanhttps://www.blogger.com/profile/12708711607517175619noreply@blogger.comtag:blogger.com,1999:blog-4113082053753185517.post-5064803230813617922017-01-19T16:44:11.677+01:002017-01-19T16:44:11.677+01:00Worked for me too. Thanks a lot.Worked for me too. Thanks a lot.Tiago Fardilhahttps://www.blogger.com/profile/07343777963610953918noreply@blogger.comtag:blogger.com,1999:blog-4113082053753185517.post-68865615449928736792016-06-30T23:43:19.899+02:002016-06-30T23:43:19.899+02:00This worked for me, thank you! I was getting the e...This worked for me, thank you! I was getting the error when trying to plot a 3D two way interaction from a gbm model using visreg2d in the visreg package.Katiehttps://www.blogger.com/profile/07843553214250634750noreply@blogger.com