[Numpy-discussion] ANN: scikit-image 0.9 release
We're happy to announce the release of scikit-image v0.9.0! scikit-image is an image processing toolbox for SciPy that includes algorithms for segmentation, geometric transformations, color space manipulation, analysis, filtering, morphology, feature detection, and more. For more information, examples, and documentation, please visit our website: http://scikit-image.org New Features `scikit-image` now runs without translation under both Python 2 and 3. In addition to several bug fixes, speed improvements and examples, the 204 pull requests merged for this release include the following new features (PR number in brackets): Segmentation: - 3D support in SLIC segmentation (#546) - SLIC voxel spacing (#719) - Generalized anisotropic spacing support for random_walker (#775) - Yen threshold method (#686) Transforms and filters: - SART algorithm for tomography reconstruction (#584) - Gabor filters (#371) - Hough transform for ellipses (#597) - Fast resampling of nD arrays (#511) - Rotation axis center for Radon transforms with inverses. (#654) - Reconstruction circle in inverse Radon transform (#567) - Pixelwise image adjustment curves and methods (#505) Feature detection: - [experimental API] BRIEF feature descriptor (#591) - [experimental API] Censure (STAR) Feature Detector (#668) - Octagon structural element (#669) - Add non rotation invariant uniform LBPs (#704) Color and noise: - Add deltaE color comparison and lab2lch conversion (#665) - Isotropic denoising (#653) - Generator to add various types of random noise to images (#625) - Color deconvolution for immunohistochemical images (#441) - Color label visualization (#485) Drawing and visualization: - Wu's anti-aliased circle, line, bezier curve (#709) - Linked image viewers and docked plugins (#575) - Rotated ellipse + bezier curve drawing (#510) - PySide PyQt4 compatibility in skimage-viewer (#551) Other: - Python 3 support without 2to3. (#620) - 3D Marching Cubes (#469) - Line, Circle, Ellipse total least squares fitting and RANSAC algorithm (#440) - N-dimensional array padding (#577) - Add a wrapper around `scipy.ndimage.gaussian_filter` with useful default behaviors. (#712) - Predefined structuring elements for 3D morphology (#484) API changes --- The following backward-incompatible API changes were made between 0.8 and 0.9: - No longer wrap ``imread`` output in an ``Image`` class - Change default value of `sigma` parameter in ``skimage.segmentation.slic`` to 0 - ``hough_circle`` now returns a stack of arrays that are the same size as the input image. Set the ``full_output`` flag to True for the old behavior. - The following functions were deprecated over two releases: `skimage.filter.denoise_tv_chambolle`, `skimage.morphology.is_local_maximum`, `skimage.transform.hough`, `skimage.transform.probabilistic_hough`,`skimage.transform.hough_peaks`. Their functionality still exists, but under different names. Contributors to this release This release was made possible by the collaborative efforts of many contributors, both new and old. They are listed in alphabetical order by surname: - Ankit Agrawal - K.-Michael Aye - Chris Beaumont - François Boulogne - Luis Pedro Coelho - Marianne Corvellec - Olivier Debeir - Ferdinand Deger - Kemal Eren - Jostein Bø Fløystad - Christoph Gohlke - Emmanuelle Gouillart - Christian Horea - Thouis (Ray) Jones - Almar Klein - Xavier Moles Lopez - Alexis Mignon - Juan Nunez-Iglesias - Zachary Pincus - Nicolas Pinto - Davin Potts - Malcolm Reynolds - Umesh Sharma - Johannes Schönberger - Chintak Sheth - Kirill Shklovsky - Steven Silvester - Matt Terry - Riaan van den Dool - Stéfan van der Walt - Josh Warner - Adam Wisniewski - Yang Zetian - Tony S Yu ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Porting to the new C-API (1.7)
Hi, I've been using the numpy-1.6 C-API as part of a large C++ based OpenGL application. The C++ classes are exposed in Python by using SWIG, and utilize numpy arrays both as inputs to methods and method return values to the Python caller. To enable numpy in the SWIG generated Python module, the SWIG generated C++ file define #define PY_ARRAY_UNIQUE_SYMBOL PyArray_API whereas all other C++ files that need access to the numpy C-API contain #define NO_IMPORT_ARRAY #include numpy/arrayobject.h I have now updated to numpy-1.7, and receive warnings of the form #warning Using deprecated NumPy API, disable it by #defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION This is basically fine with me, and I don't mind doing an update of my code to the new C-API. I have a few questions though: 1) Since I am apparently using the old API, where can I find a list of the deprecated things I use? That would make the upgrade easier. 2) Do I still have to use the PY_ARRAY_UNIQUE_SYMBOL approach when using the new C-API. 3) According to some websites you can do something like #define PY_ARRAY_UNIQUE_SYMBOL PyArrayXXX This puzzles me a bit. Is there a doc somewhere where this whole thing is explained in detail. I must admit, its somewhat hard to grasp what's going on. Best regards, Mads -- +-+ | Mads Ipsen | +--+--+ | Gåsebæksvej 7, 4. tv | | | DK-2500 Valby| phone: +45-29716388 | | Denmark | email: mads.ip...@gmail.com | +--+--+ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Contiguous memory zone with C API
Hi all,
I try to change my old C API numpy code to the 'new' API. I used to hack some
internal stuff in Numpy (yes it's bad...) and I wonder now how to change it.
Let's take an example: I have ocount numpy arrays with data allocated elsewhere
than numpy, the data pointer of the PyArrayObject is set with the malloc'd zone.
Now I select one of these array to be the memory base for all of them, then I
realloc each data pointer to make sure the ocount of them have a contiguous
zone.
The code is now 'rejected' by the new API, how can I do that without hacking
into the PyArray_Object?
first=(PyArrayObject*)context-ctg_obj[0];
psize=PyArray_NBYTES(first);
for (j=1;jocount;j++)
{
current=(PyArrayObject*)context-ctg_obj[j];
tsize=PyArray_NBYTES(current);
psize+=tsize;
((PyArrayObject*)first)-data=realloc(PyArray_DATA(first),psize); /* *** how to
do that with the API ? */
memcpy(PyArray_DATA(first)+psize-tsize,PyArray_DATA(current),tsize);
free(PyArray_DATA(current));
((PyArrayObject*)current)-data=PyArray_DATA(first)+psize-tsize;
}
I use that trick to make sure that separate numpy each representing a
coordinate of a vector can be gather in a single array.
I've had a look at PyArray_resize but it requires a own_data flag which I do
not have...
Any hint, remark?
--
--
-- Marc POINOT [ONERA/DSNA] Tel:+33.1.46.73.42.84 Fax:+33.1.46.73.41.66
-- Avertissement/disclaimer http://www.onera.fr/en/emails-terms
--
--
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Numpy 1.8.0 release
Hi, This is to tell that all Theano tests pass with the branch 1.8.x with the commit 397fdec2a2c thanks Frédéric On Sun, Oct 20, 2013 at 1:35 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, I'm planning on releasing Numpy 1.8.0 next weekend. There have been a few minor fixes since 1.8.0rc2, but nothing that I think warrants another rc release. Please make sure to test the 1.8.0rc2 or maintenance/1.8.x branch with your code, for after next weekend it will be too late. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Numpy 1.8.0 release
On Mon, Oct 21, 2013 at 9:33 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, This is to tell that all Theano tests pass with the branch 1.8.x with the commit 397fdec2a2c thanks Frédéric Thanks for testing snip Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Is there a contributors agreement for numypy?
I am checking whether there is a Contributor's agreement that new contributors have to sign. Or, whether there was one for the documentation marathon. Does anyone knows the answer to this question or can point me to where I can possibly find the answer? Thanks, Mounir ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Is there a contributors agreement for numypy?
On Mon, Oct 21, 2013 at 11:53 AM, Mounir E. Bsaibes m...@linux.vnet.ibm.comwrote: I am checking whether there is a Contributor's agreement that new contributors have to sign. Or, whether there was one for the documentation marathon. Does anyone knows the answer to this question or can point me to where I can possibly find the answer? Thanks, Mounir There is no agreement needed, but all numpy is released under the simplified BSD license and any contributions need to be compatible with that. I don't know that there is any special license for the documentation. Anyone? Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Is there a contributors agreement for numypy?
21.10.2013 21:00, Charles R Harris kirjoitti: [clip] There is no agreement needed, but all numpy is released under the simplified BSD license and any contributions need to be compatible with that. I don't know that there is any special license for the documentation. Anyone? I don't think the documentation has a separate license; also BSD. -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Is there a contributors agreement for numypy?
On Mon, 2013-10-21 at 21:23 +0300, Pauli Virtanen wrote: 21.10.2013 21:00, Charles R Harris kirjoitti: [clip] There is no agreement needed, but all numpy is released under the simplified BSD license and any contributions need to be compatible with that. I don't know that there is any special license for the documentation. Anyone? I don't think the documentation has a separate license; also BSD. How the contributors know that their contributions would be released under BSD ? ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Is there a contributors agreement for numypy?
21.10.2013 22:36, Mounir E. Bsaibes kirjoitti: On Mon, 2013-10-21 at 21:23 +0300, Pauli Virtanen wrote: 21.10.2013 21:00, Charles R Harris kirjoitti: [clip] There is no agreement needed, but all numpy is released under the simplified BSD license and any contributions need to be compatible with that. I don't know that there is any special license for the documentation. Anyone? I don't think the documentation has a separate license; also BSD. How the contributors know that their contributions would be released under BSD ? The project is BSD-licensed. Contributing implies agreement to the license. -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] official binaries on web page.
If you go to numpy.org, and try to figure out how to install numpy, you are most likely to end up here: http://www.scipy.org/install.html where there is no mention of the binaries built by the numpy project itself, either Windows or Mac. There probably should be. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/ORR(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
