Mailman 3 December 2016 - scikit-image

image type issue and failed conversion
by wine lover 26 Dec '16

26 Dec '16

Dear All, I was trying to use the above code segment for performing Contrast Limited Adaptive Histogram Equalization (CLAHE). def clahe_equalized(imgs): imgs_equalized = np.empty(imgs.shape) for i in range(imgs.shape[0]): print('imgs[i,0] ',imgs[i,0].dtype) print('imgs[i,0] ',imgs[i,0].max()) print('imgs[i,0] ',imgs[i,0].min()) imgs_equalized[i,0] = exposure.equalize_adapthist(imgs[i,0],clip_limit=0.03) return imgs_equalized The dtype is float64, maximum value is 255.0 and minimum value is 0.0 Running the program generates the following error message ( I only keep the related ones) imgs_equalized[i,0] = exposure.equalize_adapthist(imgs[i,0],clip_limit=0.03) raise ValueError("Images of type float must be between -1 and 1.") ValueError: Images of type float must be between -1 and 1. In accordance with the above error message and image characteristics, what are the best way to handle this scenario. I have been thinking of two approaches 1. add imgs[i,0] = imgs[i,0]/255. which scale it to 0 and 1 2. convert imgs[i,0] from float64 to unit8 but imgs[i,0] = imgs[i,0].astype(np.unit8) gives the error message such as imgs[i,0]=imgs[i,0].astype(np.unit8) AttributeError: 'module' object has no attribute 'unit8' Would you like to give any advice on this problem? Thank you very much!

1 0

Re: [scikit-image] Release schedule
by François Boulogne 26 Dec '16

26 Dec '16

Dear Developers, > > - Feature freeze 31 December 2016 > - Tag pre-relerase 15 January 2017 > - Tag release 20 January 2017 > > > To the core team: could someone, please, dedicate some time before the > freeze date to review and merge as many PR from the 0.13 roadmap as > possible (as I remember most of them are already finished in terms of > code)? > I would like to kindly rise again Egor's comment. We need more pairs of eyes on the pending PRs and pending issues, especially those tagged 0.13. These last days, I tried to go through them to check the status and re-tag them appropriately when needed. The Feature Freeze is in few days and we have PRs waiting in the stack that must be at least considered for 0.13. Thanks! -- François Boulogne. http://www.sciunto.org GPG: 32D5F22F

1 0

Re: [scikit-image] Release schedule
by Egor Panfilov 22 Dec '16

22 Dec '16

Hi Stefan, - Feature freeze 31 December 2016 > - Tag pre-relerase 15 January 2017 > - Tag release 20 January 2017 This one looks good to me. Are you interested in being release manager this time around? I'm not really familiar with the procedure, so maybe someone else could put a hat on the task of tagging, and deployment of the docs to the website. At the same time, I'd love to help with the reviews and the preparation of the release notes. To the core team: could someone, please, dedicate some time before the freeze date to review and merge as many PR from the 0.13 roadmap as possible (as I remember most of them are already finished in terms of code)? Thanks in advance! Regards, Egor Panfilov 2016-12-22 2:12 GMT+03:00 Stefan van der Walt <stefanv(a)berkeley.edu>: > Hi Egor > > On Sat, Dec 17, 2016, at 14:59, Egor Panfilov wrote: > > Above said, I'd suggest to push the release date a bit further. At least, > the freeze initiation. > > > OK, how about the following: > > - Feature freeze 31 December 2016 > - Tag pre-relerase 15 January 2017 > - Tag release 20 January 2017 > > Stéfan > > Regards, > Egor Panfilov > > P.S. I'm traveling on the next week, and will not be able to contribute > significant efforts till Dec'26th. However, I'll try to track the mailing > list, and participate in the discussions (if any). > > 2016-12-18 1:24 GMT+03:00 Stefan van der Walt <stefanv(a)berkeley.edu>: > > Hi, everyone > > It's time for a new skimage release. I have the following timeline in mind: > > Thursday 22 Dec, feature freeze > -- bug fixes, documentation, clean up -- > January 5th, tag pre-release > -- developer and early adopter testing-- > January 10th, tag release > > How does that sound? > > Also, do we have a volunteer for release manager? :) > > Finally, I m thinking it may be a good idea to make an automated release > schedule for the future. E.g. release every 4 months, and work out how long > we need to freeze each time. Opinions? > > Stéfan > > > _______________________________________________ > scikit-image mailing list > scikit-image(a)python.org > https://mail.python.org/mailman/listinfo/scikit-image > > *_______________________________________________* > scikit-image mailing list > scikit-image(a)python.org > https://mail.python.org/mailman/listinfo/scikit-image > > >

1 0

Re: [scikit-image] Release schedule
by Juan Nunez-Iglesias 21 Dec '16

21 Dec '16

I like both timelines. =) On 22 Dec. 2016, 10:13 AM +1100, Stefan van der Walt <stefanv(a)berkeley.edu>, wrote: > Hi Egor > > On Sat, Dec 17, 2016, at 14:59, Egor Panfilov wrote: > > Above said, I'd suggest to push the release date a bit further. At least, the freeze initiation. > > OK, how about the following: > > - Feature freeze 31 December 2016 > - Tag pre-relerase 15 January 2017 > - Tag release 20 January 2017 > > Stéfan > > > Regards, > > Egor Panfilov > > > > P.S. I'm traveling on the next week, and will not be able to contribute significant efforts till Dec'26th. However, I'll try to track the mailing list, and participate in the discussions (if any). > > > > 2016-12-18 1:24 GMT+03:00 Stefan van der Walt <stefanv(a)berkeley.edu>: > > > Hi, everyone > > > > > > It's time for a new skimage release. I have the following timeline in mind: > > > > > > Thursday 22 Dec, feature freeze > > > -- bug fixes, documentation, clean up -- > > > January 5th, tag pre-release > > > -- developer and early adopter testing-- > > > January 10th, tag release > > > > > > How does that sound? > > > > > > Also, do we have a volunteer for release manager? :) > > > > > > Finally, I m thinking it may be a good idea to make an automated release schedule for the future. E.g. release every 4 months, and work out how long we need to freeze each time. Opinions? > > > > > > Stéfan > > > > > > > > > _______________________________________________ > > > scikit-image mailing list > > > scikit-image(a)python.org > > > https://mail.python.org/mailman/listinfo/scikit-image > > _______________________________________________ > > scikit-image mailing list > > scikit-image(a)python.org > > https://mail.python.org/mailman/listinfo/scikit-image > > _______________________________________________ > scikit-image mailing list > scikit-image(a)python.org > https://mail.python.org/mailman/listinfo/scikit-image

1 0

Re: [scikit-image] Release schedule
by Stefan van der Walt 21 Dec '16

21 Dec '16

Hi Egor On Sat, Dec 17, 2016, at 14:59, Egor Panfilov wrote: > Above said, I'd suggest to push the release date a bit further. At > least, the freeze initiation. OK, how about the following: - Feature freeze 31 December 2016 - Tag pre-relerase 15 January 2017 - Tag release 20 January 2017 Stéfan > Regards, > Egor Panfilov > > P.S. I'm traveling on the next week, and will not be able to > contribute significant efforts till Dec'26th. However, I'll try > to track the mailing list, and participate in the discussions (if > any). > > 2016-12-18 1:24 GMT+03:00 Stefan van der Walt <stefanv(a)berkeley.edu>: >> Hi, everyone >> >> It's time for a new skimage release. I have the following timeline >> in mind: >> >> Thursday 22 Dec, feature freeze >> -- bug fixes, documentation, clean up -- >> January 5th, tag pre-release >> -- developer and early adopter testing-- >> January 10th, tag release >> >> How does that sound? >> >> Also, do we have a volunteer for release manager? :) >> >> Finally, I m thinking it may be a good idea to make an automated >> release schedule for the future. E.g. release every 4 months, and >> work out how long we need to freeze each time. Opinions? >> >> Stéfan >> >> >> _______________________________________________ >> scikit-image mailing list >> scikit-image(a)python.org >> https://mail.python.org/mailman/listinfo/scikit-image > _________________________________________________ > scikit-image mailing list > scikit-image(a)python.org > https://mail.python.org/mailman/listinfo/scikit-image

1 0

Re: [scikit-image] New team member
by Alexandre Fioravante de Siqueira 20 Dec '16

20 Dec '16

Dear Stéfan and all, thank you very much! I'll do my best to help in the development, documentation and propagation of scikit-image! Thanks again, have a nice weekend! Alex -- ------------------------------------------------------------------------------ Dr. Alexandre 'Jaguar' Fioravante de Siqueira Office 306 - Institut für Geologie Fakultät für Geowissenschaften, Geotechnik und Bergbau Technische Universität Bergakademie Freiberg Bernhard-von-Cotta-Straße, 2 Freiberg (09599), Mittelsachsen - Sachsen - Deutschland Lattes curriculum: http://lattes.cnpq.br/3936721630855880/ Personal site: http://www.programandociencia.com/about/ Github: http://www.github.com/alexandrejaguar/ Skype: alexandrejaguar Twitter: http://www.twitter.com/alexdesiqueira/ ------------------------------------------------------------------------------

1 0

Re: [scikit-image] Release schedule
by Egor Panfilov 17 Dec '16

17 Dec '16

Hi Stefan, >From my perspective there are still some issues to be closed before the release (see https://github.com/scikit-image/scikit-image/milestone/6). This year we have been using GitHub features extensively and they should represent our current point of view regarding the codebase status. Among the tagged issues there are some long-lasting ones, and these could be transfered into 0.13 roadmap. As for the others, I'd prefer to solve them first. Regarding release schedule: we are having a discussion in https://github.com/scikit-image/scikit-image/issues/2357. In short, the convenient release schedule should be tied to deprecation policy timeline, which is to be reviewed. Above said, I'd suggest to push the release date a bit further. At least, the freeze initiation. Regards, Egor Panfilov P.S. I'm traveling on the next week, and will not be able to contribute significant efforts till Dec'26th. However, I'll try to track the mailing list, and participate in the discussions (if any). 2016-12-18 1:24 GMT+03:00 Stefan van der Walt <stefanv(a)berkeley.edu>: > Hi, everyone > > It's time for a new skimage release. I have the following timeline in mind: > > Thursday 22 Dec, feature freeze > -- bug fixes, documentation, clean up -- > January 5th, tag pre-release > -- developer and early adopter testing-- > January 10th, tag release > > How does that sound? > > Also, do we have a volunteer for release manager? :) > > Finally, I m thinking it may be a good idea to make an automated release > schedule for the future. E.g. release every 4 months, and work out how long > we need to freeze each time. Opinions? > > Stéfan > > > _______________________________________________ > scikit-image mailing list > scikit-image(a)python.org > https://mail.python.org/mailman/listinfo/scikit-image >

1 0

Release schedule
by Stefan van der Walt 17 Dec '16

17 Dec '16

Hi, everyone It's time for a new skimage release. I have the following timeline in mind: Thursday 22 Dec, feature freeze -- bug fixes, documentation, clean up -- January 5th, tag pre-release -- developer and early adopter testing-- January 10th, tag release How does that sound? Also, do we have a volunteer for release manager? :) Finally, I m thinking it may be a good idea to make an automated release schedule for the future. E.g. release every 4 months, and work out how long we need to freeze each time. Opinions? Stéfan

1 0

New team member
by Stefan van der Walt 17 Dec '16

17 Dec '16

Hi everyone I would like to welcome the newest member of the scikit-image core team: Alexandre di Siqueira. We're excited to have you on board, Alex! Best regards Stéfan

1 0

scikit-image lecture at ImageXD, 29th of March
by Stefan van der Walt 13 Dec '16

13 Dec '16

Hi, everyone We are looking for tutors from the scikit-image team to teach at the annual ImageXD conference (this year at the University of Washington), to be held on 29 March 2017. Please indicate your availability to me via private email. Thanks! Stéfan

1 0