Daniel 🕹️ (@strengejacke) 's Twitter Profile
Daniel 🕹️

@strengejacke

He/she/it - 's' muss mit.
We're lower than the world!
Mastodon: fediscience.org/@strengejacke
Blue sky: bsky.app/profile/streng…

ID: 91195150

linkhttp://www.strengejacke.de calendar_today19-11-2009 21:18:13

2,2K Tweet

1,1K Followers

87 Following

Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

New paper on "Intersectional inequalities in health anxiety" published, using the MAIHDA approach: frontiersin.org/journals/publi…

Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

And another new paper about "Political party affiliation, social identity cues, and attitudes about protective mask-wearing during the pandemic", combining quantitative and qualitative methods: dx.plos.org/10.1371/journa…

easystats (@easystats4u) 's Twitter Profile Photo

Are you working with mixed (multilevel) models in #rstats and wondering how to calculate R2? Grab the latest updates of our #easystats {performance} and {insight} packages from CRAN and try out "r2_nakagawa()" (or simply "r2()" for mixed model): easystats.github.io/performance/re… /1

Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

Just discovered the #rstats {ggdag} package, which is really cool! So easy to create, visualize and test DAGs using familiar intuitive R syntax: r-causal.github.io/ggdag/

easystats (@easystats4u) 's Twitter Profile Photo

A new feature that *might* be added to our #rstats #easystats packages soon: checking models for correct adjustment by using DAGs! `check_dag()` (working title) makes it so easy to check the causal paths of your model and tells you how to address misspecifications!

A new feature that *might* be added to our #rstats #easystats packages soon: checking models for correct adjustment by using DAGs! `check_dag()` (working title) makes it so easy to check the causal paths of your model and tells you how to address misspecifications!
Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

This looks good! If you're interested in testing this feature, try `install.packages(c("performance", "see"), repos = "easystats.r-universe.dev")`. #rstats #easystats

Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

The function was improved and now can deal with multiple possible adjustment sets #DAG #rstats #easystats Check out at easystats.github.io/performance/re…

The function was improved and now can deal with multiple possible adjustment sets #DAG #rstats #easystats
Check out at easystats.github.io/performance/re…
Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

Always remember to run `easystats::install_latest()` every now and then, to grab the latest cool features of the the #easystats-verse! And the package documentations are always worth reading,e.g. easystats.github.io/bayestestR/ :-) #rstats

Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

Some nice people made a podcast about a function in the #easystats {parameters} package: youtube.com/watch?v=CFmAPB… 😎 #rstats

Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

"We ask, how compatible is a slightly lopsided, maybe a tad overbaked caked with the idea of delicious?" - explaining compatibility intervals and p-values in layman's terms. youtube.com/clip/UgkxPAyTM…

Yury Zablotski (@yuzar___) 's Twitter Profile Photo

Multivariable Logistic Regression in R: The Ultimate Masterclass (4K)! youtu.be/EIR9zN0tDPw #rstats #statistics #dataanalysis #stats #datascience #r4ds

Multivariable Logistic Regression in R: The Ultimate Masterclass (4K)!

youtu.be/EIR9zN0tDPw

#rstats #statistics #dataanalysis #stats #datascience #r4ds
Mattan S. Ben-Shachar 🎗️🇮🇱🇺🇦 (@mattansb) 's Twitter Profile Photo

New update to {bayestestR} expands support for a tidy workflow - working better with tidy inputs, `rvar`s, and post-modeling estimates, and generating tidy outputs! easystats #rstats 🧵 easystats.github.io/bayestestR/

Daniel 🕹️ (@strengejacke) 's Twitter Profile Photo

Which of the following information below model output (last paragraph, not that one about uncertainty intervals) do you find useful/helpful and think it's worth printing? It's printed once per session. Should some/all information moved into the docs, or kept in output? #easystats

Which of the following information below model output (last paragraph, not that one about uncertainty intervals) do you find useful/helpful and think it's worth printing? It's printed once per session. Should some/all information moved into the docs, or kept in output? #easystats