From what I understand, in the latest milestones of QuPath, Pete has chosen to replace AreaROI with GeometryROI, as seen here:
Previously, there was a huge problem in terms of processing time using the Dilate-plugin in multiple times sequentially in the same script. However, with the usage of the Java Topology Suite it went from several minutes to matter of seconds (for a single WSI!). It’s brilliant. The same issue is addressed and solved here:
But if I understand it correctly, in order to use the Java Topoplogy Suite, you have to use the Geometry ROI type, right?
Well, that’s fine in it’s own, but for my use case, it would be nice if I could convert annotations back to the AreaROI type AFTER the dilation-processing. The reason for this is that I have produces annotations using a trained CNNs and post-processed them in the new QuPath-0.2.0m8, but the annotators, who are going to correct the predictions, are currently using 0.1.2. I believe I found a rather “illegal way” to convert a QuPath-project from a newer version to be readable in 0.1.2, but the problem is that the Geometry ROI type doesn’t exist in 0.1.2. Hence, annotations cannot be read.
Therefore, is it possible to still convert or set ROI type manually? I know that it is possible to do so from AreaROI -> GeometryROI, as seen here:
It would be nice if I could set GeometryROI -> AreaROI, such that annotations could still be readable in the old version. However, the easy solution would be for the annotators to just use the new QuPath-version. But currently, at least for previous milestones, they felt that it was too unstable. Maybe that is fixed now?