-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sasquatch
: Use SAS, R, and Quarto together
#673
Comments
Thanks for submitting to rOpenSci, our editors and @ropensci-review-bot will reply soon. Type |
🚀 Editor check started 👋 |
Checks for sasquatch (v0.0.0.9004)git hash: 8353d8ac
Important: All failing checks above must be addressed prior to proceeding Package License: MIT + file LICENSE 1. Package DependenciesDetails of Package Dependency Usage (click to open)
The table below tallies all function calls to all packages ('ncalls'), both internal (r-base + recommended, along with the package itself), and external (imported and suggested packages). 'NA' values indicate packages to which no identified calls to R functions could be found. Note that these results are generated by an automated code-tagging system which may not be entirely accurate.
Click below for tallies of functions used in each package. Locations of each call within this package may be generated locally by running 's <- pkgstats::pkgstats(<path/to/repo>)', and examining the 'external_calls' table. sasquatchread_file (2), rstudio_context (2), sas_engine (2), check_connection (1), newline (1), r_to_sas (1), rstudio_selection (1), rstudio_text_tidy (1), sas_connect (1), sas_disconnect (1), sas_download (1), sas_get_session (1), sas_list (1), sas_remove (1), sas_run_file (1), sas_run_selected (1), sas_run_string (1), sas_to_r (1), sas_upload (1), sas_use_quarto (1), wrap_in_iframe (1), wrap_in_pre (1) baselist (2), log (2), system.file (2), length (1), options (1), paste (1), paste0 (1) graphicstext (1) htmlwidgetssizingPolicy (1) knitrknit_engines$set (1) reticulateimport (1) rstudioapiprimary_selection (1) 2. Statistical PropertiesThis package features some noteworthy statistical properties which may need to be clarified by a handling editor prior to progressing. Details of statistical properties (click to open)
The package has:
Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages
All parameters are explained as tooltips in the locally-rendered HTML version of this report generated by the The final measure (
2a. Network visualisationClick to see the interactive network visualisation of calls between objects in package 3.
|
id | name | conclusion | sha | run_number | date |
---|---|---|---|---|---|
11900852065 | pages build and deployment | success | fbd7ec | 29 | 2024-11-18 |
11900828295 | pkgdown.yaml | success | 8353d8 | 29 | 2024-11-18 |
11900828308 | R-CMD-check.yaml | success | 8353d8 | 12 | 2024-11-18 |
11900828293 | test-coverage.yaml | success | 8353d8 | 12 | 2024-11-18 |
3b. goodpractice
results
R CMD check
with rcmdcheck
R CMD check generated the following error:
- checking tests ...
Running ‘testthat.R’
ERROR
Running the tests in ‘tests/testthat.R’ failed.
Last 13 lines of output:
5. └─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-run.R:18:3'): Run SAS code from file ───────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment withreticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆- └─sasquatch::sas_connect() at test-run.R:18:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
[ FAIL 12 | WARN 0 | SKIP 0 | PASS 14 ]
Error: Test failures
Execution halted
R CMD check generated the following test_fail:
-
This file is part of the standard setup for testthat.
It is recommended that you do not modify it.
Where should you do additional test configuration?
Learn more about the roles of various files in:
* https://r-pkgs.org/testing-design.html#sec-tests-files-overview
* https://testthat.r-lib.org/articles/special-files.html
library(testthat)
library(sasquatch)test_check("sasquatch")
[ FAIL 12 | WARN 0 | SKIP 0 | PASS 14 ]
══ Failed tests ════════════════════════════════════════════════════════════════
── Failure ('test-connection.R:2:3'): test connection ──────────────────────────
Expected sas_connect()
to run without any errors.
i Actually got a with text:
Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
── Failure ('test-connection.R:4:3'): test connection ──────────────────────────
Expected sas_connect("oda")
to run without any errors.
i Actually got a with text:
Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
── Failure ('test-connection.R:6:3'): test connection ──────────────────────────
Expected sas_get_session()
to run without any errors.
i Actually got a with text:
No current SAS session. Use sas_connect() to start one.
── Failure ('test-connection.R:8:3'): test connection ──────────────────────────
Expected sas_disconnect()
to run without any errors.
i Actually got a with text:
No current SAS session. Use sas_connect() to start one.
── Error ('test-conversion.R:2:3'): SAS to R data.frame ────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-conversion.R:2:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-conversion.R:24:3'): R to SAS data.frame ───────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-conversion.R:24:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-io.R:12:3'): uploading files to SAS ────────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-io.R:12:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-io.R:34:3'): download files from SAS ───────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-io.R:34:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-io.R:61:3'): removing files from SAS ───────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-io.R:61:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-io.R:85:3'): listing files ─────────────────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-io.R:85:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-run.R:4:3'): Run SAS code from string ──────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-run.R:4:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
── Error ('test-run.R:18:3'): Run SAS code from file ───────────────────────────
Error: Python shared library not found, Python bindings not loaded.
Please create a default virtual environment with reticulate::virtualenv_create('r-reticulate')
.
Backtrace:
▆
- └─sasquatch::sas_connect() at test-run.R:18:3
- └─reticulate::py_capture_output(.pkgenv$session <- .pkgenv$SASPy$SASsession())
-
└─reticulate:::ensure_python_initialized()
-
└─reticulate:::initialize_python()
-
└─reticulate (local) python_not_found("Python shared library not found, Python bindings not loaded.")
[ FAIL 12 | WARN 0 | SKIP 0 | PASS 14 ]
Error: Test failures
Execution halted
R CMD check generated the following check_fail:
- rcmdcheck_tests_pass
Test coverage with covr
ERROR: Test Coverage Failed
Cyclocomplexity with cyclocomp
No functions have cyclocomplexity >= 15
Static code analyses with lintr
lintr found no issues with this package!
Package Versions
package | version |
---|---|
pkgstats | 0.2.0.48 |
pkgcheck | 0.1.2.68 |
Editor-in-Chief Instructions:
Processing may not proceed until the items marked with ✖️ have been resolved.
Submitting Author Name: Ryan Zomorrodi
Submitting Author Github Handle: @ryanzomorrodi
Other Package Authors Github handles: (comma separated, delete if none)
Repository: https://github.com/ryanzomorrodi/sasquatch
Version submitted: 0.0.0.9004
Submission type: Standard
Editor: TBD
Reviewers: TBD
Archive: TBD
Version accepted: TBD
Language: en
Scope
Please indicate which category or categories from our package fit policies this package falls under: (Please check an appropriate box below. If you are unsure, we suggest you make a pre-submission inquiry.):
Explain how and why the package falls under these categories (briefly, 1-2 sentences):
sasquatch
allows users to create remote SAS sessions, work with them interactively, pass tables between R and SAS, and render quarto documents.The target audience would be anyone looking to combine SAS in R within a single workflow. Using quarto, analysts can have one single reproducable report that combines SAS and R (and python potentially).
saquatch
works similarly to packages likesasr
orconfigSAS
.sasr
, while similar tosasquatch
, does not include interactive SAS functionality or aknitr
engine. On the other hand,configSAS
includes aknitr
engine, but no interactive SAS functionality.configSAS
knitr
output also does not include syntax highlighting and nested SAS output interferes with the styles of the rest of the document.N/A
If you made a pre-submission inquiry, please paste the link to the corresponding issue, forum post, or other discussion, or @tag the editor you contacted.
Explain reasons for any
pkgcheck
items which your package is unable to pass.Locally,
pkgcheck
is able to pass all tests except coverage. I do not currently have any coverage over theknitr
engine because I am struggling to think about how I can test that effectively. My assumption that the automatedpkgcheck
testing will fail due to the need forpython
, python packageSASPy
,java
, and a SAS License. (I have set up a CI that has all of these set up within thesasquatch
repo).Technical checks
Confirm each of the following by checking the box.
This package:
Publication options
Do you intend for this package to go on CRAN?
Do you intend for this package to go on Bioconductor?
Do you wish to submit an Applications Article about your package to Methods in Ecology and Evolution? If so:
MEE Options
Code of conduct
The text was updated successfully, but these errors were encountered: