i can hack things with calls to system() to move files after they’re generated but having the source live in a subdirectory too seems to be painful if i’m trying to adhere to the best practice of having all paths start at the project root (e.g., using {here})
does anyone have a good example of a repository where parameterized #quarto reports are generated but the source and/or outputs live in subdirectories?
i’m having trouble setting a project up so that i don’t end up with a bunch of generated reports at the top level… 🤔
very nice! how did you decide on making the y-coordinates follow a sigmoid? did you consider/try any alternatives?
thanks for the rec! the features look great and i was able to painlessly migrate my pocket data 🎉
does anyone know of a good read-it-later service/method? my go-to service, pocket, is shutting down 😔
oh! i misread your example. i thought left was step 1 and right was step 2. i agree—it’s convenient to have it all rolled up in one function 🎉
interesting! is there a benefit to using reader::parse_number() over as.numeric()?
❗️Our next workshop will be on May 8th, 6 pm CEST, on Retrieving and Generating Data using LLMs in Python by
@prashantgarg.bsky.social!
Register or sponsor a student by donating to support Ukraine!
Details: bit.ly/3wBeY4S
Please share!
#AcademicSky #EconSky #Python
super interesting data exploration. thanks for sharing!
there are a few ways to save content. i use a web browser extension on my laptop. on my phone, i have the iOS Pocket app, which comes with share menu integration: when you go to share a site in your web browser, you can tap the Pocket icon to add it to your saves
yes, it basically saves links and then gives you an interface (mobile app or website) to read the content you've saved
i like to tag my saves to help remind myself of why i saved them, and you could use that to organize into topics
when i've read something, i archive it for safe keeping 💾
🚨 this is my final thread here! what a blast. this week has really just flown by 🫠
we've discussed a lot of great #rstats topics this week 🎉 including...
i don’t know! i had the same thought during your curation week. agreed, would be great to connect 😊
hello hello 👋 my name is irena and i'm excited to be your #rladies Rotating Curator this week! 👩🎨🦋
a little bit about me...
Irena, Scientist, infectious disease modelling. They say, "Writes a lot of analysis and reporting pipelines for infectious disease models, so often reaches for {targets}, {renv} and {config}."
This week’s #RLadies curator is
@papsti.bsky.social
programming is just the art of adding bugs to an empty file
also using GitHub Desktop as a starter interface since it’s point and click and has built in diffs, but then peeling back the layers with command line git.
have new users try to draw diagrams of what’s happening (staging vs committing, pushing up to a cloud server). the mental model is the biggest hurdle in my experience teaching git to others. once they understand what’s happening, the commands aren’t too hard to remember.
my talk gives an overview of targets and some opinionated advice. if you want a more hands-on experience with the package, check out the tutorials i point to here:
papsti.github.io/talks/2025-0...
“what the hell was i doing here…?”
“my best 🥲”
looking forward to the point in my career where i don’t cringe at code i wrote two years ago (retirement)
as a cancer, can confirm 🙃
The {target} package for #reproducible #pipelines & tracking dependencies has recently been written about by
@djnavarro.net in her blog,
blog.djnavarro.net/posts/2025-0...
&
R-Ladies Philly had their meetup with @papsti.bsky.social talking about her learning experiences.
youtu.be/OCFAYFeOQ7w?...
In the January R-Ladies Philly 🔔 meetup ✨Irena Papst✨ @papsti.bsky.social generously shared {targets} tips based on her own learning experiences. 💜 Check out the recording on YouTube! 👀 https://buff.ly/3WuVL2y #rstats #rladies
