Closed ulupo closed 4 years ago
If we are going to change that behavior in the short term, I would just avoid having 2 breaking changes in a row and just go for the final result instead.
If we are going to change that behavior in the short term, I would just avoid having 2 breaking changes in a row and just go for the final result instead.
So is your preferred resolution of the bug we have to adapt the maximum calculation to the list scenario?
Either that or maybe just wait for the final fix. I think it's a niche bug as it's unlikely that anyone will use the transformer of list of images of different shapes in the near future.
Actually, none of the images transformer can actually deal with images of different shapes and this is not going to change in the future. I am really not sure there is a need for that capability in the first place. xD
@gtauzin thanks! The capability would be for time series of variable length for the most part, I think (since then one has the sublevel set filtration). But I agree that it is a niche bug...
Let's leave this as a "low priority" for now. Time allowing after the other PRs, I'll propose a temporary patch.
Reference issues/PRs Fixes #499.
Types of changes
Description To avoid #499, ndarray and list input are handled separately in
CubicalPersistence.fit
for the purpose of finding maximum pixel values.Checklist
flake8
to check my Python changes.pytest
to check this on Python tests.