rsnps
rsnps copied to clipboard
ropensci
Wrapper to a number of SNP web APIs
Hi, thanks for developing rsnps. I just started using the package, but I notice that the documentation of `ncbi_snp_query` says that the function adds 1 to the positions of SNVs...
Prepare for release (working on dev branch): * [x] `git pull` * [x] Check [current CRAN check results](https://cran.rstudio.org/web/checks/check_results_rsnps.html) * [x] [Polish NEWS](https://style.tidyverse.org/news.html#news-release) - add in issue numbers * [x] `devtools::build_readme()`...
`{rsnps}` CRAN's page now reads > Archived on 2023-07-09 for policy violation. What happened?
## Description Split in two with if the function get_placement() to obtain the result from the json related with the version choose. Create a new function called get_placement_inside() with the...
As brought up in #92. It would be nice to add support for reporting the hg19/37 position (if available) in ncbi_snp_query_api().
The function `ld_search()` was retired following issue #53 (the API was down). Now the server seems up and running again: https://data.broadinstitute.org/mpg/snpsnap/match_snps.html
The function `ncbi_snp_query(snp)` takes SNPs as input and outputs chromosome, position and other annotation for each SNP. Idea: reverse inputs. Have chromosome and position as input and output SNP identifier...
As brought up in #92 this should be checked. Does what we report in ncbi_snp_query_api() match what is reported in https://www.ncbi.nlm.nih.gov/snp/?
As suggested by @sinarueeger in #92. If the user submits a large number of rsids, "we could print a message saying that passing on 100 SNPs will take > 100...
*Problem*: Often, the documentation of the function misses or has a too general description of `@value`. *Example*: `?rsnps::annotations` just mentions `Value: data.frame of results` (independent of the four output options)....