generated from datalad/datalad-extension-template
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
Document private/datalad-annex/QC/huge data use case #535
Comments
This is what it looks, when the above script runs...
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The script below is an executable example of a workflow that aims to address a use case for huge microscopy data processing. Each file is >4GB and the joint datasets track about 2PB (yes, not TB). The workflow aims to minimize the invasiveness of datalad use, while maximizing the utility for using datalad as an option. The resulting deposit is minimized re required inodes.
The script also demos the interventions necessary after a storage reorganization, and change of data access method.
The text was updated successfully, but these errors were encountered: