You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
id = c('P00750', 'P00751', 'P00752')
getFASTAFromUniProt(id)
#gives "" "" ""
from R documentations of getFASTAFromUniProt does not run properly. the second line gives an empty character string, which will result in errors in other functions dependent on getFASTAFromUniProt such as getSeqFromUniProt.
Also,
id = c('P00750', 'P00751', 'P00752')
getSeqFromUniProt(id)
#ERROR
leads to error.
(Error in FUN(X[[i]], ...) : no line starting with a > character found)
which is obviously resulted from problems in getFASTAFromUniProt.
It seems that getURLAsynchronous in the implementation of getFASTAFromUniProt is causing the problem somehow. It's better to replace it with some equivalent base-R function.
The text was updated successfully, but these errors were encountered:
I'm having the same issue with getSeqFromUniProt. I believe the URL has changed on uniprot's end. In the getFASTAFromUniProt function getURLAsynchronous is directed to a website. However I think that has recently been updated to, "https://https://rest.uniprot.org/uniprotkb/", id, ".fasta"
I've fixed the issue in this repo - you can try it with remotes::install_github("nanxstats/Rcpi").
I also submitted the updated version v1.33.2 (devel) and v1.32.2 (release) to Bioconductor. It may take a few days to fully propagate through their build system.
from R documentations of getFASTAFromUniProt does not run properly. the second line gives an empty character string, which will result in errors in other functions dependent on getFASTAFromUniProt such as getSeqFromUniProt.
Also,
leads to error.
which is obviously resulted from problems in getFASTAFromUniProt.
It seems that getURLAsynchronous in the implementation of getFASTAFromUniProt is causing the problem somehow. It's better to replace it with some equivalent base-R function.
The text was updated successfully, but these errors were encountered: