These are chat archives for thunder-project/thunder
.mean().toarray()so that is what I have been doing. It makes sense to me for
.mean()etc to return the same type of object as a
imagesof the same type.
images.squeeze()intended to only squeeze out spatial image dimensions, and not that same singleton dimension from collapsing across all images (time)? That is something that might be worth clarifying on the current docs (http://docs.thunder-project.org/). As it currently reads, I interpreted that "removing a single dimension axes from images" should also remove the single dimension time axes from all image collapsing, though it isn't written to work that way.
images.squeeze()is meant to only work on spatial dimensions, perhaps a note in the documentation directing someone to
.toarray()to remove the time dimension might be helpful. As it stands,
.toarray()doesn't show up anywhere in the documentation as a method that can be applied to images since it is in the base. There is a brief blurb in the overview mentioning
.toarray()being applied to both
images, but it isn't clear that converting it to an ndarray will also remove that additional dimension.