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
Describe the bug
The crop offsets do not appear to be maintained when loading the state file.
In fact the correct crop offsets are maintained when viewing the crop in the pipeline, but the rendered volume appears to be located at the origin (0, 0, 0).
To Reproduce
Steps to reproduce the behavior:
Load two datasets, eg example datasets
Crop one volume
Save state
Load state to see that volume has been shifted to (0, 0, 0)
Expected behavior
The volume is rendered in its position when saving the state file.
Screenshots
Crop settings:
Volume before saving state:
Volume immediately after loading state:
Desktop (please complete the following information):
Operating system: Windows 10
Tomviz version: 1.10
Hardware (please complete the following information):
Device: Dell Precision 3640
Graphics card: NVIDIA Quadro P400
Additional context
As mentioned, the correct crop values are maintained in the state file on load, but the volume is incorrectly positioned.
Describe the bug
The crop offsets do not appear to be maintained when loading the state file.
In fact the correct crop offsets are maintained when viewing the crop in the pipeline, but the rendered volume appears to be located at the origin (0, 0, 0).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The volume is rendered in its position when saving the state file.
Screenshots
Crop settings:
Volume before saving state:
Volume immediately after loading state:
Desktop (please complete the following information):
Hardware (please complete the following information):
Additional context
As mentioned, the correct crop values are maintained in the state file on load, but the volume is incorrectly positioned.
State file showing the bug:
crop test2.zip
The text was updated successfully, but these errors were encountered: