-
Notifications
You must be signed in to change notification settings - Fork 2
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
Writing portable node-based definitions #26
Comments
That's a good case that shows some of the limitations of phyloreferencing when taxon (specifier) sampling is very low, and phylogenetic relationships aren't stable. Note that for Tree 1, the MRCA of Campanula laciniata and Campanula pelviformis is not the one labeled with 'H', but a child of it, and hence excludes Campanula carpatha, whereas for Tree 3 it is the node labeled with 'H' and does include Campanula carpatha. Remind me how does the paper define 'H'? |
Well, there is a reason why support value is very low on Tree 2. :-) Yes, I can see that is a problem but am I catching up here? Am I missing something? I am so sorry I have been distracted by personal stuff and it is not quite over for me. Maybe we, I, would benefit from a call today and talk about this.
Nico
… On Mar 21, 2017, at 6:32 PM, Gaurav Vaidya ***@***.*** ***@***.***>> wrote:
The one node-based definition we have is:
(has_Child some (has_Descendant value Campanula_laciniata and excludes_lineage_to value Campanula_pelviformis))
and
(has_Child some (has_Descendant value Campanula_pelviformis and excludes_lineage_to value Campanula_laciniata))
This works fine on tree 3 <http://journals.plos.org/plosone/article/figure/image?size=large&id=10.1371/journal.pone.0094199.g003>:
<https://cloud.githubusercontent.com/assets/23979/24173933/9391189e-0e64-11e7-9064-8c3cd6f5eada.png>
Unfortunately, this doesn't work on tree 1 <http://journals.plos.org/plosone/article/figure/image?size=large&id=10.1371/journal.pone.0094199.g001>:
<https://cloud.githubusercontent.com/assets/23979/24173770/db3ab39a-0e63-11e7-954c-535ac47567ef.png>
There is no node that has_Descendant value Campanula_laciniata and excludes_lineage_to value Campanula_pelviformis. However, the node-based definition -- the last common ancestor of Campanula laciniata and Campanula pelviformis does exist. So how do we write that node-based phyloreference that works on both of these trees?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#26>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACaXwS2tPGLUA0LaXOlCNiIyVScsgsuKks5roE_tgaJpZM4Mkfk1>.
|
@hlapp In this paper, clade H is described as:
It also says that:
That [5] refers to Cellinese et al., 2009, where clade H is identified as clade 3. Clade 3 from that paper looks like this: And is described thusly:
So: it looks to me like clade H is interesting because it consists of endemics on Crete, but I can't find a specific definition. @ncellinese No worries! This was my first attempt at a node-based definition by using |
The one node-based definition we have is:
This works fine on tree 3:
Unfortunately, this doesn't work on tree 1:
There is no node that
has_Descendant
valueCampanula_laciniata
andexcludes_lineage_to
valueCampanula_pelviformis
. However, the node-based definition -- the last common ancestor of Campanula laciniata and Campanula pelviformis does exist. So how do we write that node-based phyloreference that works on both of these trees?The text was updated successfully, but these errors were encountered: