Skip to content

Draft: Closes #2952 tte: add end_dates and event_type argument to derive_param_tte() [create website]#2988

Draft
bundfussr wants to merge 13 commits intomainfrom
2952_tte
Draft

Draft: Closes #2952 tte: add end_dates and event_type argument to derive_param_tte() [create website]#2988
bundfussr wants to merge 13 commits intomainfrom
2952_tte

Conversation

@bundfussr
Copy link
Collaborator

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.

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)
  • Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
  • Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
  • If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
  • Review the Cheat Sheet. Make any required updates to it by editing the file inst/cheatsheet/admiral_cheatsheet.pptx and re-upload a PDF and a PNG version of it to the same folder. (The PNG version can be created by taking a screenshot of the PDF version.)
  • Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
  • Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
  • Address any updates needed for vignettes and/or templates
  • Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers). A Developer Notes section is available in NEWS.md for tracking developer-facing issues.
  • Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
  • Address or fix all lintr warnings and errors - lintr::lint_package()
  • Run R CMD check locally and address all errors and warnings - devtools::check()
  • Link the issue in the Development Section on the right hand side.
  • Address all merge conflicts and resolve appropriately
  • Pat yourself on the back for a job well done! Much love to your accomplishment!

To create the website for the content of this PR add "[create website]" to the title of the pull request.

@bundfussr bundfussr changed the title Closes #2952 tte: add end_dates and event_type argument to derive_param_tte() Draft: Closes #2952 tte: add end_dates and event_type argument to derive_param_tte() Feb 24, 2026
@bundfussr bundfussr marked this pull request as draft February 24, 2026 16:26
@bundfussr bundfussr changed the title Draft: Closes #2952 tte: add end_dates and event_type argument to derive_param_tte() Draft: Closes #2952 tte: add end_dates and event_type argument to derive_param_tte() [create website] Feb 24, 2026
@github-actions
Copy link

github-actions bot commented Feb 24, 2026

Code Coverage

Package Line Rate Health
admiral 100%
Summary 100% (6176 / 6189)

@github-actions
Copy link

The website/documentation is availables at https://pharmaverse.github.io/admiral/2952_tte.

#' )
#' )
#'
#' worsening <- event_source(
Copy link
Collaborator

Choose a reason for hiding this comment

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

should we add a comment here noting the use of event_source() rather than censor_source()?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm not sure. Isn't it clear from using event_source() that an event is defined here?

Copy link
Collaborator

Choose a reason for hiding this comment

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

i think it could be handy to have a small comment to user saying this source has changed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

What do you mean by "this source has changed"?

Copy link
Collaborator

Choose a reason for hiding this comment

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

like it went from event_source to censor_source. just wondering if we should highlight to user or if my dusty old eyes just didn't notice until i did another read through :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Could you make a suggestion?

#' dataset_name = "adsl",
#' date = TRTSDT,
#' censor = 3,
#' consider_end_dates = FALSE,
Copy link
Collaborator

Choose a reason for hiding this comment

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

ooohhh a new argument for the programming strategy!?!

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think it is unlikely that we will use it somewhere else. Thus I wouldn't add it to the programming strategy.

Copy link
Collaborator

Choose a reason for hiding this comment

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

roger roger

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.

2 participants