-
Notifications
You must be signed in to change notification settings - Fork 16
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
export with -m (merge) option #652
Comments
Hi @lynnjo, Please try adding the following
The export may be slow, as reported by the original error message, because we have not optimized the performance of exporting a merged VCF yet. |
Thanks @gspowley - I will try the above. Do I still keep the "-b 65536" flag while adding the last line you show? One more question: We note that GATK can export a multi-sample vcf using the "gatk -GenomeGVCFs -V genodb://" and that is relatively fast. I know tiledbvcf originated as genomicsDB. Is the reason this works from GATK due to GATK doing some of the work to merge the files? |
Yes, keeping the |
May I take the liberty to follow up on this topic? How does multi-threading apply to the task of exporting data with (or without) the merge option? We are testing this operation with various data and can only see a single thread being active at 100% across the whole operation. |
Right, exporting data is single threaded. For large datasets, TileDB provides distributed, parallel queries as described in TileDB Academy. |
Hello -
I am using tiledbvcf to create a dataset that I would later like to be able to export as a merged vcf file. I can successfully, load and export data from this dataset. What I would like to do is export to a multi-sample vcf file. It looks like export with the -m option should handle this, though it gives me memory errors. I added the -b flag to increase this but still no luck. The command I am running:
The error I get:
Is there another trick to running the tiledbvcf export command to create a merged vcf? Thank you
I am running tiledbvcf version:
My machine is a linux, these specifics:
The text was updated successfully, but these errors were encountered: