I just updated to Slicer 4.8.1 and noticed that the “Transform hierarchy” is not behaving correctly. It does not show the correct “tree” of transformations. For example, I have images that have four transformations on them. It should show them like this:
A
.B
…C
…D
However, it is showing transformation “C” not under transformation “B”
A
.B
C
.D
If that doesn’t make sense, I can try to get a screenshot
It shows them correctly in the transformation module. This is a shame - I find it much easier to organize data/transforms in the data module.
This bug was actually present for me in version 4.5.0. However, I could get it to show the correct “tree” by switching back and forth between “displayable” and “transform” with the “Scene Model” popup. The new version tabbed screen doesn’t do that.
Please record a screen capture video or provide step-by-step instructions that we can use to reproduce it. If we cannot reproduce the problem we cannot fix it.
Sorry if this is too basic, but since 4.5 we overhauled the module, and now there is no Scene Model selection, but three tabs, in which Transform Hierarchy is not the default. Please double check that you select the middle tab in the Data module.
I experience the same issue as Nathan. Here are the steps that I can do to reproduce the issue (latest Slicer nightly 2018-03-05, Windows 10):
Open fresh Slicer.
Create a transform node. Call it FirstTransformNode.
Save the scene.
Create a another transform node. Call it SecondTransformNode.
Make SecondTransformNode the parent of FirstTransformNode.
Save the scene.
Clear the scene.
Reload the saved scene created in Step 6.
In the reloaded scene, SecondTransformNode does not appear to be the parent of FirstTransformNode in the Data module GUI (transform hierarchy tab). Likewise, in the Transforms module, FirstTransformNode does not appear to be transformed by SecondTransformNode in the GUI. But I observe that if I check the parent node of FirstTransformNode through the Python interactor, it is SecondTransformNode. See commands below: