We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would aid with identifying runs. For example,
a AB_CDE.fastq will generate something like AB_CDE-2019-02-26T12-34-56UTC, instead of or in addition to resultDocument....
AB_CDE.fastq
AB_CDE-2019-02-26T12-34-56UTC
resultDocument...
and a folder upload with multiple .fastq, if it's possible to detect this, be named with the folder's name.
.fastq
Maybe the timestamp can be less verbose if we use the input names as identifiers.
This would also help with generating more intuitive URLs in #57.
The text was updated successfully, but these errors were encountered:
Added in #96 . Now we have functionality of grouping results by source folder of GCS bucket. For example, if you add next fastq files
gs://test_bucket/folder_1/1.fastq gs://test_bucket/folder_1/2.fastq gs://test_bucket/folder_2/3.fastq gs://test_bucket/folder_2/4.fastq
you will have two result documents, for folder_1 and folder_2
folder_1
folder_2
Sorry, something went wrong.
No branches or pull requests
Would aid with identifying runs. For example,
a
AB_CDE.fastq
will generate something likeAB_CDE-2019-02-26T12-34-56UTC
, instead of or in addition toresultDocument...
.and a folder upload with multiple
.fastq
, if it's possible to detect this, be named with the folder's name.Maybe the timestamp can be less verbose if we use the input names as identifiers.
This would also help with generating more intuitive URLs in #57.
The text was updated successfully, but these errors were encountered: