NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 1035 - More precise setting of thresholds
More precise setting of thresholds
Status: NEW
Product: Fiji
Classification: Unclassified
Component: Plugins
unspecified
PC Windows
: P4 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2015-03-23 10:28 CDT by Ann Wheeler
Modified: 2015-03-23 10:28 CDT
1 user (show)

See Also:

Description Ann Wheeler 2015-03-23 10:28:23 CDT
Dear Fiji team, 

Sorry second bug, This is an option which has kind of disappeared as it was implemented in ImageJ 1 and isn't there so much in Fiji, not sure why.

When thresholding 14 bit images  it used to be possible to precisely adjust the sliders, and they would move in the same increments. This is still fine for 8 bit images, in the threshold dialogue, for 8 bit images the threshold still moves up by units of one and equal units. In 14 bit images this isn't the case. This means that by adjusting the sliders alone it isn't possible to set the same threshold quickly between two images.

So basically in 1 14 bit image the threshold will increase using the sliders in increments of 247 and in a second 14 bit image, taken on the same system with the same parameters on the same day the threshold, in image 2, will  increase in increments of 326. Both of these numbers seem really random. Its not clear how Fiji is deciding the incremental increase.

However I suspect the bug fix for the first bug, whereby I can set my image to be treated as a 14 bit image (not an option currently available)  may change this as, presumably, if Fiji thinks the images are the same bit depth it will increase the threshold in the same increments using sliders. 

Essentially I'm not sure if this is a separate bug or the same bug but it would be nice if it could be fixed.

Thanks  Ann

Certainly one can press the set button, each time, although inexperienced users aren't keen on this and for demonatration purposes under time pressure it'd be great if it worked. Or you could enter the parameters you want for the thresholding into a little dialogue box next to the low and high sliders in the threshold GUI. Probably others have suggested this too....

Information about your version of Java:

  os.arch => amd64
  os.name => Windows 7
  os.version => 6.1
  java.version => 1.6.0_24
  java.vendor => Sun Microsystems Inc.
  java.runtime.name => Java(TM) SE Runtime Environment
  java.runtime.version => 1.6.0_24-b07
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 19.1-b02
  java.vm.vendor => Sun Microsystems Inc.
  java.vm.info => mixed mode
  java.awt.graphicsenv => sun.awt.Win32GraphicsEnvironment
  java.specification.name => Java Platform API Specification
  java.specification.version => 1.6
  sun.cpu.endian => little
  sun.desktop => windows
  file.separator => \

The up-to-date check says: REMIND_LATER

Information relevant to JAVA_HOME related problems:

  JAVA_HOME is set to: \\Mvm-igmm-h213\z$\FIJI-W~1\FIJI-W~1\Fiji.app/java/win64/jdk1.6.0_24//jre
  imagej.dir => \\Mvm-igmm-h213\z$\FIJI-W~1\FIJI-W~1\Fiji.app

Information about the version of each plugin:

Activated update sites:
ImageJ: http://update.imagej.net/ (last check:20150319171059)
Fiji: http://fiji.sc/update/ (last check:20150319202456)
Cookbook: http://sites.imagej.net/Cookbook/ (last check:20150302220629)

Files not up-to-date:
  1ad3be0d (LOCAL_ONLY) 20141216163637 jars/jpedalSTD.jar
  f416387c (LOCAL_ONLY) 20150223132413 plugins/SIMcheck-0.9.5.jar