|
Bugzilla – Bug 300 |
Graph cut segmentation cannot be run twice |
Last modified: 2012-01-06 00:22:41 CST |
| ⚠ |
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. |
|
|
|
||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||
Well I now realise that yes I can run it twice... (different machine) I could not last time I tried. I also run into a problem when Toggle overlay off, which I get this error (not always): java.lang.NullPointerException at Graph_Cut$GraphCutWindow.toggleOverlay(Graph_Cut.java:440) at Graph_Cut$GraphCutWindow$1$1.run(Graph_Cut.java:243) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Furthermore, wouldn't it make sense to re-segment the image automatically as soon as one releases the Potts weight slider? And another question... why does the result gets hat blocky? Cheers G.