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
When testing the Taxonomy.pm module using Taxonomy.t, recently been getting alot of errors like below (stemming from gi2taxid and taxid2lineage methods). I thought the Bioperl module has a built in delay so that it doesn't send too many requests.
Here is the respone from NLM Support case #CAS-630050-S2L8Q7: RE: too many requests error using eutilities TRACKING:000349000000978 (Nov 9 2020)
Dear Colleague,
Bioperl is crowd sourced and not review/approved/maintained by NCBI, so I cannot explicitly answer this. It is possible the built in waits are set for 101 milliseconds, assuming the user has an API key, which would fail if you do not supply an API key, as the rate drops to three requests per second rather than ten when you have an API key.
So, I would not make the above assumption, and simply institute your own wait statements using standard Perl methods within your loops. If you have questions about the built in timer to Bioperl, I would post a comment to the github site, rather than writing to the help desk.
When testing the Taxonomy.pm module using Taxonomy.t, recently been getting alot of errors like below (stemming from gi2taxid and taxid2lineage methods). I thought the Bioperl module has a built in delay so that it doesn't send too many requests.
and
The text was updated successfully, but these errors were encountered: