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

VCF output for different "--filter N" option #1490

Open
shin0727 opened this issue Sep 26, 2024 · 1 comment
Open

VCF output for different "--filter N" option #1490

shin0727 opened this issue Sep 26, 2024 · 1 comment

Comments

@shin0727
Copy link

Hi, I'm a Ph.D student in bioinformatics,
And I have some questions while using the "minigraph-cactus".
I run the program, in order to get some pangenome and vcf files in the graph.
I have 24 sequences in the graph, and used the following command.
"cactus-pangenome ./jobstorepath ./sequenceFile.tsv --outDir ${PREFIX1} --outName ${PREFIX1} --reference ${REF} --filter 2 --giraffe clip filter --vcf --viz --odgi --chrom-vg clip filter --chrom-og --gbz clip filter full --gfa clip full --vcf --giraffe --gfa --gbz --chrom-vg --logFile ${PREFIX1}.log"

I ran minigraph-cactus twice with the "--filter 2" and "--filter 9" options, and the variant results in the "vcf.gz" are different. I thought the "--filter" option only applies when generating dist, min, and gbz output, but does it affect the vcf results as well?

@glennhickey
Copy link
Collaborator

yeah, --filter has no effect on the vcf output.

but there are some non-deterministic parts inside cactus, which means the output can be slightly different between different runs even if the parameters are the same.

if you want to play with the --filter values without affecting the rest of the graph, you can run cactus-graphmap-join (using the vg files in chrom-alignments as input) instead.

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