Mailman 3 June 2014 - scikit-image

Re: skimage and opencv
by Emmanuelle Gouillart Sept. 22, 2016

Sept. 22, 2016

Hi FranÃ¯Â¿Â½ois, that's an excellent question, and not a troll :-). Opencv is a very powerful library, but it focuses primarily on computer vision (feature detection and extraction, classification, ...), as opposed to image processing in general (with other tasks such as denoising, segmentation, ...). The other big difference is that skimage builds on numpy ndarrays, and uses the full power of the numpy API (including of course the basic facilities for processing arrays as images that come with numpy), as well as some of scipy functions (you could have added scipy.ndimage to your list -- a few functions in skimage are wrappers around scipy.ndimage, that exist for the sake of completeneness). One important consequence is that algorithms working for 3-d or even n-d images can be easily implemented in 3-d/n-d in skimage, whereas opencv is restricted to 2-D images (as far as I know). Thanks to the use of numpy arrays, the API of skimage is also quite pleasant for a numpy user, more than the API of opencv. A related difference is that skimage is written in python and cython, whereas opencv is a C++ library. The two libraries attract a different crowd of developers, and a Python/Cython toolkit based on numpy arrays is easier to develop and maintain inside the Scientific Python ecosystem. I'm sure that other devs/users will have things to add to this discussion! Cheers, Emmanuelle On Thu, Dec 27, 2012 at 02:06:08PM -0800, FranÃ¯Â¿Â½ois wrote: > Hi users and devs, > It came to my knowledge that another python library (based on C++ and C > codes) for image processing exists too : opencv > I understand that numpy intregrates some basic features and we need some > advanced features but I have the feeling that skimages is redoundant with > opencv in some ways. > What's the position of skimage about that? (Don't read this question as a > troll but like a real question). > I mean that similar features exist in both. Would not be possible to > reuse/integrate opencv or merge? what's the reason for keeping them apart? > My observation is there is 4 libraries to manipulate images: > * PIL > * numpy > * skimages > * opencv > That's a lot. > Cheers,

3 2

Re: Building skimage wheels for OS X using Travis CI
by Stéfan van der Walt June 30, 2014

June 30, 2014

Hi Matthew On Tue, Jul 1, 2014 at 1:20 AM, Matthew Brett <matthew.brett(a)gmail.com> wrote: > This repo is now working; it builds the wheels, runs the tests and > then uploads to a rackspace container: This is absolutely fantastic--thank you! > Any interest in taking this over to the scikit-image organization? If > you make me a member even temporarily, I can set you up with the > encrypted API key to upload to the rackspace container. I've forked the repo to the scikit-image organization and added you to the packaging team with the necessary administrative rights. Thanks again! Stéfan

1 0

Re: Building skimage wheels for OS X using Travis CI
by Matthew Brett June 30, 2014

June 30, 2014

Hi, On Sat, Jun 28, 2014 at 2:14 AM, Matthew Brett <matthew.brett(a)gmail.com> wrote: > Hi, > > On Fri, Jun 27, 2014 at 3:47 PM, Matthew Brett <matthew.brett(a)gmail.com> wrote: >> Hi, >> >> On Fri, Jun 27, 2014 at 3:30 PM, Jonathan Helmus <jjhelmus(a)gmail.com> wrote: >>> All, >>> >>> To follow up on the thread in which Matthew provided OS X wheel packages >>> for the v0.10.0 release, I was inspired to create a more reproducible method >>> for building wheels. What I came up with is a GitHub repository [1] which >>> uses the Mac OS X CI environment provided by Travis CI and miniconda to >>> create wheels for Python 2.6, 2.7, 3.3 and 3.4. These are uploaded to >>> GitHub as a Release which users can download. These files could be then >>> uploaded to PyPI, perhapes after renaming them so indicate that they will >>> work using the Python.org/macport/homebrew python. Travis CI could also be >>> setup to upload these file to directly to PyPI or to S3, Rackspace, or a >>> number of other providers [2]. >>> >>> I have not extensively tested these wheel files. Despite having >>> Anaconda's platform (macosx_10_5_x86_64) I expect that these work with other >>> Mac Python versions, but verification should be done. It should be possible >>> to adapt this to use a different version of Python for the build (the >>> Python.org version is probably best) if compatibility is an issue. Let me >>> know if folks are interested in using this and I'd be happy to improve upon >>> the method. >>> >>> Also a big thanks to Matthew for providing the initial spark of interest and >>> for the great write up on spinning wheels for OS X [3]. Python packaging is >>> getting pretty exciting. >> >> Nice job - it looks very clean. >> >> I had the same idea, but my setup is much messier; I use some shell >> scripts I inherited from Matt Terry [1]. Example in use (much less >> neat than yours, but for a more complex build) [2]. >> >> Although your install is really neat, I think conda isn't a good basis >> for the wheels, because it is x86_64 only, so can't build wheels >> compatible with system python or python.org python: >> >> $ python -c "import distutils.util; print(distutils.util.get_platform())" >> >> macosx-10.5-x86_64 >> >> Here's a testing grid for the scipy stack, checking wheel >> compatibility across a range of OSX Pythons, and including i386 - >> again - based on Matt Terry's scripts [3]. Maybe something like that >> could be generalized for - say - scikit-image test wheels for RCs and >> development builds. I think that would be pretty easy. > > This is a scikit-image wheel builder using Matt Terry's scripts and > Python.or g pythons: > > https://github.com/matthew-brett/scikit-image-wheels > > It runs the tests before uploading, and the tests will be a little > tough to get passing - they have lots of dependencies - but the > general structure is a bit cleaner than I had first thought, This repo is now working; it builds the wheels, runs the tests and then uploads to a rackspace container: https://travis-ci.org/matthew-brett/scikit-image-wheels/builds/28821657 Any interest in taking this over to the scikit-image organization? If you make me a member even temporarily, I can set you up with the encrypted API key to upload to the rackspace container. Also, I think these are the right wheels to build because they work with python.org and system pythons... It would mean that anyone in the organization could build and test wheels with a click of a button or a commit to the repo. Cheers, Matthew

1 0

Re: Doctest failures
by Josh Warner June 30, 2014

June 30, 2014

Several of these might be solved by globally forcing the expected numpy.set_printoptions <http://docs.scipy.org/doc/numpy/reference/generated/numpy.set_printoptions.…> prior to running the doctests. I'm not sure why this would differ in certain platforms, but for whatever reason it looks like on OSX 10.9 you're reliably printing an additional two digits. The second to last error, in skimage.measure._label.label, looks like a real error / malformed example to me. Josh On Friday, June 20, 2014 9:18:34 AM UTC-5, Juan Nunez-Iglesias wrote: > > Hi all, > > I'm running this > <https://github.com/scikit-image/skimage-tutorials/blob/master/scipy-2014/ch…> > on my system (OSX 10.9) and getting some doctest failures, apparently due > to precision issues (see below). Can people please run this on theirs and > see what happens, and offer ideas re: fixing it? I imagine something like > setting the precision of numpy printouts will do, but it would be best if > that can be a global setting. > > In the meantime, I might not run the doctests in this script, so that > people don't incorrectly fail their check_env for the SciPy 2014 > tutorial... Thoughts? > > Thanks! > > Juan. > > ........................................F.F...................................F./Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py:4: > skimage_deprecation: Call to deprecated function ``label``. Use > ``skimage.measure.label`` instead. > return _label(input, neighbors, background, return_num) > ..F....................................................... > ====================================================================== > FAIL: Doctest: skimage.feature.texture.greycoprops > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 2226, in runTest > raise self.failureException(self.format_failure(new.getvalue())) > AssertionError: Failed doctest test for skimage.feature.texture.greycoprops > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/feature/texture.py", > line 125, in greycoprops > > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/feature/texture.py", > line 176, in skimage.feature.texture.greycoprops > Failed example: > contrast > Expected: > array([[ 0.58333333, 1. ], > [ 1.25 , 2.75 ]]) > Got: > array([[ 0.5833333333, 1. ], > [ 1.25 , 2.75 ]]) > > > ====================================================================== > FAIL: Doctest: skimage.filter._gaussian.gaussian_filter > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 2226, in runTest > raise self.failureException(self.format_failure(new.getvalue())) > AssertionError: Failed doctest test for > skimage.filter._gaussian.gaussian_filter > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/filter/_gaussian.py", > line 13, in gaussian_filter > > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/filter/_gaussian.py", > line 73, in skimage.filter._gaussian.gaussian_filter > Failed example: > gaussian_filter(a, sigma=0.4) # mild smoothing > Expected: > array([[ 0.00163116, 0.03712502, 0.00163116], > [ 0.03712502, 0.84496158, 0.03712502], > [ 0.00163116, 0.03712502, 0.00163116]]) > Got: > array([[ 0.0016311596, 0.0371250207, 0.0016311596], > [ 0.0371250207, 0.8449615765, 0.0371250207], > [ 0.0016311596, 0.0371250207, 0.0016311596]]) > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/filter/_gaussian.py", > line 77, in skimage.filter._gaussian.gaussian_filter > Failed example: > gaussian_filter(a, sigma=1) # more smooting > Expected: > array([[ 0.05855018, 0.09653293, 0.05855018], > [ 0.09653293, 0.15915589, 0.09653293], > [ 0.05855018, 0.09653293, 0.05855018]]) > Got: > array([[ 0.0585501805, 0.096532928 , 0.0585501805], > [ 0.096532928 , 0.1591558917, 0.096532928 ], > [ 0.0585501805, 0.096532928 , 0.0585501805]]) > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/filter/_gaussian.py", > line 82, in skimage.filter._gaussian.gaussian_filter > Failed example: > gaussian_filter(a, sigma=1, mode='reflect') > Expected: > array([[ 0.08767308, 0.12075024, 0.08767308], > [ 0.12075024, 0.16630671, 0.12075024], > [ 0.08767308, 0.12075024, 0.08767308]]) > Got: > array([[ 0.0876730803, 0.1207502431, 0.0876730803], > [ 0.1207502431, 0.1663067063, 0.1207502431], > [ 0.0876730803, 0.1207502431, 0.0876730803]]) > > > ====================================================================== > FAIL: Doctest: skimage.measure._label.label > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 2226, in runTest > raise self.failureException(self.format_failure(new.getvalue())) > AssertionError: Failed doctest test for skimage.measure._label.label > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py", > line unknown line number, in label > > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py", > line ?, in skimage.measure._label.label > Failed example: > x = np.eye(3).astype(int) > Exception raised: > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 1315, in __run > compileflags, 1) in test.globs > File "<doctest skimage.measure._label.label[0]>", line 1, in <module> > x = np.eye(3).astype(int) > NameError: name 'np' is not defined > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py", > line ?, in skimage.measure._label.label > Failed example: > print(x) > Exception raised: > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 1315, in __run > compileflags, 1) in test.globs > File "<doctest skimage.measure._label.label[1]>", line 1, in <module> > print(x) > NameError: name 'x' is not defined > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py", > line ?, in skimage.measure._label.label > Failed example: > print(m.label(x, neighbors=4)) > Exception raised: > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 1315, in __run > compileflags, 1) in test.globs > File "<doctest skimage.measure._label.label[2]>", line 1, in <module> > print(m.label(x, neighbors=4)) > NameError: name 'm' is not defined > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py", > line ?, in skimage.measure._label.label > Failed example: > print(m.label(x, neighbors=8)) > Exception raised: > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 1315, in __run > compileflags, 1) in test.globs > File "<doctest skimage.measure._label.label[3]>", line 1, in <module> > print(m.label(x, neighbors=8)) > NameError: name 'm' is not defined > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py", > line ?, in skimage.measure._label.label > Failed example: > x = np.array([[1, 0, 0], > [1, 1, 5], > [0, 0, 0]]) > Exception raised: > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 1315, in __run > compileflags, 1) in test.globs > File "<doctest skimage.measure._label.label[4]>", line 1, in <module> > x = np.array([[1, 0, 0], > NameError: name 'np' is not defined > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/_label.py", > line ?, in skimage.measure._label.label > Failed example: > print(m.label(x, background=0)) > Exception raised: > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 1315, in __run > compileflags, 1) in test.globs > File "<doctest skimage.measure._label.label[5]>", line 1, in <module> > print(m.label(x, background=0)) > NameError: name 'm' is not defined > > > ====================================================================== > FAIL: Doctest: skimage.measure.fit.ransac > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/Users/nuneziglesiasj/anaconda/lib/python2.7/doctest.py", line > 2226, in runTest > raise self.failureException(self.format_failure(new.getvalue())) > AssertionError: Failed doctest test for skimage.measure.fit.ransac > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/fit.py", > line 470, in ransac > > ---------------------------------------------------------------------- > File > "/Users/nuneziglesiasj/anaconda/lib/python2.7/site-packages/skimage/measure/fit.py", > line 576, in skimage.measure.fit.ransac > Failed example: > ransac_model.params > Expected: > array([ 20.12762373, 29.73563063, 4.81499637, 10.4743584 , > 0.05217117]) > Got: > array([ 20.1276237259, 29.7356306313, 4.8149963715, 10.474358404 , > 0.0521711691]) >

2 1

reduce time taken for ellipse detection
by Austin Chungath June 30, 2014

June 30, 2014

Hi, I am trying out the ellipse hough transform as described in the following link: http://scikit-image.org/docs/dev/auto_examples/plot_circular_elliptical_hou… The ellipse detection in the example above with the coffee mug takes about 15 seconds to give a result. Unfortunately, I need to be able to at least do this in under a second since I am working on a video stream. 1. Is it possible to get the time taken for ellipse detection to under a second? 2. Are there any suggestions for improving the execution time? 3. Are there any other library/package that can do ellipse detection better? 4. When I use my own image instead of the coffee mug - I get an error :Buffer and memoryview are not contiguous in the same dimension I use the following code for loading the image the rest of the code is the same from the above example. image_rgb = io.imread('ellipse.png') #instead of image_rgb = data.coffee()[0:220, 160:420] Obviously I must be doing something wrong. I had mostly been working with OpenCV so I am a bit new to skimage's way of doing things. Please feel free to assume that I am a noob and any help is much appreciated. Thanks, Austin

3 2

Re: Building skimage wheels for OS X using Travis CI
by Matthew Brett June 28, 2014

June 28, 2014

Hi, On Fri, Jun 27, 2014 at 3:47 PM, Matthew Brett <matthew.brett(a)gmail.com> wrote: > Hi, > > On Fri, Jun 27, 2014 at 3:30 PM, Jonathan Helmus <jjhelmus(a)gmail.com> wrote: >> All, >> >> To follow up on the thread in which Matthew provided OS X wheel packages >> for the v0.10.0 release, I was inspired to create a more reproducible method >> for building wheels. What I came up with is a GitHub repository [1] which >> uses the Mac OS X CI environment provided by Travis CI and miniconda to >> create wheels for Python 2.6, 2.7, 3.3 and 3.4. These are uploaded to >> GitHub as a Release which users can download. These files could be then >> uploaded to PyPI, perhapes after renaming them so indicate that they will >> work using the Python.org/macport/homebrew python. Travis CI could also be >> setup to upload these file to directly to PyPI or to S3, Rackspace, or a >> number of other providers [2]. >> >> I have not extensively tested these wheel files. Despite having >> Anaconda's platform (macosx_10_5_x86_64) I expect that these work with other >> Mac Python versions, but verification should be done. It should be possible >> to adapt this to use a different version of Python for the build (the >> Python.org version is probably best) if compatibility is an issue. Let me >> know if folks are interested in using this and I'd be happy to improve upon >> the method. >> >> Also a big thanks to Matthew for providing the initial spark of interest and >> for the great write up on spinning wheels for OS X [3]. Python packaging is >> getting pretty exciting. > > Nice job - it looks very clean. > > I had the same idea, but my setup is much messier; I use some shell > scripts I inherited from Matt Terry [1]. Example in use (much less > neat than yours, but for a more complex build) [2]. > > Although your install is really neat, I think conda isn't a good basis > for the wheels, because it is x86_64 only, so can't build wheels > compatible with system python or python.org python: > > $ python -c "import distutils.util; print(distutils.util.get_platform())" > > macosx-10.5-x86_64 > > Here's a testing grid for the scipy stack, checking wheel > compatibility across a range of OSX Pythons, and including i386 - > again - based on Matt Terry's scripts [3]. Maybe something like that > could be generalized for - say - scikit-image test wheels for RCs and > development builds. I think that would be pretty easy. This is a scikit-image wheel builder using Matt Terry's scripts and Python.or g pythons: https://github.com/matthew-brett/scikit-image-wheels It runs the tests before uploading, and the tests will be a little tough to get passing - they have lots of dependencies - but the general structure is a bit cleaner than I had first thought, Cheers, Matthew

1 0

Building skimage wheels for OS X using Travis CI
by Jonathan Helmus June 27, 2014

June 27, 2014

All, To follow up on the thread in which Matthew provided OS X wheel packages for the v0.10.0 release, I was inspired to create a more reproducible method for building wheels. What I came up with is a GitHub repository [1] which uses the Mac OS X CI environment provided by Travis CI and miniconda to create wheels for Python 2.6, 2.7, 3.3 and 3.4. These are uploaded to GitHub as a Release which users can download. These files could be then uploaded to PyPI, perhapes after renaming them so indicate that they will work using the Python.org/macport/homebrew python. Travis CI could also be setup to upload these file to directly to PyPI or to S3, Rackspace, or a number of other providers [2]. I have not extensively tested these wheel files. Despite having Anaconda's platform (macosx_10_5_x86_64) I expect that these work with other Mac Python versions, but verification should be done. It should be possible to adapt this to use a different version of Python for the build (the Python.org version is probably best) if compatibility is an issue. Let me know if folks are interested in using this and I'd be happy to improve upon the method. Also a big thanks to Matthew for providing the initial spark of interest and for the great write up on spinning wheels for OS X [3]. Python packaging is getting pretty exciting. Cheers, - Jonathan Helmus http://nmrglue.com/jhelmus/ [1] https://github.com/jjhelmus/scikit-image-ci-wheel-builder [2] http://docs.travis-ci.com/user/deployment/ [3] https://github.com/MacPython/wiki/wiki/Spinning-wheels

3 2

Fwd: Interface for the Interactive Gallery
by Johannes Schönberger June 27, 2014

June 27, 2014

This message was not supposed for the regular list, but instead for skimage-gsoc. Sorry about the confusion… Johannes Schönberger > > On Jun 26, 2014, at 11:08 PM, Johannes Schönberger <jsch(a)demuc.de> wrote: > >> I just did. It’s strange… something must be special about your messages to the list. Normally, I automatically reply to the list… >> >> Sorry. >> >> Johannes Schönberger >> >> On Jun 26, 2014, at 11:06 PM, Rishabh Raj <rishabhr123(a)gmail.com> wrote: >> >>> Could you add this to the google group thread? >>> >>> >>> On Thu, Jun 26, 2014 at 2:29 PM, Johannes Sch önberger <jsch(a)demuc.de> wrote: >>> >>>> It's time we work out the interface for the Interactive Gallery (more on discussion about it - http://bit.ly/1m0YD19 and blog @ http://sharkysoc14.wordpress.com/). >>>> >>>> I initially had two different ideas. One is we try to integrate our code editor with the example code and place a run button strategically on the example page itself for ex @ http://scikit-image.org/docs/dev/auto_examples/plot_convex_hull.html >>>> >>>> The other idea would be to have a separate testing page, for this, maybe there we could have the user select with dropdown, the example he wants to Run, which would load code and the previously generated output image, then he can Run it and get new output. >>>> The default output and new output are separated by a vertical division, so it is easy to compare them too. >>>> >>>> Personally i would prefer the later idea. imho, it provides for a more cleaner and effective solution. What do you think? >>> >>> I think, the latter idea is very good. Also, it should be easy to add a “Run” button to each example, that preselects the respective entry in to drop down menu. That way we combine your two ideas. >>> >>> Can you tell how the whole thing scales with number of users? >>> >>> >>> >>> -- >>> Best, >>> Rishabh Raj >> >

1 0

Re: Interface for the Interactive Gallery
by Johannes Schönberger June 27, 2014

June 27, 2014

My message attached below… On Jun 26, 2014, at 11:06 PM, Rishabh Raj <rishabhr123(a)gmail.com> wrote: > Could you add this to the google group thread? > > > On Thu, Jun 26, 2014 at 2:29 PM, Johannes Sch önberger <jsch(a)demuc.de> wrote: > > > It's time we work out the interface for the Interactive Gallery (more on discussion about it - http://bit.ly/1m0YD19 and blog @ http://sharkysoc14.wordpress.com/). > > > > I initially had two different ideas. One is we try to integrate our code editor with the example code and place a run button strategically on the example page itself for ex @ http://scikit-image.org/docs/dev/auto_examples/plot_convex_hull.html > > > > The other idea would be to have a separate testing page, for this, maybe there we could have the user select with dropdown, the example he wants to Run, which would load code and the previously generated output image, then he can Run it and get new output. > > The default output and new output are separated by a vertical division, so it is easy to compare them too. > > > > Personally i would prefer the later idea. imho, it provides for a more cleaner and effective solution. What do you think? > > I think, the latter idea is very good. Also, it should be easy to add a “Run” button to each example, that preselects the respective entry in to drop down menu. That way we combine your two ideas. > > Can you tell how the whole thing scales with number of users? > > > > -- > Best, > Rishabh Raj

1 0

Re: Example doesn't display in gallery?
by Tony Yu June 26, 2014

June 26, 2014

It looks like the IPython notebook code added to `dox/ext/plot2rst.py` is the cause. Specifically, the call to `publish_parts` ( https://github.com/scikit-image/scikit-image/blob/master/doc/ext/plot2rst.p…) is causing problems with some links. For this example, links aren't being resolved correctly---I'm not sure why though. Note that links that define and refer-to links in separate blocks will fail (e.g. the Radon example), but that's not the case here. On Wed, Jun 25, 2014 at 10:15 AM, Rishabh Raj <rishabhr123(a)gmail.com> wrote: > The ipynb link also seems to be not generated. > > > On Wednesday, June 25, 2014, Stéfan van der Walt <stefan(a)sun.ac.za> wrote: > >> I don't see it either! Yikes, how did that happen? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "scikit-image" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to scikit-image+unsubscribe(a)googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Best, > Rishabh Raj > > -- > You received this message because you are subscribed to the Google Groups > "scikit-image" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to scikit-image+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

1 0