Data Science. TileDB. Open Source. Quant Research. R. C++. Debian. Linux. Adjunct Clinical Professor, University of Illinois. Lots of coffee. And some running.
The #Rcpp website has been refreshed, but still has quick intros, pointers to the ten vignettes, the gallery, 2500+ #Rstats packages using #Rcpp, and the book.
At rcpp.org (and yes, I should order a https cert)
Thanks all: I am (of course) aware of `ymd()`, the point of the tweet was that `anydate()` avoids all this automagically.
Plus, as @shabbychef reminded us, base #Rstats was there first (for this value) as `as.Date("2022-03-21") + 7` also works. Peace out.
I also use it but it a) supports fewer formats that anydate(), b) does not deal with as many input types and c) still insists on the re-repeating for 1e5s time what "origin" is (as if there ever was a doubt) so anydate() wins.
Apart from that it's great and zero-dependency.
> lubridate::dmy("2022-03-21") + lubridate::days(7)
[1] NA
Warning message:
All formats failed to parse. No formats found.
>
> anytime::anydate("2022-03-21") + 7
[1] "2022-03-28"
>
Always happy to help another #rstats user 😉
𝚍𝚖𝚢("𝟸𝟶𝟸𝟸-𝟶𝟹-𝟸𝟷") + 𝚍𝚊𝚢𝚜(𝟽)
That's right, for folks planning to submit your talk for consideration at 𝚛𝚜𝚝𝚞𝚍𝚒𝚘::𝚌𝚘𝚗𝚏(𝟸𝟶𝟸𝟸), we’re extending the deadline to March 28.
#rstudioconf#rstudioconf2022
If you want to learn about #Rcpp for C++ and #Rstats integration, I will be giving a one-hour introduction on March 25 thanks to a kind invitation by @NISS_DataSci via Kevin Lee. Registration should be opening soon, more details at the link below.
niss.org/events/rcpp-r-and-c…
It's been a while since I looked at it but I am fairly certain that `caret` and/or `mlr3` already cover it for #rstats.
It is a not uncommon task. Here is a tweet from just yesterday doing it for #rspatial data too:
New version of #rstats#rspatial package CAST allows visualizing whether training data for #MachineLearning have representative coverage of the prediction area and whether CV folds are appropriately chosen. Tutorial: hannameyer.github.io/CAST/ar…
@MLdwig @edzerpebesma @carles_milagarc
Hey, look, round number at CRAN!
A big, big thank you to the CRAN maintainers who are volunteers putting together an unparallel repository with unmatched quality guarantees, year in and out. Very much appreciated!
(Even if #RStats package authors like myself grumble at times.)
#rstats package tinytest now used to unit-test 200+ packages on CRAN! Thanks to all users for your trust in the package, and for all your valuable suggestions!
M-x R
M-x rename-buffer *R:projA*
and repeat for several buffers to give multiple (long-running) R sessions within Emacs. Which of course runs in daemon mode so that you can access it at the workstation or remotely ssh'ed in _accessing the same R sessions_.
#rstats#emacs
S, of course.
Which dates back to May 5, 1976, at Bell Labs and what followed. You may find the excellent article on "S, #RStats, and Data Science" by John Chambers in the ACM HOPL issue interesting if all this new to you:
doi.org/10.1145/3386334
It's a NOTE.
Not a WARNING or ERROR. There a lots of packages with larger installed footprints.
So you can proceed. But you can consider it as hint to maybe reduce same sample data or documentation.
With daughter #1 in town for her first big grad school conference (hello to the APS meeting at McCormick Place) I fired up a family favourite recipe @bittman's HTCE: crispy pork with orange and black beans.
The quote below is from the @duckdb documentation, but holds in general: don't use `insert` for bulk operations.
Rather look at the _specific_ documentation for _your_ SQL backend and see what it recommends for bulk.
Or else just be very patient.