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 #168 University post #213

Merged
merged 20 commits into from
Sep 16, 2024
Merged

Closes #168 University post #213

merged 20 commits into from
Sep 16, 2024

Conversation

syon45
Copy link
Collaborator

@syon45 syon45 commented Sep 3, 2024

Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

  • 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
  • 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!
  • 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, propose a new tag to the maintainers! Note: if you use a tag not from this list, the "Check Post Tags" CICD pipeline will error. We occasionally tidy up all tags for consistency.
  • Add a short description for your blog post in the description field at the top of the markdown document.
  • Blog post is short, personalized, reproducible and readable
  • 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.)
  • Address all merge conflicts and resolve appropriately
  • Assign two of us (@bms63, @manciniedoardo, @StefanThoma, @kaz462) as reviewers in the PR.
  • Pat yourself on the back for a job well done! Much love to your accomplishment!

@manciniedoardo
Copy link
Collaborator

Thanks @syon45 - as discussed in person, please try resolve the failing CICD checks while I review your post 😄

Copy link
Collaborator

@manciniedoardo manciniedoardo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @syon45 please take a look at my comments 😄

Copy link
Collaborator

@StefanThoma StefanThoma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see there is a qmd and an Rmd file with otherwise the same name and content.
Which do you want to use?

(In the end it should be a qmd file I think)

Otherwise I added some minor changes requested.

Cool post :)


The quantitative project report investigates statistical analyses on preliminary clinical trial data using the R Studio software as instructed by the trainStats program I have authored to help ease new Biostatisticians in the industry. The software was built considering the needs of people who are keen to pursue a career in Biostatistics, and was inspired from some exploratory analyses I had done during my placement year with the Ophthalmology Precision Medicine (OPM) group. It entails both hard abilities such as programming, data visualisation and modelling alongside soft skills like logic, reasoning and communication.

I had a smooth experience with pharmaverse all throughout my business and university project. I was introduced to the package by Ross Farrugia while looking for open-source data to analyse for my project. The package was very easy to read and use, with excellent documentation on the pharamverseadam website. As I was planning to share aggregated outputs (such as tables, listings and graphs) from clinical datasets externally to the university, even using historical clinical data was not allowed since external use of confidential data did not align with Roche's FAIR Data principles.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pharmaverse is a collection of packages, not just one package. Or do you mean a specific package?

I think it is not due to the FAIR data principles that sharing data outside of Roche is problematic, but rather an issue with data privacy.


I had a smooth experience with pharmaverse all throughout my business and university project. I was introduced to the package by Ross Farrugia while looking for open-source data to analyse for my project. The package was very easy to read and use, with excellent documentation on the pharamverseadam website. As I was planning to share aggregated outputs (such as tables, listings and graphs) from clinical datasets externally to the university, even using historical clinical data was not allowed since external use of confidential data did not align with Roche's FAIR Data principles.

Throughout the trainStats documentation, I have primarily used the `adoe_ophtha` dataset to allow for a variety of exploratory statistical analyses ranging from producing boxplots of the spread of data by visit day, computing standard deviation and confidence intervals for endpoints, as well as programming linear regression models and patient profiles. As the "adoe_ophtha" ADaM dataset contains visit day, active arm and endpoint data, it was ideal to use for training purposes. In addition, I did use the "adsl" dataset too, to encourage trainStats users to join and merge datasets, taking into account patient demographics such as Age.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you link the trainStats? Is this publicly available?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not yet! It is not publicly available as of now unfortunately

Copy link
Collaborator

@StefanThoma StefanThoma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@manciniedoardo manciniedoardo merged commit 1f07278 into main Sep 16, 2024
5 checks passed
@manciniedoardo manciniedoardo deleted the 168universitypost branch September 16, 2024 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants