ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ

@drmowinckels

Staff scientists / RSE @LCBC_UiO & @LifebrainEU. She/Her. PhD Cognitive Neurosciences 🧠 @rladies.org Global Team. #Rstats #Nerd 🌈🏳️‍🌈

645 Following3,029 Followers1,748 Posts

Bluesky

Is this your profile?Claim it and drmowinckels.dirty.social is yours.Claim profile

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· 15d

101 tests passed — then R crashed on exit with a Windows stack-buffer-overrun 🫠 I wrapped Rust's link checker lychee into an R package (rambutan). The whole trip, teardown bug and all: #rstats #rust https://l.drmowinckels.io/ajLoWM

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Jul 16

Its so dang warm! Happy we have AC to cool down. Even forced the cat to stay indoor the last hour so she is out of the worst of it and can cool down.

screenshot of a weather station report showing its 34C, and feels like 39C

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Jul 15

I'm an R person who just shipped two cross-platform desktop apps in Rust + Tauri + React — a stack I'd never written before. One built straight in code with Claude, one designed first as a clickable artifact. Story: https://l.drmowinckels.io/sNeRrN

A modern minimalist desk setup in warm, natural light. On a light wooden surface, a stylized cairn of stacked stones glows with digital, circuit-board patterns. Next to it, an open silver laptop displays a dark-mode productivity dashboard with charts and UI elements labeled "Cairn." A blurred succulent sits in the background.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Jun 20

Do you use The StoryGraph to catalogue the books you read, and find it cumbersome to sync the devices you read from to the website? drmowinckels.io/storywell/ #books #storyGraph #bibliophile

Promotional banner for Storywell — "Sync your shelf" service that pulls every finished book from Audible, Goodreads and more and marks them read on The StoryGraph.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Jun 1

Quarto's `hugo-md` format wraps every figure in raw HTML, so Hugo's image render hook never fires on them. Fifteen lines of Lua + one line in `_quarto.yml` and every figure comes out as clean `![alt](src)` markdown instead. https://l.drmowinckels.io/WgOEMR

A simplified diagram showing a Quarto qmd document on the left flowing through a Lua filter labelled figure-to-markdown into a Hugo theme on the right, with the figure being converted from HTML to a clean markdown image syntax.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Mar 30

ggseg.extra now builds cortical brain atlases directly from the mesh geometry! A 150-region Destrieux atlas tok 9 seconds. No screenshots, no ImageMagick, no headless browser. #rstats #neuroscience #brainimaging

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Mar 18

It's full of new features, and likely lots of new bugs. I'd love folks to test how it works, I've really tried making things more robust and I hope its payed off! #rstats #ggsegverse #neuroimaging

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Mar 2

My dotfiles now manage my AI coding agents 🤖 Same instructions for Claude Code and OpenCode, symlinked from one repo. Here's how I set it up: https://drmo.site/CCrf37

A minimalist isometric 3D illustration on a dark background showing a central glowing cube labeled ".dotfiles" with a git icon. Glowing neon lines radiate from the cube to icons representing "Shell Config," "Editor & Tooling," and "AI Agents (Claude & OpenCode)." A sidebar labeled "Skills Marketplace" displays specialized icons for R, Shiny, Quarto, and writing voices, illustrating a unified development environment.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Feb 15

New neuromapr #rstats package is available from GitHub! Highly experimental, early adopters and bug identifiers are super welcome to report issues! github.com/lcbc-uio/neu... #neuroscience #rstats #neuroimaging

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Feb 9

The ggseg ecosystem finally has a proper home! 🧠 For those who don't know, ggseg is an R package ecosystem for visualizing brain atlas data. Think ggplot2, but for brains. #rstats #neuroimaging #openscience

Dark blue hexagon, with a light blue frame. Features a brain facing the left, with the front half as a wire-frame mesh of light blue, and the back half with several polygon segments of different colours. Below is written "ggseg" in light blue.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Feb 3

Stop playing "diagnostics ping-pong" with your users 🏓 Wrote about why every R package wrapping external tools needs a sitrep() function — with real examples from meetupr and freesurfer. #RStats https://drmo.site/F5gVjR

A close-up view of a computer monitor in a dimly lit room, showing a terminal console. The terminal displays the output of an R function called meetupr_sitrep(). The report shows green checkmarks for "Active Authentication" and "Cached Token," and a blue information icon for package settings. At the bottom, a red "X" marks a failed "API Connectivity Test," illustrating a diagnostic situation report in action. In the foreground, a coffee mug and a person’s hand on a keyboard are visible but slightly out of focus.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Jan 23

15 years together, and going strong. Growing, learning, supporting, laughing, crying, loving.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Jan 19

My 2025 Year in Review is out! 📝 A year of deliberate work amidst post-COVID recovery. Highlights: deep dives into #RStats APIs w/ #httr2, the R Package Dev Advent Calendar, & `ggseg` improvements. Focus on sustainable, impactful work. Read more & share your 2025! 👇 https://drmo.site/8NNsxa

image of a woman (me) with dark hair and glasses wearing mauve-burgundy dress, sitting next to an evergreen tree decorated with lights and Christmas ornaments

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Jan 16

Managing a Hugo site gets complex fast - builds, dev servers, and getting dependencies where Hugo expects them. Here's how npm scripts solved our R-Ladies website workflow 🧵 #Hugo #NPM #WebDev #BuildTools #OpenSource #Automation

$NPM json setup. ```json { "name": "hugo-rladies-theme-js", "private": true, "version": "0.1.0", "scripts": { "clean": "rm -rf assets/js/vendor assets/scss/vendor", "setup": "mkdir -p assets/js/vendor assets/scss/vendor", "build": "npm run clean && npm run setup && npm run sync:bootstrap && npm run sync:jquery", "sync:bootstrap": "cp node_modules/bootstrap/dist/js/bootstrap.bundle.min.js* assets/js/vendor/ 2>/dev/null || true && cp -r node_modules/bootstrap/scss assets/scss/vendor/bootstrap", "sync:jquery": "cp node_modules/jquery/dist/jquery.min.js* assets/js/vendor/ 2>/dev/null || true", "update": "npm update && npm run build", "postinstall": "npm run build" }, "dependencies": { "bootstrap": "^5.3.8", "jquery": "^3.7.0" } } ```$

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 28

My #RPackageAdvent2025 recap is live! 📦✨ Get the complete guide to modern R package development: setup, docs, testing, CI/CD, and CRAN submission. All 25 days of tips, tools, and best practices in one place! Dive in! #RStats #RPackageDevelopment Link: https://drmo.site/8ny3eU

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 26

We Made It! 🎉 25 days. Complete modern R package development workflow. From usethis automation to CRAN submission. You have everything you need! #rstats #CRAN #RPackageAdvent2025 #ThatsAWrap

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 25

Day 25: CRAN Submission Checklist and cran-comments.md Final steps for successful CRAN submission. Pro Tip: Be proactive about communicating any unusual aspects of your package to CRAN reviewers. #rstats #RPackageAdvent2025

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 24

Happy Christmas to all who celebrate, and to those who don't I hope you get to enjoy the end of the year. We celebrated just the three of us, with a quiet and lovely celebration. After two Christmases that have been quite difficult, it was nice to have a semblance of normality.

image of a woman (me) with darl hair and glasses wearing mauve dress, sitting next to an evergreen tree decorated with lights and Christmas ornaments

photo of a tabby cat sitting on a rug being incredibly cute

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 24

Day 24: rlang - Tidy Evaluation in Packages Handle user expressions safely in package functions. Pro Tip: Use {{ }} (embrace) for single arguments, ... for multiple arguments. Resources: rlang.r-lib.org #rstats #RPackageAdvent2025

$my_summarise <- function(data, ...) { data |> dplyr::summarise(...) }$

$my_mutate <- function(data, col, value) { data |> dplyr::mutate({{ col }} := value) }$

$my_function <- function(...) { dots <- rlang::list2(...) # process dots }$

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 23

Day 23: cli - Beautiful Command Line Interfaces Create user-friendly messages and progress indicators. Pro Tip: Use semantic markup like {.fn function_name} and {.val value} for consistent formatting. Resources: cli.r-lib.org #RpackageAdvent2025 #rstats

$cli::cli_progress_bar("Processing files", total = length(files)) for (file in files) { # process file cli::cli_progress_update() }$

$cli::cli_alert_success("Package built successfully!") cli::cli_alert_warning("Missing documentation for {.fn my_function}") cli::cli_abort("Invalid input: {.val {invalid_value}}")$

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 22

Day 22: S3, S4, and S7 Object Systems Create robust object-oriented interfaces with R's object systems. Pro Tip: Use S3 for simple classes, S4 for complex validation, S7 for modern OOP. Resources: rconsortium.github.io/S7 #rstats #RPackageAdvent2025

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 21

Day 21: rhub - Multi-Platform Testing (Thread) Test your package on multiple platforms before CRAN submission. Resources: r-hub.github.io/rhub/ #rstats #RPackageAdvent2025

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 20

Day 20: Performance Testing with bench Profile and benchmark your package functions. Pro Tip: Include benchmarks in your test suite to catch performance regressions. Resources: bench.r-lib.org #rstats #RPackageAdvent2025

bench::mark(
my_function(big_data),
filter_gc = FALSE
)

results <- bench::mark(
old_approach = old_function(data),
new_approach = new_function(data),
check = FALSE, # Skip result equality check
iterations = 100
)
plot(results)

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 19

5/ The Bottom Line: goodpractice is your package health checkup. Catches issues before they become problems. Run regularly, maintain quality.

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 18

Day 18: Use linters! Maintain consistent, readable code style automatically. Usage: lintr::lint_package() styler::style_pkg() Pro Tip: Add both to pre-commit hooks for automatic code formatting. Resources: lintr.r-lib.org #rstats #RPackageAdvent2025

# .lintr file in project root
linters: linters_with_defaults(
line_length_linter(120),
commented_code_linter = NULL
)

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 17

Day 17: vcr - Recording API Calls for Tests Record real API responses for reliable, fast tests without hitting live APIs. Pro Tip: Commit cassette files to git for reproducible tests across environments. Resources: docs.ropensci.org/vcr #rstats #RPackageAdvent2025

$# In vignette setup vcr::use_cassette("demo_data", { demo_data <- fetch_api_data("example") })$

$test_that("API returns expected data", { use_cassette("github_api", { response <- httr::GET("https://api.github.com/users/octocat") expect_equal(httr::status_code(response), 200) }) })$

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 16

Day 16: Testing with Mocks using testthat Test functions that depend on external resources using testthat's built-in mocking. Pro Tip: Use local_mocked_bindings() to mock functions within the test scope only. Resources: testthat.r-lib.org #rstats #RPackageAdvent2025

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 15

Day 15: Snapshot Testing with testthat Test complex outputs that are hard to specify exactly. Pro Tip: Review snapshot changes carefully - they capture everything, including whitespace and formatting. #rstats #RPackageAdvent2025

$test_that("plots look right", { p <- ggplot(mtcars, aes(mpg, wt)) + geom_point() vdiffr::expect_doppelganger("mtcars-scatter", p) })$

$test_that("error messages are informative", { expect_snapshot(my_function(bad_input), error = TRUE) })$

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 14

Day 14: testthat 3rd Edition Features Modern testing with the latest testthat features. Setup: usethis::use_testthat(3) Pro Tip: Use test_that() with descriptive names that explain what should happen. Resources: testthat.r-lib.org #rstats #RPackageAdvent2025

$test_that("plot output is stable", { p <- my_plot(data) vdiffr::expect_doppelganger("basic-plot", p) })$

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱ@drmowinckels· Dec 13

Day 13: covr - Test Coverage Reporting Track how much of your code is tested. use #nocov for code you don't want to cover (like basic R functions etc) Pro Tip: Focus on testing critical functions thoroughly rather than chasing 100%. Resources: covr.r-lib.org #rstats #RPackageAdvent2025