Bug Description
Metadata Tabulate churns for extended periods of time on data with many rows/records e.g. ErrorCorrectionDetails. Resulting .qzv unapproachably long.
Steps to reproduce the behavior
Run qiime metadata tabulate on a significantly sized ErrorCorrectionDetails .qza
Wait for the heat death of the universe
Get nothing
Expected behavior
Let the user know what they're about to do has a significant probability of taking a long time, failing, or both. Let the user know that the process failed, how it failed, and why it failed to the best of our ability when it does fail.
Computation Environment
See forum x-ref
OS: On an HPC so presumably some form of Linux
64gb of RAM available to compute node
Unknown version of Qiime2
Questions
What file size is large enough for us to warn them about the probability of failure? Or should we just say "Producing .qzv files from this form of .qza can take a significant amount of time and compute power with a high risk of failure" or something similar regardless of any other factors?
Can we do this without negatively impacting backwards compatibility for users?
Bug Description Metadata Tabulate churns for extended periods of time on data with many rows/records e.g.
ErrorCorrectionDetails. Resulting .qzv unapproachably long.Steps to reproduce the behavior
qiime metadata tabulateon a significantly sizedErrorCorrectionDetails.qzaExpected behavior Let the user know what they're about to do has a significant probability of taking a long time, failing, or both. Let the user know that the process failed, how it failed, and why it failed to the best of our ability when it does fail.
Computation Environment See forum x-ref
Questions
References