[ ] more unit tests for refactored code: writing unit test codes
[ ] passing R CMD CHECK --as-cran
[ ] Check DESCRIPTION
From CRAN checklist
The most important way to do this is to write an informative entry in the Description field in the DESCRIPTION file (see the relevant section of the [Writing R Extensions](https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#The-DESCRIPTION-file) manual). The Title and Description fields are shown at the top of the CRAN landing page for the package, and should therefore be written with care.
Make the Description as informative as possible for potential new users of your package. If in doubt, make the Description longer rather than shorter, but try to avoid redundancies such as repetitions of the package name.
Write function names including parentheses as in foo() but without quotes.
Put non-English usage, including names of other packages and external software, in single quotes. Example: 'OpenSSL'.
Relevant citations should be included in the description. These should be in author-year style, preferably followed by an identifier such as DOI, arXiv id, or ISBN for published materials.
DOIs should be enclosed in angle brackets, and formatted as <doi:10.prefix/suffix>. Example: Sugihara (1994) <doi:10.1098/rsta.1994.0106>.
arXiv identifiers should be enclosed in angle brackets, and formatted as . Example: Srivastava et al. (2011) .
Preferably, provide an Authors@R field in DESCRIPTION giving all the authors, including contributors and copyright holders, with appropriate roles. For persons with an ORCID identifier (see https://orcid.org/ for more information, provide the identifier via an element named "ORCID" in the comment argument of person(). Example: person("Achim", "Zeileis", comment = c(ORCID = "0000-0003-0918-3766")).
Road to CRAN package. See the checklist from CRAN
[x] #15 : Which is done in another project.
[ ] more unit tests for refactored code: writing unit test codes
[ ] passing
R CMD CHECK --as-cran[ ] Check
DESCRIPTIONFrom CRAN checklist
The most important way to do this is to write an informative entry in the Description field in the DESCRIPTION file (see the relevant section of the [Writing R Extensions](https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#The-DESCRIPTION-file) manual). The Title and Description fields are shown at the top of the CRAN landing page for the package, and should therefore be written with care.Make the Description as informative as possible for potential new users of your package. If in doubt, make the Description longer rather than shorter, but try to avoid redundancies such as repetitions of the package name.
Write function names including parentheses as in foo() but without quotes.
Put non-English usage, including names of other packages and external software, in single quotes. Example: 'OpenSSL'.
Relevant citations should be included in the description. These should be in author-year style, preferably followed by an identifier such as DOI, arXiv id, or ISBN for published materials.
DOIs should be enclosed in angle brackets, and formatted as <doi:10.prefix/suffix>. Example: Sugihara (1994) <doi:10.1098/rsta.1994.0106>.
arXiv identifiers should be enclosed in angle brackets, and formatted as. Example: Srivastava et al. (2011) .
Similarly, relevant URLs should be included in the description, also enclosed in angle brackets (see the Writing R Extensions manual for details). Example: https://cran.r-project.org/.
Preferably, provide an Authors@R field in DESCRIPTION giving all the authors, including contributors and copyright holders, with appropriate roles. For persons with an ORCID identifier (see https://orcid.org/ for more information, provide the identifier via an element named "ORCID" in the comment argument of person(). Example: person("Achim", "Zeileis", comment = c(ORCID = "0000-0003-0918-3766")).