Closed robertlennox closed 2 years ago
Multiple measures for the same species is likely the problem since the form=~species_latin option will match the rows of your data table with the tips of the tree. I suggest you aggregate them.
Is there a logical reason why this would have run perfectly fine a few months ago? Any further advice as to whether this could be run in the nlme::lme framework would be appreciated..
There is no logical reason why this would run fine now or a few months ago (or last year!) The reason is that if the same label is used in two different data objects (a tree and a data frame in your case), there is no unambiguous way to match them. For instance, you may have a tree with ten tips having the same label "Cichla ocellaris", but which one of them has a length of 28.6? This is the same reason why duplicated labels are not accepted in boot.phylo()
, among other functions.
When I run the name.check I get a message "OK" but warning, unknown column "tip.labels".. that is not in my data, so it must be unknown in the tree (but it is the default name)
I wonder if there is maybe an issue with repeated measures, I hadn't considered before but I have multiple measures for the same species..a table below of obs by species (first five).. maybe the pgls assumes one row per species..
species_latin n