You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When .select method is called on Image object it looks like bounds of newly created image are set to the input of .select method. I found that in following case:
it leads to confusion when accessing value at the same coordinates of the initial and new object.
Maybe bounds of a new object should be selected to the edge of edge pixels that got selected?
The text was updated successfully, but these errors were encountered:
I've assigned the milestone to 1.6.0 as I agree this is an important bug to address. I would consider moving it to a minor, post 1.5 release if we decide we are going to have one of those (seems likely!).
This turned out to be a pretty important bug which actually caused some distortions in a plot in my thesis. I've finally figured it out in #994, which will hopefully make it into the 1.7 release.
When
.select
method is called onImage
object it looks likebounds
of newly created image are set to the input of.select
method. I found that in following case:it leads to confusion when accessing value at the same coordinates of the initial and new object.
Maybe bounds of a new object should be selected to the edge of edge pixels that got selected?
The text was updated successfully, but these errors were encountered: