0015 derive seq

[ramiromagno]

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 oak 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.

• [x] Place Closes # into the beginning of your Pull z Request Title (Use Edit button in top-right if you need to update)
• [x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
• [x] 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
• [x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
• [x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
• [x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
• [x] Address any updates needed for vignettes and/or templates
• [x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
• [x] Build oak site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
• [x] Address or fix all lintr warnings and errors - lintr::lint_package()
• [x] Run R CMD check locally and address all errors and warnings - devtools::check()
• [x] Link the issue in the Development Section on the right hand side.
• [x] Address all merge conflicts and resolve appropriately
• [x] Pat yourself on the back for a job well done! Much love to your accomplishment!

[ramiromagno]

@edgar-manukyan: As discussed today, I will wait for those examples for inclusion in the Examples section of the docs and to create unit tests. Many thanks!

[github-actions[bot]]

Package	Line Rate	Health
sdtm.oak	68%	➖
Summary	68% (498 / 734)	➖

[rammprasad]

@edgar-manukyan - Ready for your review.

[ramiromagno]

Thanks so much Ramiro, looks fine to me. Just left two comments in case you want to address them. Are we going to add tests at some point?

I am happy to write the unit tests, but could you provide some input and output examples such that the tests are based on realistic examples, and also cover corner cases. (you guys have more experience here).

[edgar-manukyan]

Thanks so much Ramiro, looks fine to me. Just left two comments in case you want to address them. Are we going to add tests at some point?

I am happy to write the unit tests, but could you provide some input and output examples such that the tests are based on realistic examples, and also cover corner cases. (you guys have more experience here).

Ram mentioned that we can have a separate issue to increase the coverage, no worries Ramiro. Thanks so much for your brilliant work 💠 💠 💠