martinsch / ilastik Goto Github PK

instead of hard coding the costs

see ilastik issue 932

Issue by martinsch from Thursday Jan 23, 2014 at 09:28 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/8

Maybe this is already fixed when merging with master.

Building scipy with buildem results in this error:

/usr/bin/ld: cannot find -lpython2.7

Dirty Workaround: Create a softlink in the appropriate directory:

ln -s <ilastik_build_dir>/lib/libpython2.7.so <ilastik_build_dir>/src/scipy-0.11.0/build/temp.linux-x86_64-2.7

Issue by martinsch from Monday Feb 10, 2014 at 23:58 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/20

...or forbid them.

Issue by martinsch from Tuesday Nov 13, 2012 at 17:06 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/4

Issue by martinsch from Thursday Jan 23, 2014 at 09:29 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/9

...and thresholds on the wrong channel etc.

I guess, the bug is somewhere in the division feature computation.

Issue by martinsch from Tuesday Nov 13, 2012 at 15:48 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/3

for conservation tracking rather than chaingraph tracking.
Provide example ilps.

Issue by hanslovsky from Friday Dec 07, 2012 at 12:31 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/6

Object Extraction Group is not saved.

Issue by martinsch from Wednesday Nov 14, 2012 at 09:47 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/5

If there are only 2 input channels (i.e. only bg and fg label), the nearest neighbor tracker should simply track the objects without considering divisions.

Make pgmlink build on windows.

Issue by martinsch from Thursday Jan 23, 2014 at 12:34 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/16

Labels should already be preset and not removable. (See counting for an example).

Issue by hanslovsky from Tuesday Feb 11, 2014 at 19:01 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/21

The "Track!" button in the Tracking Applet (conservation tracking) is grayed out after the first click. Multiple tracking calls are not possible.

Issue by martinsch from Thursday Jan 23, 2014 at 12:35 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/17

Names should be preset to the number of cells expected to be labeled with the respective label.

Issue by martinsch from Thursday Jan 23, 2014 at 10:03 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/11

This code certainly needs refactoring... :-)

Issue by martinsch from Thursday Jan 23, 2014 at 12:24 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/15

Issue by martinsch from Thursday Jan 23, 2014 at 10:58 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/13

.... and the workflows containing optical translation should be removed for the release.

Issue by martinsch from Tuesday Nov 13, 2012 at 15:48 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/2

Issue by martinsch from Monday Feb 10, 2014 at 18:29 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/18

...for division detection. Investigate!

in tracking applet

Issue by martinsch from Tuesday Nov 13, 2012 at 15:47 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/1

...and for the last one??

This may only be solved by addressing martinsch/pgmlink#8

Issue by martinsch from Thursday Jan 23, 2014 at 10:02 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/10

Make a new applet which has the object feature computation operator and a division operator as inner operators. (Make sure that division features are computed AFTER the vigra features).
All the features to be computed may be preselected already.
The applet then may be set to invisible in the workflow module since it won't display anything but only compute features.

This would be a workaround for cases where there is no need to train a classifier...

Issue by martinsch from Monday Feb 10, 2014 at 18:31 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/19

Issue by martinsch from Thursday Jan 23, 2014 at 10:16 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/12

Provide option for anisotropic division features somewhere else (data properties dialog??) or discard.

Issue by hanslovsky from Friday Dec 07, 2012 at 12:33 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/7

removing an input dataset and adding a new one leads to multiple layer in the object extraction applet

Issue by martinsch from Thursday Jan 23, 2014 at 12:24 GMT
Originally opened as https://github.com/martinsch/ilastik-topsecret/issues/14

It should be preset if tracking with classifier prior is used. Grey out the spinbox and show a tooltip that the number must be changed in the Classification applet.