Closed mpadge closed 3 years ago
@ropensci-review-bot help
Hello @mpadge, here are the things you can ask me to do:
# List all available commands
@ropensci-review-bot help
# Show our Code of Conduct
@ropensci-review-bot code of conduct
# Switch to "seeking reviewers"
@ropensci-review-bot seeking reviewers
# Approve the package
@ropensci-review-bot approve
# Add a user to this issue's reviewers list
@ropensci-review-bot add xxxxx to reviewers
# Remove a user from the reviewers list
@ropensci-review-bot remove xxxxx from reviewers
# Assign a user as the editor of this submission
@ropensci-review-bot assign @username as editor
# Remove the editor assigned to this submission
@ropensci-review-bot remove editor
# Close the issue
@ropensci-review-bot approve
# Close the issue
@ropensci-review-bot out of scope
# Various package checks
@ropensci-review-bot check package
@ropensci-review-bot check package
git hash: 1e2f8c99
Important: All failing checks above must be addressed prior to proceeding
Package License: GPL-3
### Package Statistics
---
Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages
The following terminology is used:
- `loc` = "Lines of Code"
- `fn` = "function"
- `exp`/`not_exp` = exported / not exported
The final measure (`fn_call_network_size`) is the total number of calls between functions (in R), or more abstract relationships between code objects in other languages. Values are flagged as "noteworthy" when they lie in the upper or lower 5th percentile.
|measure | value| percentile|noteworthy |
|:--------------------|-----:|----------:|:----------|
|files_R | 4| 23.3| |
|files_vignettes | 0| 0.0|TRUE |
|files_tests | 2| 64.1| |
|loc_R | 10| 0.4|TRUE |
|loc_tests | 6| 4.2|TRUE |
|loc_per_fn_r | 3| 2.3|TRUE |
|loc_per_fn_r_not_exp | 3| 4.0|TRUE |
|loc_per_fn_src | 4| 1.8|TRUE |
|loc_per_fn_r | 3| 2.3|TRUE |
|loc_per_fn_r_not_exp | 3| 4.0|TRUE |
|loc_per_fn_src | 4| 1.8|TRUE |
|fn_call_network_size | 1| 0.3|TRUE |
---
click to see
This package is in the following category: Regression and Supervised Learning
Click here to view output of 'srr_report', which can be re-generated locally by running the `srr_report() function from within a local clone of the repository.
Processing may not proceed until the items marked with :heavy_multiplication_x: have been resolved.
@ropensci-review-bot goodtoreview
Thanks, about to check whether the package is review-ready
:rocket:
Note This package features some noteworthy statistical properties, as detailed in the 'details' section at the top of this issue. Reasons for the features flagged in that section as noteworthy should be clarified by a handling editor prior to progressing.
Please address the above noteworthy statistical properties prior to assigning reviewers.
:wave:
@ropensci-review-bot assign @mpadge as editor
Assigned! @mpadge is now the editor
@ropensci-review-bot add @noamross to reviewers
@noamross added to the reviewers list. Review due date is 2021-05-20. Thanks @noamross for accepting to review! Please refer to our reviewer guide.
@ropensci-review-bot help
Hello @mpadge, here are the things you can ask me to do:
# List all available commands
@ropensci-review-bot help
# Show our Code of Conduct
@ropensci-review-bot code of conduct
# Switch to "seeking reviewers"
@ropensci-review-bot seeking reviewers
# Approve the package
@ropensci-review-bot approve
# Add a user to this issue's reviewers list
@ropensci-review-bot add xxxxx to reviewers
# Remove a user from the reviewers list
@ropensci-review-bot remove xxxxx from reviewers
# Assign a user as the editor of this submission
@ropensci-review-bot assign @username as editor
# Remove the editor assigned to this submission
@ropensci-review-bot remove editor
# Close the issue
@ropensci-review-bot approve
# Close the issue
@ropensci-review-bot out of scope
# Check whether a package is good to send out to review
@ropensci-review-bot goodtoreview
@ropensci-review-bot check package
@ropensci-review-bot goodtoreview
Thanks, about to check whether the package is review-ready
:rocket:
Since the previous statistics were generated, the repository has been updated to: git hash: 77dfe392
Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages The following terminology is used:
loc
= "Lines of Code"fn
= "function"exp
/not_exp
= exported / not exportedThe final measure (fn_call_network_size
) is the total number of calls between functions (in R), or more abstract relationships between code objects in other languages. Values are flagged as "noteworthy" when they lie in the upper or lower 5th percentile.
measure | value | percentile | noteworthy |
---|---|---|---|
files_R | 4 | 23.3 | |
files_vignettes | 0 | 0.0 | TRUE |
files_tests | 2 | 64.1 | |
loc_R | 10 | 0.4 | TRUE |
loc_tests | 6 | 4.2 | TRUE |
loc_per_fn_r | 3 | 2.3 | TRUE |
loc_per_fn_r_not_exp | 3 | 4.0 | TRUE |
loc_per_fn_src | 4 | 1.8 | TRUE |
loc_per_fn_r | 3 | 2.3 | TRUE |
loc_per_fn_r_not_exp | 3 | 4.0 | TRUE |
loc_per_fn_src | 4 | 1.8 | TRUE |
fn_call_network_size | 1 | 0.3 | TRUE |
Note This package features some noteworthy statistical properties, as detailed immediately above. Reasons for the features flagged in that section as noteworthy should be clarified by a handling editor prior to progressing.
Please address the above noteworthy statistical properties prior to assigning reviewers.
:wave:
@ropensci-review-bot check package
Submitting Author: Mark Padgham (@mpadge) Repository: https://github.com/mpadge/srr-demo Version submitted: 0.0.0.9000 Editor: !--editor-->@mpadge<!--end-editor-- Reviewers: !--reviewers-list-->@noamross<!--end-reviewers-list--
Due date for @noamross: 2021-05-20Archive: TBD Version accepted: TBD
General Information
Who is the target audience and what are scientific applications of this package?
Paste your responses to our General Standard G1.1 here, describing whether your software is:
Please include hyperlinked references to all other relevant software.
(If applicable) Does your package comply with our guidance around Ethics, Data Privacy and Human Subjects Research?
Technical checks
Confirm each of the following by checking the box.
autotest
checks on the package, and ensured no tests fail.srr_stats_pre_submit()
function confirms this package may be submitted.This package:
Publication options
Code of conduct