muratmaga
muratmaga
Rework the module based on the input from @lassoan and davide punze on the forum. https://discourse.slicer.org/t/how-to-include-markup-annotations-in-scene-reconstruction-for-screen-capture/35813/11?u=muratmaga
fixed works for 5.7 or higher.
We can't do that at gpa since it just reads from files, selection states in the file -even if they were written- might be random across samples.
Well it is not a totally general purpose markup editor since it's entire existence is born to support markup partitions we need in gpa analysis. All it needs to do...
@smrolfe we discussed this using the markup editor in context of subsetting the landmarks from DeCaL. It is a separate issue on the DeCA site (and not sure if you...
We need to add this to the next update of the GPA module for sure (i.e., before the next stable is cut). Others are not that critical
@pieper @lassoan this is turning to be quite blocking for large datasets. Until we have time to look into why these errors generated, would it be possible to just print...
> This issue is all over github and StackOverflow. It is crazy to think about the hundreds of thousands $ worth of effort wasted on this because of wrong decisions...
@lassoan @pieper is this in Slicer/ITK now? Because I am still seeing the error in the latest preview?
Ok my concern is making sure this changes integrated before the new stable is cut, as we primarily use the stable versions for our events. Also @jcfr