Mailman 3 March 2016 - scikit-image

Re: 0.12 release
by Stéfan van der Walt 04 Mar '16

04 Mar '16

Who wants to merge the last outstanding PR for 0.12! https://github.com/scikit-image/scikit-image/pulls?q=is%3Aopen+is%3Apr+mile… On 2 March 2016 at 18:50, Juan Nunez-Iglesias <jni.soma(a)gmail.com> wrote: > Aren't these pre-existing bugs? At any rate, as you say, might be a moot > point, finally. =) > > On Thu, Mar 3, 2016 at 1:29 PM, Stéfan van der Walt <stefanv(a)berkeley.edu> > wrote: >> >> On 2 March 2016 at 16:00, Juan Nunez-Iglesias <jni.soma(a)gmail.com> wrote: >> > Bug fixes seem precisely inessential to get done ahead of release? >> > Anything >> > that doesn't break the API can be added in 0.12.1? >> >> You can't really release a package with a broken test suite. So you >> have the option to temporarily disable the tests, but shipping with a >> known bug feels kind of weird? >> >> Either way, I think I've zapped most of the outstanding ones. Waiting >> for Travis. >> >> Stéfan >> >> -- >> 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. >> To post to this group, send an email to scikit-image(a)googlegroups.com. >> To view this discussion on the web, visit >> https://groups.google.com/d/msgid/scikit-image/CABDkGQnz%2BdW7-oC2CpcEpxRYj…. >> For more options, visit https://groups.google.com/d/optout. > > > -- > 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. > To post to this group, send email to scikit-image(a)googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/scikit-image/CA%2BJHcKRUYPFNz7n3OARY1rhpZ…. > > For more options, visit https://groups.google.com/d/optout.

1 0

Re: 0.12 release
by Juan Nunez-Iglesias 03 Mar '16

03 Mar '16

Aren't these pre-existing bugs? At any rate, as you say, might be a moot point, finally. =) On Thu, Mar 3, 2016 at 1:29 PM, Stéfan van der Walt <stefanv(a)berkeley.edu> wrote: > On 2 March 2016 at 16:00, Juan Nunez-Iglesias <jni.soma(a)gmail.com> wrote: > > Bug fixes seem precisely inessential to get done ahead of release? > Anything > > that doesn't break the API can be added in 0.12.1? > > You can't really release a package with a broken test suite. So you > have the option to temporarily disable the tests, but shipping with a > known bug feels kind of weird? > > Either way, I think I've zapped most of the outstanding ones. Waiting > for Travis. > > Stéfan > > -- > 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. > To post to this group, send an email to scikit-image(a)googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/scikit-image/CABDkGQnz%2BdW7-oC2CpcEpxRYj… > . > For more options, visit https://groups.google.com/d/optout. >

1 0

Re: 0.12 release
by Stéfan van der Walt 03 Mar '16

03 Mar '16

On 2 March 2016 at 16:00, Juan Nunez-Iglesias <jni.soma(a)gmail.com> wrote: > Bug fixes seem precisely inessential to get done ahead of release? Anything > that doesn't break the API can be added in 0.12.1? You can't really release a package with a broken test suite. So you have the option to temporarily disable the tests, but shipping with a known bug feels kind of weird? Either way, I think I've zapped most of the outstanding ones. Waiting for Travis. Stéfan

1 0

Re: 0.12 release
by Emmanuelle Gouillart 03 Mar '16

03 Mar '16

On Wed, Mar 02, 2016 at 01:44:11PM -0800, StÃ©fan van der Walt wrote: > On 2 March 2016 at 13:24, Emmanuelle Gouillart > <emmanuelle.gouillart(a)nsup.org> wrote: > >> #1937 highlights a bug in our tests (and failing tests, that aren't > >> currently showing up), so I would consider that the last blocker. > #1937 is a bug fix, so should be merged. The real problem is the bug > that it exposes, which is > https://github.com/scikit-image/scikit-image/issues/1935 > I will work on fixing it this afternoon. Thanks :-D

2 1

Re: 0.12 release
by Emmanuelle Gouillart 02 Mar '16

02 Mar '16

> #1937 highlights a bug in our tests (and failing tests, that aren't > currently showing up), so I would consider that the last blocker. Well, #1937 has been stalling for a while and I would consider it a minor bug only (differing opinion, anyone?), so how about we postpone #1937 to 0.13? Emma

2 1

Re: Livewire segmentation in scikit-image
by Ivo Flipse 02 Mar '16

02 Mar '16

Hi Pavlo, I did manage to get your example code working, though I agree with Stéfan that the Matplotlib GUI doesn't really enable great interactivity. I also tried loading a different image (a frontal view X-ray of the hips), but since it was really big (4kx4k) your cost calculation became pretty slow, so there's room for improvement there ;-) Also, the choice of filter and threshold didn't work out at all for my image, so that should probably be more configurable. I was rather surprised how well it worked, given that it only calculates a minimal cost path. I reckon that once the edges aren't as strong as they are in this image, it won't perform as well. Then fixing such segmentations suddenly becomes a lot more painful in my experience, because the algorithm won't help you anymore and you don't want to have to draw the entire path by hand. Perhaps Emmanuelle or Juan has any suggestions on how we can make the calculations more robust? <https://lh3.googleusercontent.com/-L-83NNetFSI/VtWqy-C7Y4I/AAAAAAAFr8E/seCg…> Ivo

2 3

3D skeleton action recognition
by Pradyumna Kumar N 01 Mar '16

01 Mar '16

Hi all, Does action recognition from 3D skeleton fit into scikit-image? If yes, I would like to implement the functionality. Let me know your thoughts on this.

2 1

SciPy 2016
by jillc＠enthought.com 01 Mar '16

01 Mar '16

**SciPy 2016 Conference (Scientific Computing with Python) Announcement** *Call for Proposals: Submit Your Tutorial and Talk Ideas by March 25, 2015 at http://scipy2016.scipy.org <http://www.scipy2015.scipy.org>. SciPy 2016 <http://www.scipy2016.scipy.org>, the 15th annual Scientific Computing with Python conference, will be held July 11-17, 2016 in Austin, Texas. SciPy is a community dedicated to the advancement of scientific computing through open source Python software for mathematics, science, and engineering. The annual SciPy Conference brings together over 650 participants from industry, academia, and government to showcase their latest projects, learn from skilled users and developers, and collaborate on code development. The full program will consist of 2 days of tutorials <http://scipy2016.scipy.org/ehome/146062/332967/?&&> (July 11-12), 3 days of talks <http://scipy2016.scipy.org/ehome/146062/332968/?&&> (July 13-15), and 2 days of developer sprints <http://scipy2016.scipy.org/ehome/146062/332969/?&&> (July 16-17). More info is available on the conference website at http://scipy2016.scipy.org <http://www.scipy2016.scipy.org> (where you can sign up for the mailing list); or follow @scipyconf <https://twitter.com/scipyconf> on Twitter. We hope you’ll join us - early bird registration is open until May 22, 2016 at http://scipy2016.scipy.org/ehome/146062/332936/?&& We encourage you to submit tutorial or talk proposals in the categories below; please also share with others who you’d like to see participate! Submit via the conference website: http://scipy2016.scipy.org <http://www.scipy2016.scipy.org>. ------------------------------------------------------------------------------------------------------------------------------ *SUBMIT A SCIPY 2016 TUTORIAL PROPOSAL- DUE MARCH 21, 2016* ------------------------------------------------------------------------------------------------------------------------------ Details and submission here: http://scipy2016.scipy.org/ehome/146062/332967/?&& These sessions provide extremely affordable access to expert training, and consistently receive fantastic feedback from participants. We're looking for submissions on topics from introductory to advanced - we'll have attendees across the gamut looking to learn. Whether you are a major contributor to a scientific Python library or an expert-level user, this is a great opportunity to share your knowledge and stipends are available. ------------------------------------------------------------------------------------------------------------------------------ **SUBMIT A SCIPY 2016 TALK / POSTER PROPOSAL - DUE MARCH 25, 2016* ------------------------------------------------------------------------------------------------------------------------------ Details and submission here: http://scipy2016.scipy.org/ehome/146062/332968/?&& SciPy 2016 will include 2 major topic tracks and 8 mini-symposia tracks. Major topic tracks include: - Python in Data Science (Big data and not so big data) - High Performance Computing Mini-symposia will include the applications of Python in: - Earth and Space Science - Biology and Medicine - Engineering - Social Science - Special Purpose Databases - Case Studies in Industry - Education - Reproducibility If you have any questions or comments, feel free to contact us at: scipy-organizers(a)scipy.org -------------------------------------------------------------------------- **SCIPY 2016 REGISTRATION IS OPEN** -------------------------------------------------------------------------- Please register early. SciPy early bird registration until May 22, 2016! Register at http://scipy2016.scipy.org. Plus, enter our t-shirt design contest to win a free registration. (Send a vector art file to scipy(a)enthought.com by March 31 to enter).

1 0