#cran — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cran, aggregated by home.social.
-
For segfault lovers #CRAN Release of Rtinycc v0.1.8 For 'C' Scripting in #RStats Binding to libctcc and a declarative C FFI framework including thread safe R callbacks in C Code The package remove the R2C code transformation work to a coming downstream work github.com/sounkou-bioi...
-
📮You've got mail! 💌
We are thrilled to invite you to "Where do R packages live?" a discussion with folks from the #R foundation, #CRAN #Bioconductor #R-universe and @Posit
Let's learn from our panel about the ins-and-outs of where you might want to create a home for your R software 📦
Register today!
📆 Wed 20 May 2026
⏰ 5:00 PM AEST | 7:00 AM UTC
🔗 statsoc.org.au/event-6653060Looking forward to nerdy chats with @visnut Stevie P. @jeroenooms and Valerie B.
-
https://www.europesays.com/africa/161307/ Starlink fires back after Namibia rejects licence bid #CommunicationsRegulatoryAuthorityOfNamibia #cran #ElonMusk #Icasa #Namibia #spacex #Starlink #StarlinkNamibia
-
robscale 0.5.3 is now on CRAN: A major update since the last public release (0.2.1).
New: 11 robust estimators with confidence intervals, plus a variance-weighted ensemble combining seven scale statistics via bootstrap. Newton–Raphson replaces scoring iteration (2–4 steps vs 6–8), a fused AVX2 kernel does NR accumulation in one data pass, and all input validation runs in C++ with zero R-side allocation.
Speedups vs existing implementations:
Small samples (n ≤ 20):
• robScale/robLoc: 4–5× vs revss 3.1.0
• Qn: 6× vs robustbase
• MAD: 21–26× vs stats::mad
• IQR: 37× vs stats::IQRMid-to-large samples (n ≥ 1000):
• robScale: 2–4× vs revss
• Sn: 7–9× vs robustbase
• MAD: 5–8× vs stats::mad
• IQR: 5–7× vs stats::IQR
• GMD: 2–8× vs GiniDistancehttps://cran.r-project.org/package=robscale
https://github.com/davdittrich/robscale#RStats #Statistics #RobustStatistics #CRAN #DataScience #OpenSource
-
My #RStats package for forensic authorship analysis, 'idiolect', now has an associated paper published in the Journal of Open Source Software: https://doi.org/10.21105/joss.07575. New release of idiolect, 1.2.0, also available from #CRAN.
#forensic #linguisticshttp://andreanini.com/2026/03/15/idiolect-an-r-package-for-forensic-authorship-analysis/
-
Sometimes (often) one ends up needing to run older versions of R using older versions of packages. Evercran might be just the tool to help with that: https://github.com/r-hub/evercran#readme #RStats #docker #Cran #Rcheology
-
We Made It! 🎉
25 days. Complete modern R package development workflow. From usethis automation to CRAN submission. You have everything you need!
Your Next Steps:
✨ Apply these tools to your packages
📚 Bookmark for reference
🤝 Share knowledge with community
🚀 Build amazing R packagesThank you for following #RPackageAdvent2025! Now go make the R ecosystem better! 🎄📦
Keep Learning: https://r-pkgs.org | https://usethis.r-lib.org -
Thankfully temporary but I must have caught the CRAN website on a config change or something...back now but for the record I might need blood pressure medication if I see this again 😅
-
Sometimes (often) one ends up needing to run older versions of R using older versions of packages. Evercran might be just the tool to help with that: https://github.com/r-hub/evercran#readme #RStats #docker #Cran #Rcheology
-
Dear R developers and CRAN maintainers, I wonder if you can kindly help me understand how I should deal with the import of some packages and package functions. Despite reading "R Packages" (eg <https://r-pkgs.org/dependencies-mindset-background.html>) and "Writing R Extensions" (eg <https://cran.r-project.org/doc/manuals/R-exts.html#Package-Dependencies>), I'm still unsure how to deal with the following situation.
Suppose you have a package with the following requirements:
1. *One* function in your package, say "funA" requires a whole package, say PKGA. *However*, the function only uses PKGA in a separate (parallel::makeCluster) process. This function is fundamental to your package, in the sense that the user will surely use it at least once in their workflow.
2. Another function in your package, say "funB", requires two functions "aux1" and "aux2" from another package, say PKGB. The user might use this function, or maybe not. In your code (no parallel invocation), the functions are called with PKGB::aux1 etc.
3. The two functions "aux1" and "aux2" from PKGB are also available in PKGA. You'd like to be sure that the user can choose freely which ones they want in their workflow, alongside your package. In other words, no masking should take place a priori.
Given these conditions, what should NAMESPACE and DESCRIPTION contain? With Roxygen, where should I use @ import and @ importFrom? and what about usethis::use_import()?
Thank you very much for any tips or extra references to read!
Edit: for the moment, my solution has been to include PKGA, PKGB, and parallel in the Imports field of the DESCRIPTION file, but not to have these three packages in the NAMESPACE file as Import(). This seems to achieve what i want, but I'm not sure it's the "proper" solution.
-
Dependencies and reverse dependencies: Python vs. R: Julie Tibshirani reflects on how the #R ecosystem uniquely manages dependencies through reverse dependency checks on #CRAN. R’s approach comes at a cost to developers, but also fosters a culture of empathy and responsibility among package...
https://spatialists.ch/posts/2025/09/26-dependencies-and-reverse-dependencies-python-vs-r/ #GIS #GISchat #geospatial #SwissGIS -
#Macron affirme que l’ #Otan doit « #monter d’un #cran » en cas de « #nouvelles #provocations #russes » mais #sans #abattre d’ #avion
-
https://www.europesays.com/fr/348127/ Paroles de Girondins : « J’attends des victoires ou un changement d’entraîneur » #attends #Bordeaux #changement #chez #cran #entraineur #football #FR #France #Girondins #grogne #Monté #paroles #Sports #Supporters #victoires
-
tandis que le CRAN organise la cohérence entre les différentes versions de ses packages, ce travail d'alignement fait malheureusement défaut dans Pypi, raison pour laquelle Bruno Rodrigues plaide pour un meilleur contrôle des packages dans PyPi sous l'aspect de leur interopérabilité avec les autres packages qu'il contient https://brodrigues.co/posts/2025-08-22-pypan.html #Pypi #CRAN #DependencyHell
-
#RandomWaker has been updated to stable 1.0.0 and out to #CRAN Post: www.spsanderson.com/steveondata/...
-
#RandomWalker is updated and out to #CRAN look for a blog post tomorrow as I’ve had it ready for a little bit now #rstats #r #random
-
Following #rstats packages were maintained and are back on #CRAN now thanks to Andrej Spiess
- #dpcR, 2025-06-18, Digital PCR Analysis <10.32614/CRAN.package.dpcR>
- #MBmca, 2025-06-11, Nucleic Acid Melting Curve Analysis (https://journal.r-project.org/articles/RJ-2013-024/)
- #qpcR, 2025-06-10, Modelling and Analysis of Real-Time PCR Data <doi10.1093/bioinformatics/btn227>
- #PCRedux, 2025-06-13, Quantitative #PCR (#qPCR) Data Mining and Machine Learning Toolkit as Described in <doi:10.21105/Joss.04407> -
Sometimes (often) one ends up needing to run older versions of R using older versions of packages. Evercran might be just the tool to help with that: https://github.com/r-hub/evercran#readme #RStats #docker #Cran #Rcheology
-
chromConverter 0.7.5 is finally available on CRAN! Major changes since v0.2.1 include support for 10+ new file formats (Shimadzu LCD/QGD, Agilent D, Varian SMS, Allotrope ASM, ANDI MS/CHROM, mzML), parallel processing, and improved metadata extraction.
https://cran.r-project.org/web/packages/chromConverter/index.html
#rstats #CRAN #chromatography #opendata -
Sometimes (often) one ends up needing to run older versions of R using older versions of packages. Evercran might be just the tool to help with that: https://github.com/r-hub/evercran#readme #RStats #docker #Cran #Rcheology
-
Last week, I updated #adegenet on #CRAN. This is an important update as it fixes a memory overflow problem for SNP data that has existed since 2016.
If you use #PopGen packages that import adegenet (e.g. #poppr, #vcfR, or #dartR), then you should update.
-
Last week, I updated #adegenet on #CRAN. This is an important update as it fixes a memory overflow problem for SNP data that has existed since 2016.
If you use #PopGen packages that import adegenet (e.g. #poppr, #vcfR, or #dartR), then you should update.
-
Last week, I updated #adegenet on #CRAN. This is an important update as it fixes a memory overflow problem for SNP data that has existed since 2016.
If you use #PopGen packages that import adegenet (e.g. #poppr, #vcfR, or #dartR), then you should update.
-
Last week, I updated #adegenet on #CRAN. This is an important update as it fixes a memory overflow problem for SNP data that has existed since 2016.
If you use #PopGen packages that import adegenet (e.g. #poppr, #vcfR, or #dartR), then you should update.
-
Last week, I updated #adegenet on #CRAN. This is an important update as it fixes a memory overflow problem for SNP data that has existed since 2016.
If you use #PopGen packages that import adegenet (e.g. #poppr, #vcfR, or #dartR), then you should update.
-
Une #femme avec du #cran et des #convictions
Avec deux ovaires. Respect.En 150 ans, jamais personne n’avait quitté la #Royal #Society , l’illustre #sociéte #savante #britannique . #Dorothy #Bishop l’a fait, pour dénoncer la présence, dans cette docte assemblée, du #milliardaire #ElonMusk . Entretien exclusif.
#womeninstem #femmesenscience
#women #stem #femmes #sciences -
{zstdlite} news - package was accepted by CRAN 2 days ago, and has now been removed from CRAN by BDR for pretty weak policy "violations".
It feels like something that could have been emailed to me for discussion, instead of straightout rejection-after-initial-acceptance.
-
@hsorlie @JorisMeys @wviechtb To find the versions of packages that worked at a point in time in #CRAN you can use the newly released #rang https://cran.r-project.org/package=rang It might help to find the exact dependencies to make #RMediation work.
-
Sources for using OpenBlas multi-threading numerical libraries in CRAN R:
[1] https://csantill.github.io/RPerformanceWBLAS/ (including Benchmarks and HowTo for Linux)
[2] http://brettklamer.com/diversions/statistical/faster-blas-in-r/
[3] https://www.r-bloggers.com/why-is-r-slow-some-explanations-and-mklopenblas-setup-to-try-to-fix-this/
[4] https://github.com/xianyi/OpenBLAS (binary packages for Windows)
#rstats #cran #multicore #multithreading #parallelization #linux #windows #OpenBlas #BLAS #LAPACK
-
@rstats I would like to ask you about your experience with multi-threading and multi-core processors in R:
What is the current state of official CRAN R in using multi-threaded libraries to fully utilize multi-core processors? Were there any recent developments (on Linux and Windows)?
Now in 2020, how is the performance of CRAN R compared to Microsoft/Revolution R?#rstats #cran #multicore #multithreading #parallelization #linux #windows
-
Last December, the #rstats package #bcp was archived. 🙄
https://cran.r-project.org/package=bcp
As my package 📁 #PCRedux 🧬 depends on it, it had a similar fate (like some others). I vainly hoped that its maintainer would bring it back to #CRAN :rstats:. My plan is in the coming months to incorporate relevant code from bpc into my package or remove the dependent function within my package. Since it is published at #JOSS [1], this is important for me.
Let's see when this works out 🤞 -
Recently I used https://r-pkg.org/ (
#METACRAN: Search and browse all #CRAN/#R packages). This was a good thing to do, since I discovered R packages related to #qPCR that I haven't heard of before. Since several authors and I are writing a review about #dPCR, qPCR and #meltingcurveanalysis this is good not to forget anybody. -
@anders Yes, I used #RQDA in some smaller projects. It was very basic, but functional. RQDA is not maintained anymore and has been removed from #Rstats #CRAN.
#QualCoder is inspired by RQDA, but - as far as I know - has no R integration.
#QCoder is a fairly new R package for "lightweight" qualitative analysis. It uses #Shiny for the UI.
-
@feld good question!
i think we automatically package all #haskell packages from #hackage and some #stackage (18k) and all #Rpackages from #CRAN (27k)
the manually packaged python and perl libs are available for multiple versions. the supported ones are visible, older still work
check out the package sets on the left https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=*
that blows up the number! we don't have ancient, unmaintained packages found in debian, but modern ones like in #AUR
-
Thread:
🚨Software Publication Alert🚨
This one is for you, text-analysis folks:I am very happy to share the publication of my text annotation R-package "handcodeR" 🥳, which is now available on CRAN. 🧵1/7
CRAN.R-project.org/package=handcoge=handcodeR