Releases: Kimitsuna-Goblin/GGD
v1.0.4
Updated manuals.
- Description about 'kind' is now consolidated in 'Fields' at 'GGD-class'.
- Tables are now adopted to explain 'mix.type' and 'kind'.
- Single quotation marks were replaced to \sQuote.
- Added link from '==' operator to base::Comparison.
- Corrected some words and phrases.
v1.0.3.1
- d(), p(), q() and r() methods now references each other at 'See also'.
- At nls.freq manual, description about this.kind argument is revised.
Author has not yet written a paper on this package. Therefore, the following problems still exist.
- It may be difficult to prove publicly that the calculations in this package are correct using other sources (even there are computational assurances with tests/testthat/test.integ.R).
- Most people will not know what this package is useful for.
For this reason, although cran-comments.md has been added (with some notes by devtools::check_rhub()), this package has not been posted to CRAN yet.
v1.0.3
- Fixed issues
- Fixed a minor bug
- If mix.type contains an illegal value, two or more errors could occur at once in p() method depending on the environment.
- Brushed up all manuals and comments
- Simplified and corrected a lot of sentences.
- Fixed spells and sentences.
- Quotes were maintained.
- Descriptions of samples are improved.
- Samples of nls.freq() and trace.q() were made faster to run.
- All source files are now 96 characters or less per line.
- Renamed arguments
- At ggd.start.template(), target was renamed to kind.
- At calc.v() (non-exported), k was renamed to i.
- At v2.qt4.cmp() (non-exported), retriable was renamed to retryable.
- Renamed a function
- separate.data.quarter() (non-exported) was renamed to divide.data.quarter().
- Changed a function location
- dp.t3() (non-exported) has moved from ggd.trace.R to ggd.1.R.
- Code improvement
- base::on.exit() is now used to clear the object on error.
Author has not yet written a paper on this package. Therefore, the following problems still exist.
- It may be difficult to prove publicly that the calculations in this package are correct using other sources (even there are computational assurances with tests/testthat/test.integ.R).
- Most people will not know what this package is useful for.
For this reason, although cran-comments.md has been added (with some notes by devtools::check_rhub()), this package has not been posted to CRAN yet.
v1.0.2
- Simplified some titles of the manuals.
- Updated some phrases in the manuals and error messages.
- In is.hv() method, if conditions with the same contents were judged twice. Therefore, they were simplified to once.
- In a non-exported function get.nls.params(), a vector "sqrt.md.mid" has been renamed to "sqrt.sds.mid".
- Added cran-comments.md to the branch.
Author has not yet written a paper on this package. Therefore, the following problems still exist.
- It may be difficult to prove publicly that the calculations in this package are correct using other sources (even there are computational assurances with tests/testthat/test.integ.R).
- Most people will not know what this package is useful for.
For this reason, although cran-comments.md has been added (with some notes by devtools::check_rhub()), this package has not been posted to CRAN yet.
v1.0.1
- README and manuals are updated to make definitions and other descriptions of GGD clearer.
Author has not yet written a paper on this package. Therefore, the following problems still exist.
- It may be difficult to prove publicly that the calculations in this package are correct using other sources (even there are computational assurances with tests/testthat/test.integ.R).
- Most people will not know what this package is useful for.
For this reason, this package has not been posted to CRAN yet, although it can pass devtools::check_rhub() with some notes.
A new release
This is a new release.
This package passes devtools::check_rhub() (with 4 NOTEs) but has not yet posted to CRAN with devtools::release().
The reasons are as follows.
- Author wanted to release this package somehow within 2023, but it was not until December 30, 2023 that it finally reached a level where it could be submitted to CRAN. If we wait for CRAN to review it, we will not be able to release it until 2024.
- Author has not yet written a paper on this package. Therefore, the following problems still exist.
- It may be impossible to prove publicly that the calculations in this package are correct using other sources (even there are computational assurances with tests/testthat/test.integ.R).
- Most people will not know what this package is useful for.