Skip to content
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

closes #143 Navitas R blog #150

Merged
merged 7 commits into from
May 2, 2024

Merge branch 'main' into 143_navitas_R_blog

2a0e238
Select commit
Loading
Failed to load commit list.
Merged

closes #143 Navitas R blog #150

Merge branch 'main' into 143_navitas_R_blog
2a0e238
Select commit
Loading
Failed to load commit list.
Task list completed / task-list-completed succeeded May 2, 2024 in 0s

9 / 9 tasks completed

All tasks have been completed

Details

Required Tasks

Task Status
Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side Completed
Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file! Completed
Choose (possibly several) tag(s) or categories from the current list: c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Community", "Conferences", "Submissions", "Technical") for your blog post. If you cannot find anything that fits your blog post, add your own tag! We occasionally tidy up all tags for consistency. Completed
Add a short description for your blog post in the description field at the top of the markdown document. Completed
Blog post is short, personalized, reproducible and readable Completed
Add a disclaimer at the top of your post, if appropriate (example: Disclaimer
This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.) Completed
Address all merge conflicts and resolve appropriately Completed
Assign two of us (@bms63, @manciniedoardo, @StefanThoma, @kaz462) as reviewers in the PR. Completed
Pat yourself on the back for a job well done! Much love to your accomplishment! Completed
Added ® after any mention of SAS and removed mention of SAS “high cost” as such negative wording would not be suitable to place in a public blog in my opinion Incomplete
Removed the dual programming section as don’t think it added any value for this blog to show that same table can be created in SAS or R Incomplete
Added reference to pharmaverse as otherwise why post this blog on our site Incomplete
I updated some of the wording such as R “usage is currently below par” as I don’t actually think it’s true – some of the blog reads more like a viewpoint from 2-3 years ago compared to the growing momentum we now see in R in our industry Incomplete
Removed “The notable difference between SAS® and R is that SAS® is proprietary software, whereas R is an open-source programming language” as I feel readers would know this Incomplete
Added reference to R consortium R submissions WG Incomplete
I replaced the package examples given with pharmaverse examples as again this is a pharmaverse blog Incomplete
Mentioned R Validation Hub rather than R Foundation for more specificity Incomplete
Added a note on licensing Incomplete
Learning curve of R removed “steep” and “lacks direct support from the company,” as those are not the case in many of the across-industry experiences I’ve seen Incomplete
Added some images to help brighten the blog Incomplete