bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Server stats:

252
active users

#RStats

140 posts119 participants11 posts today

Imho, when it comes to likert-type data, the only reasonable way to make nil-hypotheses tests (like in standard regression outputs) semantically meaningful is to center the data beforehand. Not standardizing, most people can't read that correctly.
If you center, you can always interpret deviation from the mean, which is somewhat of a built-in feature, considering it is the backbone of estimation in many cases.
#rstats #stats

#RStats Dev Diary:

Playing with some Forward Error Correction code - similar to par2 & Reed-Solomon codes.

I'm considering making a package.

What should the package on FEC (Forward Error Correction) be named?

So I'll totally post this on the @Posit community forum, but thought the #rstats crowd here might have some ideas... about this potentially daft question.

So I'm pretty new to using Posit Connect. All seems pretty straight forward, but I'm not an admin so hard to tell exactly what is going on or might have been borked in setting it up.

The problem is, I can deploy a .rmd document with source code and have it schedule, and I can render everything locally fine, but if I try to deploy a quarto doc with source code it fails saying there is no rmarkdown package, which seems... weird. But this screenshot from the console make me think there should be a universal install of knitr/rmarkdown on the server maybe?

Do I just need to get an admin to install the packages? It seems so weird because packages (including knitr/rmarkdown) seem to be installing in the deploy process...

#rstats Is there an existing tool to automate a repex->rpubs pipeline? My current manual workflow is make a reprex in an .R script, copy the contents over to a .qmd, and use the publish feature in the rstudio IDE.

Sometimes my reprexes get just a tad bit more complex and requires some prose to walk through the steps. In those cases I like publishing them as almost like standalone micro blogposts.

Ex: this reprex doc I made to show how to recover ggrepel coordinates rpubs.com/yjunechoe/ggrepel-re

rpubs.comRPubs - Recover ggrepel drawn positions

#rstats hivemind: would it be too funky to define a package version major.minor.patch.dev as YYYY.MM.DD.VERSION, i.e. map major to year, minor to month, patch to day, and leave the dev component for the actual version..? I'm thinking of a data package whose upstream data releases are versioned based on the date... anyone ever tried such heretic approach? Would CRAN maintainers be okay with this?! ;)

asking for a friend.