Hi Vincent,
if I understood you correctly, you have:
Now, how do you want to visualize the jplace file? There are a couple of options depending on how many sequences you placed on that tree:
Furthermore, you might want to have a look at the R package ggtree, which can also work with jplace files: https://bioconductor.org/packages/devel/bioc/vignettes/treeio/inst/doc/Importer.html#parsing-epa-and-pplacer-output
Lastly, a little caveat when working with BS values in newick trees: https://academic.oup.com/mbe/article/34/6/1535/3077051 ;-)
So long
Lucas
--
You received this message because you are subscribed to the Google Groups "raxml" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raxml+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Vincent,
Following up on Sergios’ advice i’ve written a shell script that will produce an iTOL dataset that can be used to add bootstrap symbols or text labels to a jplace tree.
It was created to use on the output from the EPA algorithm, but I think it will also work in your case.
https://github.com/Kzra/Bootstrap-Jplace
Hope it’s useful!
Ezra
Thanks Ezra! I will test it as soon i can. Thanks again!
Vincent Carrier
--
You received this message because you are subscribed to a topic in the Google Groups "raxml" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/raxml/IildAkMRI9Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
raxml+un...@googlegroups.com.
Hi,
I recently restarted using RAxmL and just tried your recommendation. I encounter however a problem:
bash bootstrap_jplace.sh RAxML_bipartitions.test RAxML_labelledTree.Placement
grep: Unmatched ) or \)
grep: Unmatched ) or \)
paste: nodeID2: No such file or directory
paste: nodeID2: No such file or directory
I attached the two files in which I am trying to use the bash file. I used the same protocol as below to get the reference tree (RAxML_bipartitions.test) and the placement tree (RAxML_labelledTree.Placement).
Am I using the wrong input files?
Vincent Carrier
From: ra...@googlegroups.com <ra...@googlegroups.com>
On Behalf Of ezra kitson
Sent: onsdag 23. mai 2018 00:38
To: raxml <ra...@googlegroups.com>
Subject: [raxml] Re: Tree visualization of Placement with bootstrap values
Hi Vincent,
--
Hi Vincent,
not sure whether Ezra is still checking this thread, so I'll jump
in.
bash sometimes is a bit tricky with the use of parenthesis in commands. Maybe Ezra used bash on a different system than you do, which might cause the difference. Anyway, the issue seems to come from lines 6 and 7 of the script (https://github.com/Kzra/Bootstrap-Jplace/blob/master/bootstrap_jplace.sh).
Try to replace them with those two lines:
grep -o -E '\).{3}' $1 | sed 's/)//' | sed 's/:0//' | sed 's/://' >BS
grep -o -E '.{4}\).{0}' $2 | sed 's/^.*{//' | sed 's/})//' >nodeID
That is, the two closing parenthesis in the grep command are now properly escaped. That might work.
Lucas
You received this message because you are subscribed to the Google Groups "raxml" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raxml+un...@googlegroups.com.
Thanks Lucas, I will try it and keep you updated!
Vincent Carrier
Hi Lucas,
I tried the bash file and it indeed worked. I encountered however a problem further away while I was trying to implement it on iToL. The bash file has assigned node IDS that iToL doesn’t seem to recognize. I added the line sed -i -e 's/^/I/' nodeID2 and now it appears all is working fine. I added the modified script in case it can be useful for other. Thanks a lot!
Vincent Carrier
From: ra...@googlegroups.com <ra...@googlegroups.com> On Behalf Of Lucas Czech
Sent: tirsdag 16. oktober 2018 10:53
To: ra...@googlegroups.com
Hi,
Actually I am ending on errors where the NodeID extracted doesn’t correspond to the original NodeID. It also collects one more NodeID than a bootstrap value. It doesn’t appear to be picking the right nodeID or ItOL is not understanding the same NodeID. Could that be possible?
Vincent Carrier
Hi Vincent,
I am not sure whether I understand what the script is supposed to
do. Jplace does not have NodeID's, but uses curly brackets {} to
denote edge numbers, which is a concept described in the jplace
paper
(https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0031009).
From what the script looks like, it extracts these edge nums, and
calls them NodeIDs. This might work, but still smells like
trouble. Mapping edges to nodes in a tree is only stable for fixed
rootings, at even then, might cause problems
(https://academic.oup.com/mbe/article/34/6/1535/3077051).
As for the correspondence of NodeIDs to original ones: Firstly,
are you sure that you use the same reference tree all the time
(identical rooting, identical topology)? If so, this comment from
the script might explain what is happening there:
#nodeID2 is the nodeID + 1, this ensures the bootstrap labels are consistent with those produced from iTOL automatically on the reference tree. To use the true nodeiDs replace nodeID2 with nodeID the the paste command.
Maybe this can help you track the issue. Or try to ask the original author of the script directly.
Lucas