-
Notifications
You must be signed in to change notification settings - Fork 4
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 #244: introduction of derive_vars_cat() #252
Closes #244: introduction of derive_vars_cat() #252
Conversation
…placing look-up table with derive_vars_merged() feat: #247 Used call_derivation with derive_vars_crit_flag() to generate CRITy conditions and CRITyFL flags, superseding derive_var_bcvacritxfl()
@steventing12 quoting your comment from the issue just so it's in the MR: Used derive_vars_cat() to derive AVALCA1N and AVALCAT1, replacing look-up table with derive_vars_merged(). However, the input expression is still duplicating conditions for SBCVA and FBCVA as a combining expressions doesn't yield the same structure. |
@steventing12 after reviewing and playing around, I agree that it's too complicated to programmatically duplicate the SBCVA rows to generate the FBCVA rows. Even if we managed to do it, the program would be unreadable. As such please could you go ahead with implementing the update using a simple lookup "table" like this one:
maybe with a comment above it explaining this could also be moved to a separate file if so desired? Please could you also reset the ADBCVA template to the current version in Once the template is updated, please also update the ADBCVA vignette. |
@steventing12 i forgot to mention - please ensure all checks pass and let me know of any queries. The PR checklist at the top of the page should be a good guide, and will for instance guide you on other tasks to execute like updating NEWS.md. |
feat: #247 Used call_derivation with derive_vars_crit_flag() to generate CRITy conditions and CRITyFL flags, superseding derive_var_bcvacritxfl()
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 family 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.styler::style_file()
to style R and Rmd files.devtools::document()
so all.Rd
files in theman
folder and theNAMESPACE
file in the project root are updated appropriately.NEWS.md
under the header# admiralophtha (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()
.