Closed niederhuth closed 2 years ago
👋 Chad!
Did you run synteny()
with tomato as an outgroup, then re-run init_genespace
so that your gpar
object doesn't have an outgroup, then run pangenome()
?
I reran entire pipeline (except the initial orthofinder step) with or without tomato as outgroup.
My guess is you didn't set synteny(..., overwrite = TRUE)
, so the second run in the same directory saw that a run was there and didn't go forward (so the outgroup was ignored). In the next release, GENESPACE will check to make sure that all the genomes that you want to analyze have synteny results before not overwriting.
I deleted the results directory between runs. Also I ran it with the outgroup first.
ok. this looks like a real bug. I'll address it and get back to you.
Yup, its a bug. If you use an outgroup, v0.9.3 would not respect it. If using v0.9.3 and an outgroup, you'll also need to manually specify the genomes to use. For example pg <- pangenome(gpar, genomeIDs = c("L1","S1"))
. This should be fixed in v.0.9.4 and later, but I will take care to ensure no issues persist in future releases.
Thanks for your work finding this, Chad.
Hi John,
Hope all is well.
I'm trying to run genespace on two mimulus genomes, using tomato as an outgroup. However, during the pangenome step I am getting this error as it tries to pull the non-syn orthologs:
I do not get this error if I set
outgroup=NULL