Add function covereage table to the documentation
See original GitHub issueIt would be good to add a page to our docs including this table comparing coverage of dask-image vs scipy ndimage functions.
Function name | SciPy ndimage | dask-image |
---|---|---|
affine_transform |
X | |
binary_closing |
X | X |
binary_dilation |
X | X |
binary_erosion |
X | X |
binary_fill_holes |
X | |
binary_hit_or_miss |
X | |
binary_opening |
X | X |
binary_propagation |
X | |
black_tophat |
X | |
center_of_mass |
X | X |
convolve |
X | X |
convolve1d |
X | |
correlate |
X | X |
correlate1d |
X | |
distance_transform_bf |
X | |
distance_transform_cdt |
X | |
distance_transform_edt |
X | |
extrema |
X | X |
find_objects |
X | |
fourier_ellipsoid |
X | |
fourier_gaussian |
X | X |
fourier_shift |
X | X |
fourier_uniform |
X | X |
gaussian_filter |
X | X |
gaussian_filter1d |
X | |
gaussian_gradient_magnitude |
X | X |
gaussian_laplace |
X | X |
generate_binary_structure |
X | |
generic_filter |
X | X |
generic_filter1d |
X | |
generic_gradient_magnitude |
X | |
generic_laplace |
X | |
geometric_transform |
X | |
grey_closing |
X | |
grey_dilation |
X | |
grey_erosion |
X | |
grey_opening |
X | |
histogram |
X | X |
imread |
X | X |
iterate_structure |
X | |
label |
X | X |
labeled_comprehension |
X | X |
laplace |
X | X |
map_coordinates |
X | |
maximum |
X | X |
maximum_filter |
X | X |
maximum_filter1d |
X | |
maximum_position |
X | X |
mean |
X | X |
median |
X | X |
median_filter |
X | X |
minimum |
X | X |
minimum_filter |
X | X |
minimum_filter1d |
X | |
minimum_position |
X | X |
morphological_gradient |
X | |
morphological_laplace |
X | |
percentile_filter |
X | X |
prewitt |
X | X |
rank_filter |
X | X |
rotate |
X | |
shift |
X | |
sobel |
X | X |
spline_filter |
X | |
spline_filter1d |
X | |
standard_deviation |
X | X |
sum |
X | X |
uniform_filter |
X | X |
uniform_filter1d |
X | |
variance |
X | X |
watershed_ift |
X | |
white_tophat |
X | |
zoom |
X |
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Advanced Code Documentation with Coverage and Unit Tests
Coverage refers to the proportion of scopes (classes, functions, modules) that have documentation included. Good coverage signifies that a codebase is well ...
Read more >Reviewing Coverage Information - Parasoft C++test 10.3.3 ...
This topic explains how to review coverage information from tests run with C++test. Coverage can be tracked for unit tests and manual or ......
Read more >Customizing Code Coverage Analysis - Visual Studio (Windows)
In Solution Explorer, on the shortcut menu of your solution, choose Add > New Item, and select XML File.
Read more >Test Coverage — Flask Documentation (2.2.x)
Flask provides a test client that simulates requests to the application and returns the response data. You should test as much of your...
Read more >Configuring Test Coverage - Code Climate
Azure Pipelines.. One way to add needed information to your Azure Pipelines is to specify environment variables for the Code Climate test reporter ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’d say so!
We have all our documentation pages in the
docs/
folder of this repository, and use ReST (restructured text) formatting.Closed via https://github.com/dask/dask-image/pull/155