home.social

#rstats — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rstats, aggregated by home.social.

  1. 👋 Meet Philippe Massicotte! 🇨🇦

    Research Assistant and maintainer of {rnaturalearth}, {rnaturalearthdata}, and {gitignore} for rOpenSci. The first two packages facilitate mapping by providing world vector maps and data. {gitignore} helps you to create useful .gitignore files for your project.

    Find Philippe at:
    🐘 @philmassicotte
    💻 github.com/PMassicotte
    🔗 linkedin.com/in/philippe-massicotte-725214260

  2. Rivers and lakes of Wisconsin. I see the broken lines...turns out it takes more effort than I anticipated to resolve. I can fix the entire river, but it breaks when I intersect.

    Would appreciate any suggestions.

    adventures, an tale

  3. Rivers and lakes of Wisconsin. I see the broken lines...turns out it takes more effort than I anticipated to resolve. I can fix the entire river, but it breaks when I intersect.

    Would appreciate any suggestions.

    #rayshader adventures, an #rstats tale

    #wisconsin #rivers #lakes #dataviz

  4. Rivers and lakes of Wisconsin. I see the broken lines...turns out it takes more effort than I anticipated to resolve. I can fix the entire river, but it breaks when I intersect.

    Would appreciate any suggestions.

    #rayshader adventures, an #rstats tale

    #wisconsin #rivers #lakes #dataviz

  5. Rivers and lakes of Wisconsin. I see the broken lines...turns out it takes more effort than I anticipated to resolve. I can fix the entire river, but it breaks when I intersect.

    Would appreciate any suggestions.

    #rayshader adventures, an #rstats tale

    #wisconsin #rivers #lakes #dataviz

  6. Rivers and lakes of Wisconsin. I see the broken lines...turns out it takes more effort than I anticipated to resolve. I can fix the entire river, but it breaks when I intersect.

    Would appreciate any suggestions.

    #rayshader adventures, an #rstats tale

    #wisconsin #rivers #lakes #dataviz

  7. We had the pleasure of hosting Edgar Riuz, who shared incredible insights on how to use the #mall package in #R.

    📺 Replay: youtu.be/jh2U5U-mJ_w

    A special thanks for R-Ladies #Abuja to the collaboration!

    #RStats #RStatsFr #LLM #NLP #RLadies

  8. We had the pleasure of hosting Edgar Riuz, who shared incredible insights on how to use the #mall package in #R.

    📺 Replay: youtu.be/jh2U5U-mJ_w

    A special thanks for R-Ladies #Abuja to the collaboration!

    #RStats #RStatsFr #LLM #NLP #RLadies

  9. We had the pleasure of hosting Edgar Riuz, who shared incredible insights on how to use the #mall package in #R.

    📺 Replay: youtu.be/jh2U5U-mJ_w

    A special thanks for R-Ladies #Abuja to the collaboration!

    #RStats #RStatsFr #LLM #NLP #RLadies

  10. We had the pleasure of hosting Edgar Riuz, who shared incredible insights on how to use the #mall package in #R.

    📺 Replay: youtu.be/jh2U5U-mJ_w

    A special thanks for R-Ladies #Abuja to the collaboration!

    #RStats #RStatsFr #LLM #NLP #RLadies

  11. We had the pleasure of hosting Edgar Riuz, who shared incredible insights on how to use the #mall package in #R.

    📺 Replay: youtu.be/jh2U5U-mJ_w

    A special thanks for R-Ladies #Abuja to the collaboration!

    #RStats #RStatsFr #LLM #NLP #RLadies

  12. The R Consortium R Submissions Working Group continues to help move regulatory submissions with R from concept to practical implementation.

    In Pilot 4, the group explored WebAssembly and Docker containers for packaging and running an R Shiny app for regulatory review.

    FDA feedback showed both approaches are technically feasible, highlighting practical needs around reproducibility, security, reviewer usability, and operational readiness.

    Read more: r-consortium.org/posts/beyond-

  13. The R Consortium R Submissions Working Group continues to help move regulatory submissions with R from concept to practical implementation.

    In Pilot 4, the group explored WebAssembly and Docker containers for packaging and running an R Shiny app for regulatory review.

    FDA feedback showed both approaches are technically feasible, highlighting practical needs around reproducibility, security, reviewer usability, and operational readiness.

    Read more: r-consortium.org/posts/beyond-

    #rstats #pharma

  14. The R Consortium R Submissions Working Group continues to help move regulatory submissions with R from concept to practical implementation.

    In Pilot 4, the group explored WebAssembly and Docker containers for packaging and running an R Shiny app for regulatory review.

    FDA feedback showed both approaches are technically feasible, highlighting practical needs around reproducibility, security, reviewer usability, and operational readiness.

    Read more: r-consortium.org/posts/beyond-

    #rstats #pharma

  15. The R Consortium R Submissions Working Group continues to help move regulatory submissions with R from concept to practical implementation.

    In Pilot 4, the group explored WebAssembly and Docker containers for packaging and running an R Shiny app for regulatory review.

    FDA feedback showed both approaches are technically feasible, highlighting practical needs around reproducibility, security, reviewer usability, and operational readiness.

    Read more: r-consortium.org/posts/beyond-

    #rstats #pharma

  16. The R Consortium R Submissions Working Group continues to help move regulatory submissions with R from concept to practical implementation.

    In Pilot 4, the group explored WebAssembly and Docker containers for packaging and running an R Shiny app for regulatory review.

    FDA feedback showed both approaches are technically feasible, highlighting practical needs around reproducibility, security, reviewer usability, and operational readiness.

    Read more: r-consortium.org/posts/beyond-

    #rstats #pharma

  17. spotlight! Meet Francesca Palmeira

    She is a biologist working on conservation conflicts and ecological modeling. Francesca participated on rOpenSci Champions Program, developing {pcir}, a package to calculate, compare, and visualize the Potential for Conflict Index among stakeholders.

    Find her at:

    🔗 in/francesca-palmeira-06393725a
    💻 github.com/fblpalmeira
    🌐 fblpalmeira.github.io

  18. #MaintainerMonth spotlight! Meet Francesca Palmeira

    She is a biologist working on conservation conflicts and ecological modeling. Francesca participated on rOpenSci Champions Program, developing {pcir}, a package to calculate, compare, and visualize the Potential for Conflict Index among stakeholders.

    Find her at:

    🔗 in/francesca-palmeira-06393725a
    💻 github.com/fblpalmeira
    🌐 fblpalmeira.github.io

    #rOpenSci #RStats

  19. #MaintainerMonth spotlight! Meet Francesca Palmeira

    She is a biologist working on conservation conflicts and ecological modeling. Francesca participated on rOpenSci Champions Program, developing {pcir}, a package to calculate, compare, and visualize the Potential for Conflict Index among stakeholders.

    Find her at:

    🔗 in/francesca-palmeira-06393725a
    💻 github.com/fblpalmeira
    🌐 fblpalmeira.github.io

    #rOpenSci #RStats

  20. #MaintainerMonth spotlight! Meet Francesca Palmeira

    She is a biologist working on conservation conflicts and ecological modeling. Francesca participated on rOpenSci Champions Program, developing {pcir}, a package to calculate, compare, and visualize the Potential for Conflict Index among stakeholders.

    Find her at:

    🔗 in/francesca-palmeira-06393725a
    💻 github.com/fblpalmeira
    🌐 fblpalmeira.github.io

    #rOpenSci #RStats

  21. #MaintainerMonth spotlight! Meet Francesca Palmeira

    She is a biologist working on conservation conflicts and ecological modeling. Francesca participated on rOpenSci Champions Program, developing {pcir}, a package to calculate, compare, and visualize the Potential for Conflict Index among stakeholders.

    Find her at:

    🔗 in/francesca-palmeira-06393725a
    💻 github.com/fblpalmeira
    🌐 fblpalmeira.github.io

    #rOpenSci #RStats

  22. Land cover of India. This was edifying. I had no idea so much land was devoted to crops. I mean, I sorta knew but seeing it this way really hammered it home. This was also the render that drove me to pure GDAL for raster operations.

    adventures, an tale

  23. Land cover of India. This was edifying. I had no idea so much land was devoted to crops. I mean, I sorta knew but seeing it this way really hammered it home. This was also the render that drove me to pure GDAL for raster operations.

    #rayshader adventures, an #rstats tale

  24. Land cover of India. This was edifying. I had no idea so much land was devoted to crops. I mean, I sorta knew but seeing it this way really hammered it home. This was also the render that drove me to pure GDAL for raster operations.

    #rayshader adventures, an #rstats tale

  25. Land cover of India. This was edifying. I had no idea so much land was devoted to crops. I mean, I sorta knew but seeing it this way really hammered it home. This was also the render that drove me to pure GDAL for raster operations.

    #rayshader adventures, an #rstats tale

  26. Land cover of India. This was edifying. I had no idea so much land was devoted to crops. I mean, I sorta knew but seeing it this way really hammered it home. This was also the render that drove me to pure GDAL for raster operations.

    #rayshader adventures, an #rstats tale

  27. a teammate shared one of @ivelasq3 workshop in team chat and I browsed her website and I really like the "TIL" section.

    ivelasq.rbind.io/til

    Did other try something similar? I am curious on feedback!

  28. a teammate shared one of @ivelasq3 workshop in team chat and I browsed her website and I really like the "TIL" section.

    ivelasq.rbind.io/til

    Did other try something similar? I am curious on feedback!

    #rstats

  29. a teammate shared one of @ivelasq3 workshop in team chat and I browsed her website and I really like the "TIL" section.

    ivelasq.rbind.io/til

    Did other try something similar? I am curious on feedback!

    #rstats

  30. a teammate shared one of @ivelasq3 workshop in team chat and I browsed her website and I really like the "TIL" section.

    ivelasq.rbind.io/til

    Did other try something similar? I am curious on feedback!

    #rstats

  31. a teammate shared one of @ivelasq3 workshop in team chat and I browsed her website and I really like the "TIL" section.

    ivelasq.rbind.io/til

    Did other try something similar? I am curious on feedback!

    #rstats

  32. security issue in {insitu}

    I just received this AI-generated PR, which posits that a crafty user could lie about matrix dimensions and cause a malloc issue.

    But a malicious user can just do a "system()" call.

    So what's the point of addressing this "critical" security issue?

    github.com/coolbutuseless/insi

  33. #RStats security issue in {insitu}

    I just received this AI-generated PR, which posits that a crafty user could lie about matrix dimensions and cause a malloc issue.

    But a malicious user can just do a "system()" call.

    So what's the point of addressing this "critical" security issue?

    github.com/coolbutuseless/insi

  34. #RStats security issue in {insitu}

    I just received this AI-generated PR, which posits that a crafty user could lie about matrix dimensions and cause a malloc issue.

    But a malicious user can just do a "system()" call.

    So what's the point of addressing this "critical" security issue?

    github.com/coolbutuseless/insi

  35. #RStats security issue in {insitu}

    I just received this AI-generated PR, which posits that a crafty user could lie about matrix dimensions and cause a malloc issue.

    But a malicious user can just do a "system()" call.

    So what's the point of addressing this "critical" security issue?

    github.com/coolbutuseless/insi

  36. #RStats security issue in {insitu}

    I just received this AI-generated PR, which posits that a crafty user could lie about matrix dimensions and cause a malloc issue.

    But a malicious user can just do a "system()" call.

    So what's the point of addressing this "critical" security issue?

    github.com/coolbutuseless/insi

  37. ANyone know a good CONTRIBUTING.md (or similar) that I can add to my projects such that:

    * Issues and PRs have to be from humans.
    * I don't mind if you use AI, but don't just auto-drench my repository with AI generated reports.

    #RStats

  38. ANyone know a good CONTRIBUTING.md (or similar) that I can add to my projects such that:

    * Issues and PRs have to be from humans.
    * I don't mind if you use AI, but don't just auto-drench my repository with AI generated reports.

  39. ANyone know a good CONTRIBUTING.md (or similar) that I can add to my projects such that:

    * Issues and PRs have to be from humans.
    * I don't mind if you use AI, but don't just auto-drench my repository with AI generated reports.

    #RStats

  40. ANyone know a good CONTRIBUTING.md (or similar) that I can add to my projects such that:

    * Issues and PRs have to be from humans.
    * I don't mind if you use AI, but don't just auto-drench my repository with AI generated reports.

    #RStats

  41. ANyone know a good CONTRIBUTING.md (or similar) that I can add to my projects such that:

    * Issues and PRs have to be from humans.
    * I don't mind if you use AI, but don't just auto-drench my repository with AI generated reports.

    #RStats

  42. Because I'm a glutton for punishment, I'm resurrecting (trying for a third time) {getCRUCLdata}. I'm not even sure that anyone uses it, but since I still have it sitting around, I've overhauled it and rewritten it to remove any caching, using {rappdirs} got me in trouble the first time, using R's own user cache directory got me in trouble the second time. So twice archived, now going back with no caching aside from in-session via {httr2}. codeberg.org/ropensci/getCRUCL #RStats #ClimateData

  43. Because I'm a glutton for punishment, I'm resurrecting (trying for a third time) {getCRUCLdata}. I'm not even sure that anyone uses it, but since I still have it sitting around, I've overhauled it and rewritten it to remove any caching, using {rappdirs} got me in trouble the first time, using R's own user cache directory got me in trouble the second time. So twice archived, now going back with no caching aside from in-session via {httr2}. codeberg.org/ropensci/getCRUCL #RStats #ClimateData

  44. Because I'm a glutton for punishment, I'm resurrecting (trying for a third time) {getCRUCLdata}. I'm not even sure that anyone uses it, but since I still have it sitting around, I've overhauled it and rewritten it to remove any caching, using {rappdirs} got me in trouble the first time, using R's own user cache directory got me in trouble the second time. So twice archived, now going back with no caching aside from in-session via {httr2}. codeberg.org/ropensci/getCRUCL #RStats #ClimateData

  45. Because I'm a glutton for punishment, I'm resurrecting (trying for a third time) {getCRUCLdata}. I'm not even sure that anyone uses it, but since I still have it sitting around, I've overhauled it and rewritten it to remove any caching, using {rappdirs} got me in trouble the first time, using R's own user cache directory got me in trouble the second time. So twice archived, now going back with no caching aside from in-session via {httr2}. codeberg.org/ropensci/getCRUCL #RStats #ClimateData