Checks for NDData and data/subshape dimension length agreement in subtract_psf #833
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.
This PR fixes a few minor check/edge cases in
subtract_psf
.The docstrings say that
data
can be anastropy.nddata.NDData
object, but the first line previously checked fordata.ndim
which would throw anAttributeError
for anNDData
object.Currently the only check on whether the PSF can be subtracted directly from the image or if a cutout is required is
if subshape is None
, but equally true would be the case wheredata
andsubshape
are equal in both dimensions, which bypasses unnecessary code inextract_array
andadd_array
.Closes #818 (at least the case where both dimension lengths are equal; for the final edge case of one equal one non-equal dimension length
add_array
would need amending)