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 #14: ADTTE + ADRS with PFS examples #64

Merged
merged 46 commits into from
Oct 7, 2024

Conversation

DavidBlairs
Copy link
Collaborator

@DavidBlairs DavidBlairs commented Apr 16, 2024

Pull Request

Howdy. I've had a go at writing up the examples for ADRS and ADTTE with PFS parameters. I think the ADTTE is a good draft (barring any amendment suggestions) but I'm thinking the ADRS article isn't sufficient just yet.

I was able to get a lot of information about ADTTE with PFS in the vignette provided here. However, there was nothing specifically relating to add PFS parameters in the basic ADRS vignette or in the more detailed version. I'd appreciate any assistance on this as well as any criticism on the ADRS example.

@rossfarrugia I added my name in the DESCRIPTION file in another PR, hence why you won't find it here.

  • Title: Place Closes #<insert_issue_number> at the beginning of your PR title. Use the Edit button in the top-right if you need to update.
  • Linked Issue: Ensure the related issue is linked in the "Development Section" on the right-hand side.
  • First Contribution: If this is your first contribution, add yourself to the DESCRIPTION file.
  • Impact on Examples: If your updates impact any examples, review locally for warnings or errors in the impacted example pages.
  • Merge Conflicts: Developers should address any merge conflicts and merge upon successful review.
  • New Packages: If new packages were used, ensure they are included in the DESCRIPTION file's Imports section.
  • Updated Examples: If you added or updated an example, ensure it runs on the latest CRAN release versions of all packages used.
  • Testing Instructions: Provide instructions on how to test the code if necessary.

@DavidBlairs DavidBlairs linked an issue Apr 16, 2024 that may be closed by this pull request
@rossfarrugia
Copy link
Contributor

thanks @DavidBlairs - will try and take a look over the next week when get chance and sure i could help advise for any gaps.

@DavidBlairs
Copy link
Collaborator Author

Hello @rossfarrugia. Can I just clarify, when the issue says "ADRS and ADTTE with minimal PFS parameters" does that mean:

  1. create a minimal ADRS, then use the ADRS to create a minimal ADTTE and add PFS parameters
  2. or does it mean create an ADRS with minimal PFS parameters and create an ADTTE with minimal PFS parameters

@rossfarrugia
Copy link
Contributor

rossfarrugia commented Apr 18, 2024

@DavidBlairs probably option 2 is easiest as you can use the pharmaverseadam adrs_onco as input to your ADTTE example as chances are you may need more than the brief example you create here for ADRS and saves you having to save the final dataset in this repo to be re-used in your ADTTE example.

@DavidBlairs
Copy link
Collaborator Author

@DavidBlairs probably option 2 is easiest as you can use the pharmaverseadam adrs_onco as input to your ADTTE example as chances are you may need more than the brief example you create here for ADRS and saves you having to save the final dataset in this repo to be re-used in your ADTTE example.

Debatably, given that the ADRS vignettes don't describe how to add PFS parameters specifically for ADRS, I'd say its easier to have one article thats ADRS -> ADTTE w/ PFS in terms of the documentation available. I'm just not sure if thats acceptable for #14

@rossfarrugia
Copy link
Contributor

@DavidBlairs not sure i understand your point on the ADRS vignette - it shows here how to create disease progression parameter and here how to create death parameter, and these 2 then feed into ADTTE to create the PFS parameter.

I haven't had chance to review your PR yet sorry so in case it helps to further clarify here, i was imaging an ADRS example including a disease progression parameter and death parameter, and then an ADTTE example including a PFS parameter using these 2 from an ADRS.

@DavidBlairs
Copy link
Collaborator Author

@rossfarrugia that makes more sense. My confusion came from there not being anything specific in the ADRS vignette saying "PFS". Hold off on the review till next week, I'll give this a better go.

@DavidBlairs DavidBlairs marked this pull request as ready for review April 24, 2024 14:04
@DavidBlairs
Copy link
Collaborator Author

@rossfarrugia I think this is in a good place to receive critique. I look forward to your feedback

Copy link
Contributor

@rossfarrugia rossfarrugia left a comment

Choose a reason for hiding this comment

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

@DavidBlairs thanks for the first draft of these! i made some suggestions from an initial review of mainly the ADRS example. if you could make updates consistently across both then i'd be able to take another look and will spend a bit more time next review on ADTTE. let me know if any of my suggested updates are unclear as to why needed.

adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adtte.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adtte.qmd Outdated Show resolved Hide resolved
Applies to both `adrs.qmd` and `adtte.qmd`. Simplified the title and added order parameter.
Simplified the first paragraph.
Simplified the second paragraph.
Add curly brackets around package names.
Simplified the opening paragraph in the `Required Packages` section.
Simplified the first paragraph in the `Loading Data` section.
Simplified the second paragraph in the `Loading Data` section.
Changed `ADSL` to `adsl` in the `Merging Data` section.
Simplified paragraph 1 in the `Apply the Worst Response Function` section.
Simplified paragraph 1 in the `Handling Death Data` section.
Simplified the first paragraph in the `Merging Additional ADSL Variables` section and fixed a typo.
Changed ADRS to `ADRS`.
Removed `ANL02FL` and `RSDTC` columns from the code block.
@DavidBlairs DavidBlairs marked this pull request as ready for review May 30, 2024 16:12
@DavidBlairs
Copy link
Collaborator Author

Hello @rossfarrugia. I added these amendments and did a larger rewrite to ensure ADTTE and ADRS were consistent with the ADaM guides already on the examples website. Let me know what you think.

@rossfarrugia
Copy link
Contributor

thanks @DavidBlairs - will try find time over next few weeks to take another look

Copy link
Contributor

@rossfarrugia rossfarrugia left a comment

Choose a reason for hiding this comment

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

@DavidBlairs sorry it took me so long to get back around to this. thanks for all the updates! here's some more review comments for consideration.

metadata/adam_spec.xlsx Outdated Show resolved Hide resolved
adam/adrs.qmd Outdated Show resolved Hide resolved
adam/adam_spec.xlsx Outdated Show resolved Hide resolved
adam/adrs.qmd Show resolved Hide resolved
adam/adtte.qmd Outdated Show resolved Hide resolved
adam/adtte.qmd Outdated Show resolved Hide resolved
adam/adtte.qmd Show resolved Hide resolved
adam/adtte.qmd Outdated Show resolved Hide resolved
adam/adtte.qmd Outdated Show resolved Hide resolved
adam/adtte.qmd Outdated Show resolved Hide resolved
f-meister and others added 10 commits October 1, 2024 17:45
Also remove namespace resolution
Co-authored-by: Ross Farrugia <82581364+rossfarrugia@users.noreply.github.com>
Co-authored-by: Ross Farrugia <82581364+rossfarrugia@users.noreply.github.com>
Co-authored-by: Ross Farrugia <82581364+rossfarrugia@users.noreply.github.com>
Co-authored-by: Ross Farrugia <82581364+rossfarrugia@users.noreply.github.com>
Co-authored-by: Ross Farrugia <82581364+rossfarrugia@users.noreply.github.com>
Co-authored-by: Ross Farrugia <82581364+rossfarrugia@users.noreply.github.com>
Co-authored-by: Ross Farrugia <82581364+rossfarrugia@users.noreply.github.com>
@f-meister
Copy link
Contributor

Hello @rossfarrugia I've made the changes you suggested and fixed up some issues with the spec. When you have the time, please go through these changes and let me know if I got the assignment right 😃

@rossfarrugia
Copy link
Contributor

@f-meister one more thing needed is to follow this guidance from the README: https://github.com/pharmaverse/examples#scripts. Once you've done that and made the minor update requested above then i'm going to merge this and if anything else needs fixing i can take it. The CI fail is not related to your examples, so might have to dig into that one if it breaks when in main. I'm wondering if for some reason it's because this one is forked from our repo.

@rossfarrugia rossfarrugia merged commit 939eda3 into pharmaverse:main Oct 7, 2024
2 checks passed
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.

Add Onco ADaM examples using {admiralonco}
3 participants