-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guidance on how to generate figures and tables in a for loop (DRY principle) #156
Comments
@mayerbry we discussed this yesterday, would be great to have your thoughts. |
A better example from conversation with Bryan on July 31st:
|
Thank you to Kellie's great TIOT on Oct 24, 2024 (and @asatofh for organizing) we had some great brainstorming related to this topic! I'm tagging folks who can share the relevant code, packages and/or challenges so we can provide guidance on creating multiple similar figures and/or tables at once. Knowing other people's blockers and challenges is really helpful so we don't all repeat the same issues in silos: @at-crx Amanda shared some of her experiences with the challenges trying to create figures in a loop (issues: trying to reference figures, and the possibility of mismatching inputs when they're in the form of independent lists. for example a list of captions and a list of plot titles, etc.) Would love to see relevant code! So please share! I am currently working on a report using these methods so any code or further thoughts shared sooner rather than later are appreciated and will be referenced for specific reports as well as general guidance for all of us. Thank you all and especially @kelliemac for the presentation, and great conversation! |
Courtesy of @bneradil As described hvtnReports has a vignette on caption creation here: |
thank you @lemireg for capturing today's discussion!!!! this is really helpful. |
To follow the DRY (don't repeat yourself) principle, it is sometimes helpful to generate figures and tables in a for loop. For example, in the B-cell reports we are usually generating the same tables and figures repeatedly for different endpoints.
I think this challenge probably also applies in other assays. One approach is as follows:
Is this broadly applicable enough that it would be helpful to incorporate some version of this into the report template?
If so, any improvements to suggest?
The text was updated successfully, but these errors were encountered: