Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

container.getMaskBBSize().length can be larger than 3 in CostesSignificanceTest #6

burgerga opened this Issue Apr 28, 2015 · 3 comments


None yet
5 participants
Copy link

burgerga commented Apr 28, 2015

(Fiji Is Just) ImageJ 2.0.0-rc-29/1.49s; Java 1.6.0_24 [64-bit]; Linux 3.13.0-49-generic; 1501MB of 2257MB (66%)

java.lang.ArrayIndexOutOfBoundsException: 3
at algorithms.CostesSignificanceTest.execute(
at Coloc_2.colocalise(
at ij.IJ.runUserPlugIn(
at ij.IJ.runPlugIn(
at ij.Executer.runCommand(


This comment has been minimized.

Copy link

tomka commented Apr 30, 2015

Thanks for reporting. I'll be able to look into this next week. Do you by any chance have small sample images that trigger this (since I am not able to reproduce)?


This comment has been minimized.

Copy link

burgerga commented Apr 30, 2015

Unfortunately, I can't give you the real file I worked with. Instead I will give you a modified version where I set all pixel values to 1 and then cropped the image to a reasonable size, you can find it here:

Steps to reproduce:

  • Open in Fiji
  • Image > Color > Split channel
  • Analyze > Colocalization -> Coloc 2
    • Unselect all algorithms except "Costes' Significance Test"
    • Press OK

@ctrueden ctrueden added this to the m1 milestone Jul 29, 2015

@chalkie666 chalkie666 added the bug label Jul 30, 2015


This comment has been minimized.

Copy link

chalkie666 commented Jul 30, 2015

time series data will trigger this bug
eg sample images - mitosis.tif
it makes no sense to do analysis on a time series... each time point must be analysed separately. So we should detect if imagej says the image is a time series, warn the user and quit. Or process each timepoint separately and set the jobName for each timepoint accordingly for the results. THe latter is probably what the naive user expects.

(you could imagine doing a correlation measurement between different time points of the same colour channel.... then the images would need to be shuffled in dimensions appropriately, or a fancy input GUI created to select which dimensions to correlate against which...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
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.