med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

425
active users

#cran

1 post1 participant0 posts today
Jakub Nowosad<p>DevXY now provides CRAN R package binaries for Linux arm64 and Alpine Linux — making installs faster and workflows smoother for R users.</p><p>Blog post by Patrick Schratz: <a href="https://www.devxy.io/blog/cran-r-package-binaries-launch/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">devxy.io/blog/cran-r-package-b</span><span class="invisible">inaries-launch/</span></a></p><p><a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AlpineLinux</span></a></p>
ethanbass<p>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.<br><a href="https://cran.r-project.org/web/packages/chromConverter/index.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cran.r-project.org/web/package</span><span class="invisible">s/chromConverter/index.html</span></a><br> <a href="https://ecoevo.social/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://ecoevo.social/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> <a href="https://ecoevo.social/tags/chromatography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>chromatography</span></a> <a href="https://ecoevo.social/tags/opendata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opendata</span></a></p>
Lluís Revilla<p>Some <a href="https://fosstodon.org/tags/R" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>R</span></a> <a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> about the packages on the repositories: <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> has 722 packages that use Bioconductor (3%), <a href="https://fosstodon.org/tags/Bioconductor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bioconductor</span></a> has 2802 packages that use CRAN's packages (77%). </p><p>1.3% CRAN and 0.6% Bioconductor respectively use package outside these two repositories. But 91% and 93% use packages on their respective repos. 8% and 3% do not have any dependency on external packages (but could depend on system dependencies).</p>
Ralf Stubner<p>Today version 0.3.2 of the swephR package for R made it unto CRAN. Main reason for the upgrade was that CRAN had found a new WARNING by also inspecting the intermediate static library file. Instead of patching the upstream sources, I opted for deleting the library after building the the symbolic library for the package. It does not help anybody when code is inspected that is not actually used.</p><p>Two things were really nice:<br>* The warning message displayed at <a href="https://cran.r-project.org/package=swephR" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cran.r-project.org/package=swe</span><span class="invisible">phR</span></a> disappeared even before all test machines had build the new version. Probably once the first tests of previously failing tests came in.<br>* This package suggests a larger data package, that is only available on r-universe. Therefore, there had always been one NOTE, which meant manual inspection when submitting. Now this NOTE has been demoted to INFO, which goes through automatically, speeding up the process and leaving less work for the CRAN maintainers.</p><p><a href="https://digitalcourage.social/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://digitalcourage.social/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a></p>
Lluís Revilla<p>FYI: 14% of <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> links require knowing alias present on the libraries to resolve them. 80% of links to duplicated targets are present on the package. Which results on just 3% of links in packages being ambiguos (I expected more).</p><p>In related news, just 5 packages have different documentation for unix and windows! One of them breaks my <a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> link resolver...</p>
Data Science<p>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: <a href="https://github.com/r-hub/evercran#readme" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/r-hub/evercran#read</span><span class="invisible">me</span></a> <a href="https://genomic.social/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RStats</span></a> <a href="https://genomic.social/tags/docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>docker</span></a> <a href="https://genomic.social/tags/Cran" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cran</span></a> <a href="https://genomic.social/tags/Rcheology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Rcheology</span></a></p>
Zhian N. Kamvar<p>Last week, I updated <a href="https://hachyderm.io/tags/adegenet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>adegenet</span></a> on <a href="https://hachyderm.io/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a>. This is an important update as it fixes a memory overflow problem for SNP data that has existed since 2016. </p><p>If you use <a href="https://hachyderm.io/tags/PopGen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PopGen</span></a> packages that import adegenet (e.g. <a href="https://hachyderm.io/tags/poppr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>poppr</span></a>, <a href="https://hachyderm.io/tags/vcfR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vcfR</span></a>, or <a href="https://hachyderm.io/tags/dartR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dartR</span></a>), then you should update.</p><p><a href="https://cran.r-project.org/web/packages/adegenet/ChangeLog" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cran.r-project.org/web/package</span><span class="invisible">s/adegenet/ChangeLog</span></a></p><p><a href="https://hachyderm.io/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RStats</span></a></p>
Jakub Nowosad<p>👋 A regular reminder: CRAN Task View: Analysis of Spatial Data is always open for contributions!👋 </p><p>Let us know about great tools for working with spatial data in R!</p><p><a href="https://buff.ly/487HU6S" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">buff.ly/487HU6S</span><span class="invisible"></span></a></p><p><a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://fosstodon.org/tags/rspatial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rspatial</span></a> <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a></p>
coolbutuseless<p><a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> could halve their work on the "incoming" queue by doing the following:</p><p>"R CMD CHECK --as-cran" should fail for exported functions witthout examples - authors prompted to fix b4 submission</p><p>There. I've done it. </p><p>I've just saved CRAN XX hours a week of emailing people to "please add examples".</p><p>If someone has any inside clout with CRAN/R core please make this suggestion. </p><p>As they say "volunteer time is precious", and this trivial fix could save so much!</p><p><a href="https://fosstodon.org/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RStats</span></a> <a href="https://fosstodon.org/tags/NotHoldingMyBreath" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NotHoldingMyBreath</span></a></p>
Data Science<p>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: <a href="https://github.com/r-hub/evercran#readme" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/r-hub/evercran#read</span><span class="invisible">me</span></a> <a href="https://genomic.social/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RStats</span></a> <a href="https://genomic.social/tags/docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>docker</span></a> <a href="https://genomic.social/tags/Cran" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cran</span></a> <a href="https://genomic.social/tags/Rcheology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Rcheology</span></a></p>
Josiah<p>Folks who have contributed to <a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> core: </p><p>i've added a diff to my bug report, what happens next? This is a fairly critical fix for the :rstats: + :rust_ferris: story.</p><p>Hoping to get it merged into trunk before they publish 4.4.2 </p><p>any and all tips welcomed! </p><p><a href="https://bugs.r-project.org/show_bug.cgi?id=18806" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bugs.r-project.org/show_bug.cg</span><span class="invisible">i?id=18806</span></a></p><p><a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://fosstodon.org/tags/cran" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cran</span></a> <a href="https://fosstodon.org/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rust</span></a></p>
the notorious gzt<p>when did the tricksy hobbitses running R switch from Calloc to R_Calloc (etc)? only noticing now that they're deprecating the old way in 4.5.0 as I'm updating a bunch of old packages for another breaking update. <a href="https://hulvr.com/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://hulvr.com/tags/cran" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cran</span></a></p>
GBIF 🌱<p>R you ready for an <a href="https://ecoevo.social/tags/rgbif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rgbif</span></a> update? Version 3.8.1 📦 is on <a href="https://ecoevo.social/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> now!<br>👀 New features: <br>◼️ New function occ_download_sql() for downloading occurrence data using SQL queries<br>🐞 Bug fixes:<br>◼️occ_download_cached() bug fixed. </p><p>Learn more: 🔗 <a href="https://buff.ly/3ZPuI4F" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">buff.ly/3ZPuI4F</span><span class="invisible"></span></a></p>
coolbutuseless<p>Idea: Can we as package developers (as a group) decide on a standard file in which to store all historical communication with CRAN?</p><p>CRAN-correspondence.txt ?</p><p>I don't mean any sanitized high-level summary, I mean a record of every CRAN interaction about your package submission. Emails could be redacted to "[CRAN member]" to avoid any privacy concerns.</p><p>I'm sick of feeling like I'm navigating CRAN blind. The lack of open discussion makes it really difficult.</p><p><a href="https://fosstodon.org/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RStats</span></a> <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> <a href="https://fosstodon.org/tags/Whinge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Whinge</span></a></p>
Philipp Baumann<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@brodriguesco" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>brodriguesco</span></a></span> i'm really happy our package just made it to CRAN and will make <a href="https://fosstodon.org/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Nix</span></a> easily accessible to build and share fully reproducible <a href="https://fosstodon.org/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RStats</span></a> software environments and beyond. <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> <a href="https://fosstodon.org/tags/ROpenSci" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ROpenSci</span></a></p>
Jumping Rivers<p>Ever needed to compare different versions of R or Python packages? 🔍</p><p>With Diffify, you can easily see what's changed between versions of R packages on CRAN and Python packages on PyPI. Stay on top of package updates and manage your projects with ease. </p><p><a href="https://fosstodon.org/tags/R" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>R</span></a> <a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a> <a href="https://fosstodon.org/tags/Rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Rstats</span></a> <a href="https://fosstodon.org/tags/Diffify" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Diffify</span></a> <a href="https://fosstodon.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> <a href="https://fosstodon.org/tags/PyPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PyPI</span></a></p><p><a href="https://diffify.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">diffify.com/</span><span class="invisible"></span></a></p>
Achim Zeileis<p>New version 0.2.2 of :rstats: 📦 distributions3 on <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a>, together with <span class="h-card" translate="no"><a href="https://mastodon.social/@alexpghayes" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>alexpghayes</span></a></span> <br><a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a></p><p>- Object-oriented computations on (vectors of) probability distributions</p><p>- More model-based probabilistic forecasts</p><p>- simulate() from fitted likelihood models</p><p>- Support in <a href="https://fosstodon.org/tags/tibble" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tibble</span></a> in addition to data.frame</p><p>Documentation at:</p><p><a href="https://alexpghayes.github.io/distributions3/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">alexpghayes.github.io/distribu</span><span class="invisible">tions3/</span></a></p>
pglpm<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@schochastics" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>schochastics</span></a></span> From the stories I'm more and more frequently hearing (and I mostly tend to trust), it sounds like it's time for the people at <a href="https://c.im/tags/cran" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cran</span></a> to get their house in order?</p><p><a href="https://c.im/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a></p>
Lluís Revilla<p>The results of the <a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://fosstodon.org/tags/CRAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRAN</span></a> survey is available 😃 <a href="https://github.com/r-devel/cran-cookbook/wiki/CRAN-Cookbook-Survey-Results" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/r-devel/cran-cookbo</span><span class="invisible">ok/wiki/CRAN-Cookbook-Survey-Results</span></a></p><p>I thought more than 126 people would have answered. It seems that working on the R package development task view would be appreciated. But there are a lot of suggestions for the CRAN team too. </p><p>Many thanks <span class="h-card" translate="no"><a href="https://mastodon.cloud/@jasminedaly" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jasminedaly</span></a></span> and team for sharing it.</p>
dgkf<p>CRAN seems to be down… and although it’s a bit inconvenient, I’m also just amazed that this is the first time I’ve been impacted by CRAN downtime.</p><p>Maybe I’ve just been lucky so far, but upon reflection I’m pretty impressed it has a such a good uptime track record. </p><p><a href="https://fosstodon.org/tags/r" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>r</span></a> <a href="https://fosstodon.org/tags/rlang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rlang</span></a> <a href="https://fosstodon.org/tags/rstats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rstats</span></a> <a href="https://fosstodon.org/tags/cran" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cran</span></a></p>