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
I ran across an issue using classification() in R markdown when multiple UIDs are found or a taxon. In my example, three UIDs are found for the taxon 'Ctenophora' and I am asked to enter the row number of the taxon I wish to choose. However, in R markdown the list of options do not show in the Console, so I unable to assess which is most appropriate. If I run the exact same code in a regular R script file the options do show up. Has this happened with others?
Code run:
classification(spnames, db = "ncbi", verbose = FALSE)
##########
Console output when run in R markdown:
Retrieving data for taxon 'Ctenophora'
More than one UID found for taxon 'Ctenophora'!
Enter rownumber of taxon (other inputs will return 'NA'):
1:
##########
Console output when run in a plain R script:
Retrieving data for taxon 'Ctenophora'
More than one UID found for taxon 'Ctenophora'!
Enter rownumber of taxon (other inputs will return 'NA'):
status rank division scientificname commonname uid genus species subsp modificationdate
1 active genus diatoms Ctenophora 1003038 2015/09/16 00:00
2 active genus flies Ctenophora 516519 2016/03/23 00:00
3 active phylum comb jellies Ctenophora ctenophores 10197 2017/06/14 00:00
1:
Hello,
I ran across an issue using classification() in R markdown when multiple UIDs are found or a taxon. In my example, three UIDs are found for the taxon 'Ctenophora' and I am asked to enter the row number of the taxon I wish to choose. However, in R markdown the list of options do not show in the Console, so I unable to assess which is most appropriate. If I run the exact same code in a regular R script file the options do show up. Has this happened with others?
Code run:
##########
Console output when run in R markdown:
##########
Console output when run in a plain R script:
Session Info
The text was updated successfully, but these errors were encountered: