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
Hiya,
For maintainability, it would help if the following archives could exist untarred under /lustre/scratch123/tol/resources/nextflow/test-data:
/lustre/scratch123/tol/resources/nextflow/test-data
./resources/ascc/asccTinyTest_V2.tar.gz ./resources/ascc/asccTinyTest.tar.gz ./resources/treeval/TreeValTinyData.tar.gz ./resources/treeval/TreeValSmallData.tar.gz
The untarring itself I could do, but it's more about sorting out the source location of those test data across all developers.
Also, the datasets should also be versioned so that updating the test data doesn't break tests of previous releases.
(I guess this also applies to some extent to ascc, curationpretext, and longreadmag)
The text was updated successfully, but these errors were encountered:
I just found that the untarred data are under /lustre/scratch123/tol/resources/treeval/treeval-testdata
/lustre/scratch123/tol/resources/treeval/treeval-testdata
Sorry, something went wrong.
No branches or pull requests
Description of feature
Hiya,
For maintainability, it would help if the following archives could exist untarred under
/lustre/scratch123/tol/resources/nextflow/test-data
:The untarring itself I could do, but it's more about sorting out the source location of those test data across all developers.
Also, the datasets should also be versioned so that updating the test data doesn't break tests of previous releases.
(I guess this also applies to some extent to ascc, curationpretext, and longreadmag)
The text was updated successfully, but these errors were encountered: