wolfylair
wolfylair
Same issue here. I suspect Uniprot is changing its API again. Is there any way to apply local database so we may get around of the issue?
Thanks! Is there any chance to resume the normal use of PhylostratR in this situation? It'll be great if there is another port for the package to link with Uniprot....
Did you check the path for every entry? Please make sure your file 'Araport11_genes.201606.pep.fasta' and the folder 'blastdb' is both in your working directory. What the code does is literally...