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
Thanks for bringing this up... it's setup to potentially treat many files as one table (e.g. a directory of FASTAs), which is why if you're not using .fasta it needs to be specified. But you're right that can/should be improved to automatically detect in the single file case.
I'll look into it this afternoon and try to resolve at least for FASTA files (along w/ compression).
This should work now[1] for FASTA and FASTQ, except for the last one example in that if the user explicitly passes an option for which extension to use biobear will respect that. I've made #154 to continue to make file path options inferable ordered in rough priority. If there's a particular one you're interested in, happy to do that first. Thanks again for raising this!
Why is specifying the extension required when reading files?
When the wrong one is specified, an empty dataframe is returned.
It would be nice if the extension and compression would be automatically be detected by checking the extension(s) if not explicitly set.
Also at the moment:
fasta_sequence_data_type
option can't be set asFastaSequenceDataType
is not exposed.The text was updated successfully, but these errors were encountered: