I'm not a core developer, so anyone feel free to correct any inaccuracies in this post.<div><ul><li>I think most of the subsection "Image Types and Type Conversions" is now handled by various utility functions in `skimage.util` (like `img_as_float`).<br></li><li>There are now some registration tools available in skimage.</li></ul><div><span style="line-height: 17px;">I see many other areas that are either included, or appear to be blind attempts to translate Matlab functions directly. &nbsp;I could easily write an `imsubtract`, for example, but that functionality exists for any base 2D ndarray!&nbsp;</span></div></div><div><span style="line-height: 17px;"><br></span></div><div><span style="line-height: 17px;">Should function-for-function feature parity, even where this is not particularly useful, be a goal? &nbsp;That's what I get from this table.</span></div><div><span style="line-height: 17px;"><br></span></div><div><span style="line-height: 17px;">A separate but related issue is reinventing the wheel. &nbsp;NiBabel can read/write most medical image formats, including Analyze 7.5, nifti, and DICOM. &nbsp;Other well-known packages do 2d static visualization very well, load R files, etc. &nbsp;I don't have an answer for this without either reinventing many wheels, bringing over code from other projects (with attendant licensing issues and updating with their codebase, concern for backward compatibility), or adding dependencies to many other packages. &nbsp;</span></div><div><br></div><div>As a reformed Matlab user, I personally prefer the general Python way which is <b>not</b> "everything and the kitchen sink" in one massive package, but more pick-and-choose from a diverse toolkit for the problem(s) at hand. &nbsp;But that's just me.&nbsp;</div><div><br><br>On Monday, October 1, 2012 8:08:45 AM UTC-5, Wei LI @kuantkid wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div>Dear all,</div><div><br></div><div>Just notice that the warning on the page is still there(<a href="http://scikits-image.org/docs/0.7.0/coverage_table.html" target="_blank">http://scikits-image.<wbr>org/docs/0.7.0/coverage_table.<wbr>html</a>). There are still more red than green :) I am not sure whether it is a good idea to update this page and set priorities on what to expect in the near future for this package i.e. next release?</div><div><br></div><div>My personal feeling is maybe a table of what is still missing for this package will benefit those contributors which in turn will benefit the package itself.&nbsp;I myself love open source and try to make some contributions(if any) for those great packages that are related to my work(computer vision mostly) but sometimes just get confused what piece of codes will benefit others and could be included into the packages. IMHO, issue on github could be a guideline and is important, but seem not to be enough. Maybe a big picture at the website just as the coverage_table is equally important.(Or maybe there are some such pages I just missed).</div><div><br></div><div>Best,</div><div>Wei</div><div><br></div><div><br></div><div><br></div></blockquote></div>