Skip to content

Commit 38abade

Browse files
Update posts/zzz_DO_NOT_EDIT_automatic_s.../automatic_slide_generation_with_{autoslide_r}.qmd
Co-authored-by: Joe Zhu <[email protected]>
1 parent 8a2ff98 commit 38abade

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

posts/zzz_DO_NOT_EDIT_automatic_s.../automatic_slide_generation_with_{autoslide_r}.qmd

+3
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,10 @@ link::auto()
2424
<!--------------- post begins here ----------------->
2525

2626
We are excited to announce that the {autoslider.core} package is now a part of pharmaverse!
27+
28+
The normal process of creating clinical study slides is that a statistician manually type in the numbers from outputs and a separate statistician to double check the typed in numbers. This process is time consuming, resource intensive, and error prone.
2729
This package lets users create slides with study-specific outputs in an automated and reproducible way -- without the need to copy-paste.
30+
It reduces the amount of work and the required time when creating slides, and reduces the risk of errors from manually typing or copying numbers from the output to slides. It also helps users to avoid unnecessary stress when creating large amounts of slide decks in a short time window.
2831
It is particularly helpful for slides that need to be continuously created with updated data, such as slides needed for dose-escalation meetings.
2932

3033
The autoslider development work started as an internal initiative, and as it grew over the years, it was well received, we decided to open-source this package, at the same time not causing any downstream breaking changes to our users. therefore, the autoslider package became two layers, the outer layer exposed to internal use remains as autoslider, which now mostly contains Roche-specific formats, layouts and designs, and the inner layer, aka {autoslider.core}, which controls the rendering and workflow, are open source, it is fully functional and user-facing on its own as well. We consider {autoslider} as a framework, and would like to invite users to build your own {autoslider.*} packages as well. For more developer guidelines, you can find them at the [package homepage](https://insightsengineering.github.io/autoslider.core/latest-tag/articles/opensource.html)

0 commit comments

Comments
 (0)