You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the demo and looking at the segmentation overlay on the T1 image, on some labels when I move through the axis, the labels are not overlayed on the image. (Only the brain is visible)
To Reproduce
Steps to reproduce the behavior:
Go to sMRI biomarker demo
Click on DLMUSE segmentation step
Visualize labels after segmentation
Select some label and move through the slices (I have tested it on WM(L) sagittal)
Expected behavior
The label should be visible
Screenshots
I will try to add them later if it is not reproducible
Platform Info (please complete the following information):
Cloud demo
The text was updated successfully, but these errors were encountered:
I tested this and it worked for me as expected. I guess this may be due to a confusion with the definition of the label. WM_L means WM left (this is more visible on axial and coronal views). On the sagittal view the label disappears when you move to the right hemisphere. Can you please check if this may explain what you observe?
Related to this item, having a crosshair on the image views would be very useful to locate the x, y, z coordinates of the three views. Also, clicking to a location and moving the sliders to this location would be also a useful feature. Unfortunately, on the current viewer it's not easy to add these features. We have plans for improvements in the image viewers in future releases
Describe the bug
When running the demo and looking at the segmentation overlay on the T1 image, on some labels when I move through the axis, the labels are not overlayed on the image. (Only the brain is visible)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The label should be visible
Screenshots
I will try to add them later if it is not reproducible
Platform Info (please complete the following information):
Cloud demo
The text was updated successfully, but these errors were encountered: