Skip to content

Commit f563137

Browse files
committed
Update cran-comments
1 parent 3d69008 commit f563137

File tree

3 files changed

+13
-22
lines changed

3 files changed

+13
-22
lines changed

CRAN-SUBMISSION

Lines changed: 0 additions & 3 deletions
This file was deleted.

cran-comments.Rmd

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,11 @@ title: "cran-comments"
33
output: github_document
44
---
55

6+
## Resubmission 5 to CRAN
7+
8+
* Repairs a broken link in `vignettes/mainfunctions.Rmd`
9+
10+
611
## Resubmission 4 to CRAN
712

813
* Wrap example section of `predict()` and `brokenstick()` in `\donttest{}` to reduce CPU time
@@ -48,7 +53,7 @@ Status: OK
4853
`devtools::check_win_devel()` resulted in:
4954

5055
```
51-
Note: CPU time > 10s for predict example section
56+
OK
5257
```
5358

5459
### RHUB
@@ -60,16 +65,9 @@ rhub::check_for_cran()
6065
`rhub::check_for_cran()` produces "SUCCESS" (three times) and one note:
6166

6267
```
63-
* checking examples ... NOTE
64-
Examples with CPU (user + system) or elapsed time > 5s
65-
user system elapsed
66-
predict 7.44 0.02 7.48
67-
brokenstick 4.96 0.02 5.15
68+
Success
6869
```
6970

70-
Comment:
71-
Slightly above the threshold of 5 seconds. Both example sections demonstrate many capabilities of these functions to the end user. For clarity, I think these examples should remain as they are.
72-
7371

7472
## Downstream dependencies
7573

cran-comments.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11
cran-comments
22
================
33

4+
## Resubmission 5 to CRAN
5+
6+
- Repairs a broken link in `vignettes/mainfunctions.Rmd`
7+
48
## Resubmission 4 to CRAN
59

610
- Wrap example section of `predict()` and `brokenstick()` in
@@ -49,7 +53,7 @@ Status: OK
4953

5054
`devtools::check_win_devel()` resulted in:
5155

52-
Note: CPU time > 10s for predict example section
56+
OK
5357

5458
### RHUB
5559

@@ -59,15 +63,7 @@ rhub::check_for_cran()
5963

6064
`rhub::check_for_cran()` produces “SUCCESS” (three times) and one note:
6165

62-
* checking examples ... NOTE
63-
Examples with CPU (user + system) or elapsed time > 5s
64-
user system elapsed
65-
predict 7.44 0.02 7.48
66-
brokenstick 4.96 0.02 5.15
67-
68-
Comment: Slightly above the threshold of 5 seconds. Both example
69-
sections demonstrate many capabilities of these functions to the end
70-
user. For clarity, I think these examples should remain as they are.
66+
Success
7167

7268
## Downstream dependencies
7369

0 commit comments

Comments
 (0)