View Issue Details

Related ChangesetsJump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003074Slicer4Module Volumespublic2013-04-16 21:392017-06-07 23:27
Reporterbmoloney Assigned Tofinetjul  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product VersionSlicer 4.2.2-1 
Target VersionSlicer 4.3.0Fixed in VersionSlicer 4.3.0 
Summary0003074: Problems visualizing floating point data in range 0-> 1
Description

Visualizing parametric maps and other floating point data with values less than 1 is not viable. The auto window/level functionality fails and it doesn't seem possible to get a good setting with the manual window/level option. The manual min/max option does not allow floating point values.

TagsNo tags attached.

Relationships

related to 0002986 closedjohan.andruejol Cannot set floating point values for w/l in Volumes 

Activities

pieper

pieper

2013-05-09 04:34

administrator   ~0008585

I tried this with an FA map (values 0 to 1) and didn't have any troubles using the current svn trunk version.

To replicate:

  • download DTI volume from SampleData
  • estimate FA volume using Diffusion Tensor Scalar Measurements module
  • go to Volumes and adjust window/level threshold.

If you have other data that behaves differently can you attach a sample volume to the bug report?

2013-05-10 12:06

 

044-r1_map.nii.gz (66,223 bytes)
bmoloney

bmoloney

2013-05-10 12:08

reporter   ~0008612

I just tested with the latest nightly. Following your steps it works correctly, however I still have the issue loading my data. I believe my issue is related to the fact I am loading a Nifti file. I have attached a single slice Nifti that demonstrates the issue.
pieper

pieper

2013-05-10 12:52

administrator   ~0008613

The interface is a bit touchy, but you can use the range slider that pops up under the window/level control to adjust the sensitivity. If I drag the two ends of that in so they range about +/- 10 then I can adjust the view pretty well for that image. Will that work for you? The problem may be that your image has outlier values that make the range bigger than you want to start with.

-Steve
bmoloney

bmoloney

2013-05-10 12:56

reporter   ~0008614

The fundamental issue is that I can't set floating point values for the Window/Level or Min/Max. I have other data where the values of interest are in the range 0 -> 0.05 which would be impossible to visualize without this capability.
pieper

pieper

2013-05-13 05:10

administrator   ~0008623

Reminder sent to: finetjul

@Julien - Is there an easy fix for the issue reported here? I.e. can the window/level spinboxes be changed to accept doubles easily?
finetjul

finetjul

2013-05-13 05:19

administrator   ~0008624

If the popup spinboxes are set to 0 and 1 ( http://www.slicer.org/slicerWiki/index.php/File:VolumesModuleWindowLevelSliderPopup.gif)
then you should be able to manually edit the window and level spinboxes with 2 decimals.
pieper

pieper

2013-05-13 05:35

administrator   ~0008625

I see - the issue for me is that I cannot type into the spinboxes on linux or mac. I can type into them on windows, in which case I can get the behavior that Julien describes and can set window/level values in the 0 to 1 category.

bmoloney, what OS platform are you using? If you have access to a windows machine, can you try the data there and see if it is usable? If so we can focus on why the spinbox/popup interface is not working on mac and linux.

2013-06-14 01:30

 

Validation form.docx (15,178 bytes)
finetjul

finetjul

2013-07-09 07:09

administrator   ~0008932

Fixed in r22151
pieper

pieper

2013-07-29 13:18

administrator   ~0009261

This is working well as far as I can tell. @bmoloney re-open if it's not working right for you.

Related Changesets

Slicer: 2145-support-for-installing-extension-from-file ed5f4ed6

2013-07-18 18:01:16

finetjul

Details Diff 		BUG: Fix decimals in volumes module

Loading MRHEAD, we want the default coordinates to be:
- spacing: 1.0, 1.0, 1.3
- origin: -86.645, 133.929, 116.786 if the length unit precision is 3
Issues 0002480, 0002986, 0003074...

git-svn-id: http://svn.slicer.org/Slicer4/trunk@22212 3bd1e089-480b-0410-8dfb-8563597acbee
mod - Libs/MRML/Widgets/Resources/UI/qMRMLVolumeInfoWidget.ui Diff File
mod - SuperBuild/External_CTK.cmake Diff File

Issue History

Date Modified Username Field Change
2013-04-16 21:39 bmoloney New Issue
2013-04-27 09:49 fedorov Relationship added related to 0002986
2013-05-09 04:34 pieper Note Added: 0008585
2013-05-10 12:06 bmoloney File Added: 044-r1_map.nii.gz
2013-05-10 12:08 bmoloney Note Added: 0008612
2013-05-10 12:52 pieper Note Added: 0008613
2013-05-10 12:56 bmoloney Note Added: 0008614
2013-05-13 05:10 pieper Note Added: 0008623
2013-05-13 05:19 finetjul Note Added: 0008624
2013-05-13 05:35 pieper Note Added: 0008625
2013-06-14 01:30 deepak_27ji File Added: Validation form.docx
2013-07-09 07:07 finetjul Status new => assigned
2013-07-09 07:07 finetjul Assigned To => finetjul
2013-07-09 07:09 finetjul Note Added: 0008932
2013-07-09 07:09 finetjul Status assigned => resolved
2013-07-09 07:09 finetjul Fixed in Version => Slicer 4.3.0
2013-07-09 07:09 finetjul Resolution open => fixed
2013-07-29 13:18 pieper Note Added: 0009261
2013-07-29 13:18 pieper Status resolved => closed
2013-07-29 13:19 pieper Target Version => Slicer 4.3.0
2017-06-07 23:27 finetjul Changeset attached => Slicer 2145-support-for-installing-extension-from-file ed5f4ed6