-
Notifications
You must be signed in to change notification settings - Fork 69
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 #2138 Implement derive_vars_extreme_event() #2236
Conversation
@bundfussr I'm not sure if this is exactly what you had in mind, but it seemed like the best option was to create a new helper function |
Sounds good to me. I'll have a closer look later today or on Monday. |
I think if you add pharmaversesdtm to the Remotes you can get the new changes there so the R-CMD checks pass again? @ddsjoberg correct? You might need to change the Imports to the specific version - new territory for me as well!! |
@bms63 which R CMD Check error are you trying to solve with the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Please update the ADSL vignette and template.
- Please supersede
dthcaus_source
anddate_source
.
My understanding is this is related to a recent update in pharmaversesdtm |
Unfortunately, the development version is broken at the moment. We need to merge pharmaverse/pharmaversesdtm#78 and #2241 to fix it. |
Hi all - hope you don't mind me removing myself from review of this as I won't have time to do a thorough review - please feel free to ask someone else if required. |
R/derive_extreme_event.R
Outdated
#' mode = "first", | ||
#' new_vars = exprs(DTHCAUS = DTHCAUS, DTHDT = DTHDT) | ||
#' ) | ||
derive_vars_extreme_event <- function(dataset, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we still split this function out into a new file out so it is easy to find in the R folder. I think the events stuff should also get put into a new file, but understand if that is overkill and others don't want to split out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bms63 Ok, I split into three files.
Superseded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost done. Just one comment left.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your patience.
Thanks! I thought of one more thing: I could remove |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy! @jeffreyad @bundfussr shall we click the button!!??!!
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
devel
branch until you have checked off each task.styler::style_file()
to style R and Rmd filesdevtools::document()
so all.Rd
files in theman
folder and theNAMESPACE
file in the project root are updated appropriatelyNEWS.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)pkgdown::build_site()
and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.lintr::lint_package()
R CMD check
locally and address all errors and warnings -devtools::check()