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
Use datasets to download a summary of any number of given genomes
Use dataformat to output a tsv file for genome information, specifically declaring the field assminfo-biosample-strain
Direct the output to a tsv file
Open the tsv file, go to the column named "Assembly BioSample Strain", double-click and use Ctrl + A to see the extra white space proceeding the word "Strain"
Expected behavior
It was expected to be a string with no extra white space at the end like so: "Assembly BioSample Strain"
What is instead occurring is the following: "Assembly BioSample Strain ".
I'm not sure if the way I'm providing arguments is the issue, but I just updated to 16.24.0 and it is still present in this column. As far as I'm aware, though I've not exhaustively checked, I've had no other issue with other column names.
Thank you!
The text was updated successfully, but these errors were encountered:
Describe the bug
Downloading genome information on the Assembly BioSample Strain yields a column name containing an extra whitespace
To Reproduce
datasets summary genome accession GCF_000196515.1 --as-json-lines --assembly-level complete --assembly-source RefSeq | dataformat tsv genome --fields assminfo-biosample-strain > my_report.tsv
Steps to reproduce the behavior:
datasets
to download a summary of any number of given genomesdataformat
to output a tsv file for genome information, specifically declaring the fieldassminfo-biosample-strain
Ctrl + A
to see the extra white space proceeding the word "Strain"Expected behavior
It was expected to be a string with no extra white space at the end like so: "Assembly BioSample Strain"
What is instead occurring is the following: "Assembly BioSample Strain ".
I'm not sure if the way I'm providing arguments is the issue, but I just updated to 16.24.0 and it is still present in this column. As far as I'm aware, though I've not exhaustively checked, I've had no other issue with other column names.
Thank you!
The text was updated successfully, but these errors were encountered: