Open AlexSCFraser opened 1 year ago
Thanks for your post - I have just had the same issue come up when running gheatmap also. I needed to update a plot I made a month ago and noticed these warning signs coming up this time round which weren't there the first time I made the heatmap plot. I wonder if it has something to do with the new R update?
Glad I found your message as I've just spent an hour trying to troubleshoot what had gone wrong....
I am getting a lot of warnings from using the ggtree() and gheatmap() functions under normal use. My plots look fine, but I was concerned I was doing something wrong. Investigating further, I actually get the same warnings when I run example code straight from the treedata book. I've got the latest version of ggtree from bioconductor (3.8.0), and latest R(4.3.1) and Rstudio(2023.6.1).
The code I'm using is from this example:
And the output when i run this in RStudio:
The generated plot is correct, exactly matching the book's plot, but these warnings are very confusing to new users of the ggtree library and it would be nice if it did not generate all these warnings when it is used properly. This might be something related to my setup, since a colleague does not get the invalid edge matrix, invalid tbl_tree object, or non-missing argument to min errors, but she does get the fill scale errors.
It would be nice if there were no errors in normal operation on well formatted code(which I assume the example code in the treedata book is) and I'm not sure if this is system or setup specific or a general problem with the library.