remove extraneous function in createluts.py (and move mc_meta reference code) #6294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The first commit avoids the
flake8
warning about an undefined variableluts
reported inmc_meta/createluts.py
(see #4163).The remaining commits move the whole
mc_meta
folder out of theskimage
package path so that it will not be distributed with scikit-image. It appears to just be there for developer reference and is not otherwise used. I chose to place it intools/precompute
which is the path used for scripts precomputing attributes for the moments computations in #6188 as well as for the proposed morphology decompositions in #6150. I think it is nice to have the scripts for cases like these available in the repository for developer reference, but they do not need to be distributed to end users.Checklist
./doc/examples
(new features only)./benchmarks
, if your changes aren't covered by anexisting benchmark
For reviewers
later.
__init__.py
.doc/release/release_dev.rst
.example, to backport to v0.19.x after merging, add the following in a PR
comment:
@meeseeksdev backport to v0.19.x
run-benchmark
label. To rerun, the labelcan be removed and then added again. The benchmark output can be checked in
the "Actions" tab.