2026-05-05 00:32 UTC
Replies (4)
-
@drmorrisj@mastodon.social 2026-05-05 01:02
@vincentab@fosstodon.org hey!! I am a huge fan of your datasets. Really good stuff. That said, are you looking more for an existing framework or a method that you can tune for your purposes?
-
@HansVL@mstdn.social 2026-05-05 03:54
@vincentab@fosstodon.org Maybe the 'description' argument of 'targets::tar_target'?
-
@climbertobby@chaos.social 2026-05-05 05:47
@vincentab@fosstodon.org If you are in the clinical trials field and want the big guns to have regulatory grade documentation: CDISC For smaller projects like papers with observational studies, the usual literate programming tools like R markdown, Sweave, ... worked very well for me. (Not jupyter workbooks though, it's too easy to not run the cells in the correct order, save state between running them, ... on accident)
-
@RossGayler@aus.social 2026-10-24 06:04
@vincentab@fosstodon.org Hi Vincent - where did you end up with this question? FWIW when I was doing large model development projects (years ago) I ended up with multiple, long R-markdown notebooks. Human readable = yes, machine readable = no (-ish). Questions and decisions were highlighted in numbered text boxes. I also kept a data dictionary (as an R data frame) that evolved programmatically over the course of the analyses. New variables were added to the data dictionary as a they were generated in the analyses and the variables were tagged with analysis-relevant properties (so I could, for example, programmatically select variables to use as predictors in a model). The analyses were reproducible by re-running the notebooks. This was pre [targets] which I would probably use now. At the time I used [workflowr]. I suspect this was less structured than you were looking for. The issue is that it mostly realied on me trying really hard to be systematic and reflect all the decisions in the free text.