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
Selecting all 0 accession_ids.
Error in read.table(file = file, header = header, sep = sep, quote = quote, :
no lines available in input
I have a script that queries many lineages in a for loop. If one lineage hits an error it stops the loop. Current solution, which might be the best solution is:
Another odd side effect is that queries that are zero force reauthenticate:
> query(
+ credentials = credentials,
+ lineage = "JN.1.1.2",
+ location = 'Australia',
+ fast = TRUE
+ )
Selecting all 0 accession_ids.
Error in read.table(file = file, header = header, sep = sep, quote = quote, :
no lines available in input
> query(
+ credentials = credentials,
+ lineage = "JN.1.1.2",
+ location = 'Australia',
+ fast = TRUE
+ )
Selecting all 0 accession_ids.
Error in parseResponse(response) : Error! Please login again.
Very strange. Could it be another anti-bioinformatician measures?
Posting the solution if others run into this problem.
The text was updated successfully, but these errors were encountered:
ammaraziz
changed the title
Catch and continue if zero ids are return from query
Error is prodcued if zero ids are returne from query and reauthentication is required
Feb 1, 2024
Thanks @ammaraziz! This is related to the fast = TRUE query. When get_accession_ids fails (tries to read empty CSV of ids) the function exits and back cmd isn't sent (hence needing to log in again).
If the query returns zero ids,
gisaidr::query
errors:Output:
I have a script that queries many lineages in a for loop. If one lineage hits an error it stops the loop. Current solution, which might be the best solution is:
Another odd side effect is that queries that are zero force reauthenticate:
Very strange. Could it be another anti-bioinformatician measures?
Posting the solution if others run into this problem.
The text was updated successfully, but these errors were encountered: