Skip to content
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

Question about './work directory storage issue' #47

Open
xxYaaoo opened this issue Nov 14, 2024 · 1 comment
Open

Question about './work directory storage issue' #47

xxYaaoo opened this issue Nov 14, 2024 · 1 comment

Comments

@xxYaaoo
Copy link

xxYaaoo commented Nov 14, 2024

Hello,

I am wondering if it is feasible to delete some folders in ./work directory of some completed steps according to the output.log in order to alleviate storage burden? For example, the pipeline is running, but I delete the 'cd/d3d2ce' dir.
image
Besides, I also encounter the situation that when I use 105 samples to test the output difference between 'GT-sv-GA' and 'GT-svsn-GA' simultaneously, the storage of ./work could reach over 10T. Is this a normal phenomenon?

Thank you for the development and maintenance of GraffiTE !!

@clemgoub
Copy link
Collaborator

Hello @xxYaaoo,

Thank you for your feedback, this is indeed something we should look into.
Can you tell us if there is any process that uses most of the storage? If that's the graph alignments, perhaps we can delete the alignments files once the VCF for the sample is made.

For the time being, you should be safe to delete a ./work directory once make_graph is complete. At this point, you will be able to use the VCF produced by the tsd_ processes, in the 3_TSD_Search output directory.

Cheers,

Clém

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants