View Issue Details

IDProjectCategoryView StatusLast Update
0004534Slicer4Core: Scripting (Wrapping, Python)public2018-05-30 14:35
ReporterkayarreAssigned Tojcfr 
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
PlatformlinuxOSmint OS Version18.3
Product Version 
Target VersionFixed in Version 
Summary0004534: inconsistent loading behavior between transforms versus image volumes and saving images volumes
Description

loading a transform from a partial path fails while loading image volume from partial path works.

the loading transforms, loading image volumes, and saving image volumes should have the same behavior

Steps To Reproduce

from python console with transform in nested directory

### partial path fails
>>> slicer.util.loadTransform(r'./registration/dsa2post_man_LT.h5')
False

### whole path works loading transform
>>> slicer.util.loadTransform(r'/home/sansomk/caseFiles/mri/VWI_proj/case4/registration/dsa2post_man_LT.h5')
True

### loading image volume
>>> [success, dsa] = slicer.util.loadVolume(r'./image_vols/DSA.nrrd', returnNode=True)
>>> success
True

### saving image volume
>>> slicer.util.saveNode(dsa, r'./registration/dsa2post_man_trans.nrrd')
False

>>> slicer.util.saveNode(dsa, "/home/sansomk/caseFiles/mri/VWI_proj/case4/registration/registration/dsa2post_man_trans.nrrd")
True
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2018-04-03 14:20 kayarre New Issue
2018-04-03 14:20 kayarre Status new => assigned
2018-04-03 14:20 kayarre Assigned To => jcfr
2018-04-03 16:08 kayarre Summary inconsistent loading behavior between transforms versus image volumes => inconsistent loading behavior between transforms versus image volumes and saving images volumes
2018-04-03 16:08 kayarre Description Updated View Revisions
2018-04-03 16:08 kayarre Steps to Reproduce Updated View Revisions
2018-05-30 14:35 lassoan Steps to Reproduce Updated View Revisions