Skip to content
naulon

No retraction, correction or concern found when last checked on Oct 15, 2026.

scikit-image: image processing in Python

Stéfan van der Walt, Johannes L. Schönberger, Juan Nunez-Iglesias and 5 more

PeerJ · 2014

doi:10.7717/peerj.453

Abstract

scikit-image is an image processing library that implements algorithms and utilities for use in research, education and industry applications. It is released under the liberal Modified BSD open source license, provides a well-documented API in the Python programming language, and is developed by an active, international team of collaborators. In this paper we highlight the advantages of open source to achieve the goals of the scikit-image library, and we showcase several real-world image processing applications that use scikit-image. More information can be found on the project homepage, http://scikit-image.org.

Full text

From PubMed Central, U.S. National Library of Medicine, as current on Oct 16, 2026. Paragraph numbers are ours, so an answer can point at one.

Introduction

In our data-rich world, images represent a significant subset of all measurements made. Examples include DNA microarrays, microscopy slides, astronomical observations, satellite maps, robotic vision capture, synthetic aperture radar images, and higher-dimensional images such as 3-D magnetic resonance or computed tomography imaging. Exploring these rich data sources requires sophisticated software tools that should be easy to use, free of charge and restrictions, and able to address all the challenges posed by such a diverse field of analysis.

This paper describes scikit-image, a collection of image processing algorithms implemented in the Python programming language by an active community of volunteers and available under the liberal BSD Open Source license. The rising popularity of Python as a scientific programming language, together with the increasing availability of a large eco-system of complementary tools, makes it an ideal environment in which to produce an image processing toolkit.

The project aims are:

To provide high quality, well-documented and easy-to-use implementations of common image processing algorithms.

Such algorithms are essential building blocks in many areas of scientific research, algorithmic comparisons and data exploration. In the context of reproducible science, it is important to be able to inspect any source code used for algorithmic flaws or mistakes. Additionally, scientific research often requires custom modification of standard algorithms, further emphasizing the importance of open source.

To facilitate education in image processing.

The library allows students in image processing to learn algorithms in a hands-on fashion by adjusting parameters and modifying code. In addition, a novice module is provided, not only for teaching programming in the “turtle graphics” paradigm, but also to familiarize users with image concepts such as color and dimensionality. Furthermore, the project takes part in the yearly Google Summer of Code program1https://developers.google.com/open-source/soc (accessed 30 March 2014)., where students learn about image processing and software engineering through contributing to the project.

https://developers.google.com/open-source/soc (accessed 30 March 2014).

To address industry challenges.

High quality reference implementations of trusted algorithms provide industry with a reliable way of attacking problems without having to expend significant energy in re-implementing algorithms already available in commercial packages. Companies may use the library entirely free of charge, and have the option of contributing changes back, should they so wish.

Getting started

One of the main goals of scikit-image is to make it easy for any user to get started quickly—especially users already familiar with Python’s scientific tools. To that end, the basic image is just a standard NumPy array, which exposes pixel data directly to the user. A new user can simply load an image from disk (or use one of scikit-image’s sample images), process that image with one or more image filters, and quickly display the results:

The above demonstration loads data.coins, an example image shipped with scikit-image. For a more complete example, we import NumPy for array manipulation and matplotlib for plotting. At each step, we add the picture or the plot to a matplotlib figure shown in Fig. 1.

Since the image is represented by a NumPy array, we can easily perform operations such as building a histogram of the intensity values.

To divide the foreground and background, we threshold the image to produce a binary image. Several threshold algorithms are available. Here, we employ filter.threshold_adaptive where the threshold value is the weighted mean for the local neighborhood of a pixel.

We can easily detect interesting features, such as local maxima and edges. The function feature.peak_local_max can be used to return the coordinates of local maxima in an image.

Next, a Canny filter (filter.canny) detects the edge of each coin.

Then, we attribute to each coin a label (morphology.label) that can be used to extract a sub-picture. Finally, physical information such as the position, area, eccentricity, perimeter, and moments can be extracted using measure.regionprops.

scikit-image thus makes it possible to perform sophisticated image processing tasks with only a few function calls.

Library overview

The scikit-image project started in August of 2009 and has received contributions from more than 100 individuals.2https://www.ohloh.net/p/scikit-image The package can be installed on all major platforms (e.g., BSD, GNU/Linux, OS X, Windows) from, amongst other sources, the Python Package Index (PyPI),3http://pypi.python.org Continuum Analytics Anaconda,4https://store.continuum.io/cshop/anaconda Enthought Canopy,5https://www.enthought.com/products/canopy Python(x,y),6https://code.google.com/p/pythonxy NeuroDebian and GNU/Linux distributions such as Ubuntu.7http://packages.ubuntu.com In March 2014 alone, the package was downloaded more than 5000 times from PyPI.8http://pypi.python.org/pypi/scikit-image (accessed 30 March 2014).

https://www.ohloh.net/p/scikit-image

http://pypi.python.org

https://store.continuum.io/cshop/anaconda

https://www.enthought.com/products/canopy

https://code.google.com/p/pythonxy

http://packages.ubuntu.com

http://pypi.python.org/pypi/scikit-image (accessed 30 March 2014).

As of version 0.10, the package contains the following sub-modules:

color: Color space conversion.

data: Test images and example data.

draw: Drawing primitives (lines, text, etc.) that operate on NumPy arrays.

exposure: Image intensity adjustment, e.g., histogram equalization, etc.

feature: Feature detection and extraction, e.g., texture analysis, corners, etc.

filter: Sharpening, edge finding, rank filters, thresholding, etc.

graph: Graph-theoretic operations, e.g., shortest paths.

io: Wraps various libraries for reading, saving, and displaying images and video, such as Pillow9http://pillow.readthedocs.org/en/latest/ (accessed 30 May 2015). and FreeImage.10http://freeimage.sourceforge.net/ (accessed 15 May 2015).

http://pillow.readthedocs.org/en/latest/ (accessed 30 May 2015).

http://freeimage.sourceforge.net/ (accessed 15 May 2015).

measure: Measurement of image properties, e.g., similarity and contours.

morphology: Morphological operations, e.g., opening or skeletonization.

novice: Simplified interface for teaching purposes.

restoration: Restoration algorithms, e.g., deconvolution algorithms, denoising, etc.

segmentation: Partitioning an image into multiple regions.

transform: Geometric and other transforms, e.g., rotation or the Radon transform.

viewer: A simple graphical user interface for visualizing results and exploring parameters.

For further details on each module, we refer readers to the API documentation online.11http://scikit-image.org/docs/dev/api/api.html

http://scikit-image.org/docs/dev/api/api.html

Data format and pipelining

scikit-image represents images as NumPy arrays, the de facto standard for storage of multi-dimensional data in scientific Python. Each array has a dimensionality, such as 2 for a 2-D grayscale image, 3 for a 2-D multi-channel image, or 4 for a 3-D multi-channel image; a shape, such as (M, N, 3) for an RGB color image with M vertical and N horizontal pixels; and a numeric data type, such as float for continuous-valued pixels and uint8 for 8-bit pixels. Our use of NumPy arrays as the fundamental data structure maximizes compatibility with the rest of the scientific Python ecosystem. Data can be passed as-is to other tools such as NumPy, SciPy, matplotlib, scikit-learn, Mahotas, OpenCV, and more.

Images of differing data-types can complicate the construction of pipelines. scikit-image follows an “Anything In, Anything Out” approach, whereby all functions are expected to allow input of an arbitrary data-type but, for efficiency, also get to choose their own output format. Data-type ranges are clearly defined. Floating point images are expected to have values between 0 and 1 (unsigned images) or −1 and 1 (signed images), while 8-bit images are expected to have values in {0, 1, 2, …, 255}. We provide utility functions, such as img_as_float, to easily convert between data-types.

Development practices

The purpose of scikit-image is to provide a high-quality library of powerful, diverse image processing tools free of charge and restrictions. These principles are the foundation for the development practices in the scikit-image community.

The library is licensed under the Modified BSD license, which allows unrestricted redistribution for any purpose as long as copyright notices and disclaimers of warranty are maintained. It is compatible with GPL licenses, so users of scikit-image can choose to make their code available under the GPL. However, unlike the GPL, it does not require users to open-source derivative work (BSD is not a so-called copyleft license). Thus, scikit-image can also be used in closed-source, commercial environments.

The development team of scikit-image is an open community that collaborates on the GitHub platform for issue tracking, code review, and release management.12https://github.com/scikit-imageGoogle Groups is used as a public discussion forum for user support, community development, and announcements.13https://groups.google.com/group/scikit-image

https://github.com/scikit-image

https://groups.google.com/group/scikit-image

scikit-image complies with the PEP8 coding style standard and the NumPy documentation format in order to provide a consistent, familiar user experience across the library similar to other scientific Python packages. As mentioned earlier, the data representation used is n-dimensional NumPy arrays, which ensures broad interoperability within the scientific Python ecosystem. The majority of the scikit-image API is intentionally designed as a functional interface which allows one to simply apply one function to the output of another. This modular approach also lowers the barrier of entry for new contributors, since one only needs to master a small part of the entire library in order to make an addition.

We ensure high code quality by a thorough review process using the pull request interface on GitHub.14https://help.github.com/articles/using-pull-requests (accessed 15 May 2014). This enables the core developers and other interested parties to comment on specific lines of proposed code changes, and for the proponents of the changes to update their submission accordingly. Once all the changes have been approved, they can be merged automatically. This process applies not just to outside contributions, but also to the core developers.

https://help.github.com/articles/using-pull-requests (accessed 15 May 2014).

The source code is mainly written in Python, although certain performance critical sections are implemented in Cython, an optimising static compiler for Python. scikit-image aims to achieve full unit test coverage, which is above 87% as of release 0.10 and continues to rise. A continuous integration system15https://travis-ci.org, https://coveralls.io (accessed 30 March 2014). automatically checks each commit for unit test coverage and failures on both Python 2 and Python 3. Additionally, the code is analyzed by flake8 to ensure compliance with the PEP8 coding style standards. Finally, the properties of each public function are documented thoroughly in an API reference guide, embedded as Python docstrings and accessible through the official project homepage or an interactive Python console. Short usage examples are typically included inside the docstrings, and new features are accompanied by longer, self-contained example scripts added to the narrative documentation and compiled to a gallery on the project website. We use Sphinx to automatically generate both library documentation and the website.

https://travis-ci.org, https://coveralls.io (accessed 30 March 2014).

The development master branch is fully functional at all times and can be obtained from GitHub12. The community releases major updates as stable versions approximately every six months. Major releases include new features, while minor releases typically contain only bug fixes. Going forward, users will be notified about API-breaking changes through deprecation warnings for two full major releases before the changes are applied.

Research

Often, a disproportionately large component of research involves dealing with various image data-types, color representations, and file format conversion. scikit-image offers robust tools for converting between image data-types and to do file input/output (I/O) operations. Our purpose is to allow investigators to focus their time on research, instead of expending effort on mundane low-level tasks.

The package includes a number of algorithms with broad applications across image processing research, from computer vision to medical image analysis. We refer the reader to the current API documentation for a full listing of current capabilities16http://scikit-image.org/docs/dev (accessed 30 March 2014).. In this section we illustrate two real-world usage examples of scikit-image in scientific research.

http://scikit-image.org/docs/dev (accessed 30 March 2014).

First, we consider the analysis of a large stack of images, each representing drying droplets containing nanoparticles (see Fig. 2). As the drying proceeds, cracks propagate from the edge of the drop to its center. The aim is to understand crack patterns by collecting statistical information about their positions, as well as their time and order of appearance. To improve the speed at which data is processed, each experiment, constituting an image stack, is automatically analysed without human intervention. The contact line is detected by a circular Hough transform (transform.hough_circle) providing the drop radius and its center. Then, a smaller concentric circle is drawn (draw.circle_perimeter) and used as a mask to extract intensity values from the image. Repeating the process on each image in the stack, collected pixels can be assembled to make a space–time diagram. As a result, a complex stack of images is reduced to a single image summarizing the underlying dynamic process.

Next, in regenerative medicine research, scikit-image is used to monitor the regeneration of spinal cord cells in zebrafish embryos (Fig. 3). This process has important implications for the treatment of spinal cord injuries in humans.

To understand how spinal cords regenerate in these animals, injured cords are subjected to different treatments. Neuronal precursor cells (labeled green in Fig. 3A) are normally uniformly distributed across the spinal cord. At the wound site, they have been removed. We wish to monitor the arrival of new cells at the wound site over time. In Fig. 3, we see an embryo two days after wounding, with precursor cells beginning to move back into the wound site (the site of minimum fluorescence). The measure.profile_line function measures the fluorescence along the cord, directly proportional to the number of cells. We can thus monitor the recovery process and determine which treatments prevent or accelerate recovery.

Education

scikit-image’s simple, well-documented application programming interface (API) makes it ideal for educational use, either via self-taught exploration or formal training sessions.

The online gallery of examples not only provides an overview of the functionality available in the package but also introduces many of the algorithms commonly used in image processing. This visual index also helps beginners overcome a common entry barrier: locating the class (denoising, segmentation, etc.) and name of operation desired, without being proficient with image processing jargon. For many functions, the documentation includes links to research papers or Wikipedia pages to further guide the user.

Demonstrating the broad utility of scikit-image in education, thirteen-year-old Rishab Gargeya of the Harker School won the Synopsys Silicon Valley Science and Technology Championship using scikit-image in his project, “A software based approach for automated pathology diagnosis of diabetic retinopathy in the human retina”.

We have delivered image processing tutorials using scikit-image at various annual scientific Python conferences, such as PyData 2012, SciPy India 2012, and EuroSciPy 2013. Course materials for some of these sessions are found in and are licensed under the permissive CC-BY license. These typically include an introduction to the package and provide intuitive, hands-on introductions to image processing concepts. The well documented application programming interface (API) along with tools that facilitate visualization contribute to the learning experience, and make it easy to investigate the effect of different algorithms and parameters. For example, when investigating denoising, it is easy to observe the difference between applying a median filter (filter.rank.median) and a Gaussian filter (filter.gaussian_filter), demonstrating that a median filter preserves straight lines much better.

Finally, easy access to readable source code gives users an opportunity to learn how algorithms are implemented and gives further insight into some of the intricacies of a fast Python implementation, such as indexing tricks and look-up tables.

Industry

Due to the breadth and maturity of its code base, as well as the its commercial-friendly license, scikit-image is well suited for industrial applications.

BT Imaging (http://www.btimaging.com) designs and builds tools that use photoluminescence (PL) imaging for photovoltaic applications. PL imaging can characterize the quality of multicrystalline silicon wafers by illuminating defects that are not visible under standard viewing conditions. Figure 4A shows an optical image of a silicon wafer, and Fig. 4B shows the same wafer using PL imaging. In Fig. 4C, the wafer defects and impurities have been detected through automated image analysis. scikit-image plays a key role in the image processing pipeline. For example, a Hough transform (transform.hough_line) finds the wafer edges in order to segment the wafer from the background. scikit-image is also used for feature extraction. Crystal defects (dislocations) are detected using a band-pass filter, which is implemented as a Difference of Gaussians (filter.gaussian_filter).

The image processing results are input to machine learning algorithms, which assess intrinsic wafer quality. Solar cell manufacturers can use this information to reject poor quality wafers and thereby increase the fraction of solar cells that have high solar conversion efficiency.

scikit-image is also applied in a commercial setting for biometric security applications. AICBT Ltd uses multispectral imaging to detect when a person attempts to conceal their identity using a facial mask.17http://www.aicbt.com/disguise-detection (accessed 30 March 2014). scikit-image performs file I/O (io.imread), histogram equalization (exposure.equalize_hist), and aligns a visible wavelength image with a thermal image (transform.AffineTransform). The system determines the surface temperature of a subject’s skin and detects situations where the face is being obscured.

http://www.aicbt.com/disguise-detection (accessed 30 March 2014).

Example: image registration and stitching

This section gives a step-by-step outline of how to perform panorama stitching using the primitives found in scikit-image. The full source code is at https://github.com/scikit-image/scikit-image-demos.

Data loading

The “ImageCollection” class provides an easy way of representing multiple images on disk. For efficiency, images are not read until accessed.

Figure 5A shows the Petra dataset, which displays the same facade from two different angles. For this demonstration, we will estimate a projective transformation that relates the two images. Since the outer parts of these photographs do not conform well to such a model, we select only the central parts. To further speed up the demonstration, images are downscaled to 25% of their original size.

Feature detection and matching

“Oriented FAST and rotated BRIEF” (ORB) features are detected in both images. Each feature yields a binary descriptor; those are used to find the putative matches shown in Fig. 5B.

Transform estimation

To filter the matches, we apply RANdom SAmple Consensus (RANSAC), a common method for outlier rejection. This iterative process estimates transformation models based on randomly chosen subsets of matches, finally selecting the model which corresponds best with the majority of matches. The new matches are shown in Fig. 5C.

Warping

Next, we produce the panorama itself. The first step is to find the shape of the output image by considering the extents of all warped images.

The images are now warped according to the estimated transformation model. Values outside the input images are set to −1 to distinguish the “background”.

A shift is added to ensure that both images are visible in their entirety. Note that warp takes the inverse mapping as input.

An alpha channel is added to the warped images before merging them into a single image:

The merged image is shown in Fig. 5D. Note that, while the columns are well aligned, the color intensities at the boundaries are not well matched.

Blending

To blend images smoothly we make use of the open source package Enblend, which in turn employs multi-resolution splines and Laplacian pyramids. The final panorama is shown in Fig. 5E.

Related work

In this section, we describe other libraries with similar goals to ours.

Within the scientific Python ecosystem, Mahotas contains many similar functions, and is furthermore also designed to work with NumPy arrays. The major philosophical difference between Mahotas and scikit-image is that Mahotas is almost exclusively written in templated C++, while scikit-image is written in Python and Cython. We feel that our choice lowers the barrier of entry for new contributors. However, thanks to the interoperability between the two provided by the NumPy array data format, users don’t have to choose between them, and can simply use the best components of each.

ImageJ and its batteries-included Fiji distribution are probably the most popular open-source tools for image analysis. Although Fiji’s breadth of functionality is unparalleled, it is centered around interactive, GUI use. For many developers, then, scikit-image offers several advantages. Although Fiji offers a programmable macro mode that supports many scripting languages, many of the macro functions activate GUI elements and cannot run in headless mode. This is problematic for data analysis in high-performance computing cluster environments or web backends, for example. Additionally, Fiji’s inclusive plugin policy results in an inconsistent API and variable documentation quality. Using scikit-image to develop new functionality or to build batch applications for distributed computing is often much simpler, thanks to its consistent API and the wide distribution of the scientific Python stack.

In many respects, the image processing toolbox of the Matlab environment is quite similar to scikit-image. For example, its API is mostly functional and applies to generic multidimensional numeric arrays. However, Matlab’s commercial licensing can be a significant nuisance to users. Additionally, the licensing cost increases dramatically for parallel computing, with per-worker pricing.18http://www.mathworks.com.au/products/distriben/description3.html (accessed 9 May 2014). Finally, the closed source nature of the toolbox prevents users from learning from the code or modifying it for specific purposes, which is a common necessity in scientific research. We refer readers back to the Development Practices section for a summary of the practical and philosophical advantages of our open-source licensing.

http://www.mathworks.com.au/products/distriben/description3.html (accessed 9 May 2014).

OpenCV is a BSD-licensed open-source library focused on computer vision, with a separate module for image processing. It is developed in C/C++ and the project’s main aim is to provide implementations for real-time applications. This results in fast implementations with a comparatively high barrier of entry for code study and modification. The library provides interfaces for several high-level programming languages, including Python through the NumPy-array data-type for images. The Python interface is essentially a one-to-one copy of the underlying C/C++ API, and thus image processing pipelines have to follow an imperative programming style. In contrast, scikit-image provides a Pythonic interface with the option to follow an imperative or functional approach. Beyond that, OpenCV’s image processing module is traditionally limited to 2-dimensional imagery.

The choice of image processing package depends on several factors, including speed, code quality and correctness, community support, ecosystem, feature richness, and users’ ability to contribute. Sometimes, advantages in one factor come at the cost of another. For example, our approach of writing code in a high-level language may affect performance, or our strict code review guidelines may hamper the number of features we ultimately provide. We motivate our design decisions for scikit-image in the Development Practices section, and leave readers to decide which library is right for them.

Roadmap

In many open source projects, decisions about future development are made through “rough consensus and working code”. In scikit-image there are two ways to propose new ideas: through discussion on the mailing list, or as pull requests. The latter route has the advantage of a concrete implementation to guide the conversation, and often mailing list discussions also result in a request for a proof of concept implementation. While conversations are usually led by active developers, the entire community is invited to participate. Once general agreement is reached that the proposed idea aligns with the current project goals and is feasible, work is divided on a volunteer basis. As such, the schedule for completion is often flexible.

The following goals have been identified for the next release of scikit-image:

Obtain full test coverage.

Overhaul the functions for image reading/writing.

Improve the project infrastructure, e.g., create an interactive gallery of examples.

Add support for graph-based operations.

Significantly extend higher dimensional (multi-layer) support.

We also invite readers to submit their own feature requests to the mailing list for further discussion.

Conclusion

scikit-image provides easy access to a powerful array of image processing functionality. Over the past few years, it has seen significant growth in both adoption and contribution,19https://www.ohloh.net/p/scikit-image (accessed 15 May 2014). and the team is excited to collaborate with others to see it grow even further, and to establish it the de facto library for image processing in Python.

https://www.ohloh.net/p/scikit-image (accessed 15 May 2014).

References 31

  1. 1.

    Behnel S, Bradshaw R, Citro C, Dalcin L, Seljebotn D, Smith K. Cython: the best of both worlds. Computing in Science and Engineering. 2011;13(2):31-39.

    Not in our library10.1109/mcse.2010.118

  2. 2.

    Bhatt D, Otto S, Depoister B, Fetcho JR. Cyclic amp-induced repair of zebrafish spinal circuits. Science. 2004;305:254-258.

    Not in our library10.1126/science.1098439

  3. 3.

    Bradski G. The OpenCV library. Dr. Dobb’s Journal of Software Tools. 2000;25(11):120-126.

    Not in our library

  4. 4.

    Brandl G. 2007.

    Not in our library

  5. 5.

    Burt PJ, Adelson EH. The Laplacian pyramid as a compact image code. IEEE Transactions on Communications. 1983a;31(4):532-540.

    Not in our library10.1109/tcom.1983.1095851

  6. 6.

    Burt P, Adelson E. A multiresolution spline with application to image mosaics. ACM Transactions on Graphics. 1983b;2(4):217-236.

    Not in our library10.1145/245.247

  7. 7.

    Canny J. A computational approach to edge detection. IEEE Transactions on Pattern Analysis and Machine Intelligence. 1986;8:679-714.

    Not in our library10.1109/tpami.1986.4767851

  8. 8.

    Coelho L. Mahotas: open source software for scriptable computer vision. Journal of Open Research Software. 2013;1(1).

    Not in our library10.5334/jors.ac

  9. 9.

    Cordasco I. 2010.

    Not in our library

  10. 10.

    Creative Commons. 2013.

    Not in our library

  11. 11.

    Dersch H. 2010.

    Not in our library

  12. 12.

    Fischler M, Bolles R. Random sample consensus: a paradigm for model fitting with applications to image analysis and automated cartography. Communications of the ACM. 1981;24(6):381-395.

    Not in our library10.1145/358669.358692

  13. 13.

    Haenel V, Gouillart E, Varoquaux G, scipy-lecture-notes contributors. 2014.

    Not in our library

  14. 14.
  15. 15.

    Hoffman P. The tao of IETF: a novice’s guide to the internet engineering task force. 2014.

    Not in our library

  16. 16.

    Hunter JD. Matplotlib: A 2D Graphics Environment. Computing in Science & Engineering. 2007;9(3):90-95.

    Not in our library10.1109/mcse.2007.55

  17. 17.

    Jones E, Oliphant TE, Peterson P. 2001.

    Not in our library

  18. 18.

    Microsoft. 1995.

    Not in our library

  19. 19.

    Munshi A, Leech J. 2010.

    Not in our library

  20. 20.

    Oliphant TE. Python for scientific computing. Computing in Science & Engineering. 2007;9(3):10-20.

    Not in our library10.1109/mcse.2007.58

  21. 21.

    Paeth AW, Glassner A. Proper treatment of pixels as integers. Graphics gems. 1990;254-256.

    Not in our library

  22. 22.

    Pedregosa F, Varoquaux G, Gramfort A, Michel V, Thirion B, Grisel O, Blondel M, Prettenhofer P, Weiss R, Dubourg V, Vanderplas J, Passos A, Cournapeau D, Brucher M, Perrot M, Duchesnay E. Scikit-learn: Machine Learning in Python. Journal of Machine Learning Research. 2011;12:2825-2830.

    Not in our library

  23. 23.

    Rublee E, Rabaud V, Konolige K, Bradski G. ORB: an efficient alternative to SIFT or SURF. 2011;2564-2571.

    Not in our library

  24. 24.

    Schindelin J, Arganda-Carreras I, Frise E, Kaynig V, Longair M, Pietzsch T, Preibisch S, Rueden C, Saalfeld S, Schmid B, Tinevez J-Y, White DJ, Hartenstein V, Eliceiri K, Tomancak P, Cardona A. Fiji: an open-source platform for biological-image analysis. Nature Methods. 2012;9(7):676-682.

    Not in our library10.1038/nmeth.2019

  25. 25.

    Schneider CA, Rasband WS, Eliceiri KW. NIH image to ImageJ: 25 years of image analysis. Nature Methods. 2012;9(7):671-675.

    Not in our library10.1038/nmeth.2089

  26. 26.

    science-fair.org. 2014.

    Not in our library

  27. 27.

    Thuret S, Moon L, Gage F. Therapeutic interventions after spinal cord injury. Nature Reviews Neuroscience. 2006;7:628-643.

    Not in our library10.1038/nrn1955

  28. 28.

    Van der Walt S, Colbert C, Varoquaux G. The NumPy array: a structure for efficient numerical computation. Computing in Science & Engineering. 2011;13(2):22-30.

    Not in our library10.1109/mcse.2011.37

  29. 29.

    Van der Walt S, NumPy developers. 2008.

    Not in our library

  30. 30.

    Van Rossum G, Warsaw B, Coghlan N. 2001.

    Not in our library

  31. 31.

    Wilson R. 2012.

    Not in our library

Cited by papers we hold 56

and 36 more

Reads

Read by people on this page

None yet.

Checked or read by AI through naulon

None yet.

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.

Are you an author?

Is this your paper?

Claim it to add your note and be paid when agents cite it. Free.