I went to download
yesterday and found the following page listed below. This is discouraging. What is the situation with this? How should I interact with DataRobot from an R script?
I would also like to complain that when I copied the link into this post, the editor removed the link for being invalid HTML and refused to post it. And then when I modified the link to not be recognized for this treatment it rejected my post because it felt it was "posting the same thing within an hour". Neither of these behaviours are helpful.
Package ‘datarobot’ was removed from the CRAN repository.
Formerly available versions can be obtained from the archive.
Archived on 2022-05-01 as check issues were not corrected in time.
A summary of the most recent check results can be obtained from the check results archive.
Please use the canonical form https://CRAN.R-project.org/package=datarobot to link to this page.
Solved! Go to Solution.
I was having a look at this myself, the R section of Get started with the API recommends just installing DataRobot package through Rtools with:
However I ran into an issue with the latest version of R 4.20
Not sure if this is related? The R docs suggest that R 4.20 should be alright.
@IraWatt Thanks for the response.
you have to have a copy of datarobot to install. And the cran site
says that the datarobot package has been archived as of a few days ago because it did not satisfy their requirements for a valid package.
So, where should one get this package?
I don't believe that the version of R is important here, as the problem is with the non existence of the cran datarobot package, and not compatibility with it.
The post by @IraWatt did not solve the problem at all. The issue is that cran has indicated that the datarobot package is now archived because it is not being maintained. One can download the archived package. But, this disturbs me. Is that what datarobot (corp) is suggesting - to use a package that is no longer maintained?
I am looking for ruling on this, or a link to a package that is maintained.
Sorry, I'm no expert on R packages but it does look like its being maintained, since this post was made the package has been updated on 2022-05-06 from V 2.18.1 to V 2.18.2. Noticeably V 2.18.2 solved my earlier issue with R 4.2.
V 2.18.2 also seems to have solved a lot of issues from V 2.18.1 looking at the package checks:
Perhaps that 2.18.1 was archived because of all its issues @Bruce ?
The exact same link got an archived statement at the time that I posted, I copied that statement on the original post - this was the only reason that I posted, of course.
It looks like someone fixed the problem in the last few days.