convert_color_space should return copy of array about pydicom HOT 4 CLOSED

Re-using the input array occurs by default when you have multiple frames to minimise the memory usage. If you had an input array with lots of frames then by creating a new array of equal size you may exceed your memory limits or result in a large slowdown (which is what happened for a couple of users, so we changed the behaviour). If your input array isn't that large you can pass per_frame=False which should return a new array without modifying the original.

If you're converting only a single frame then a new array is returned. The behaviour is a bit inconsistent and it could be better explained in the documentation.

from pydicom.

I have frames between 50-100 for my particular work.
I am passing per_frame=True
The problem is when i do id(original_array) and id (new_array)
It returns same id.
Which is what got me confused as it is not supposed to modify the original array.

This is quite unexpected

from pydicom.

Why is it not supposed to modify the original array? You mean because the id is the same? The input object is the same object returned when per_frame=True, just with different values (but the same dtype).

Also, as an aside, in CPython id is the memory address of the array. And it's definitely possible (I have seen it happen) that when an ndarray goes out of scope the memory can be reused if the replacement array has the same/smaller shape and dtype and therefore has the same id even though its a new object.

from pydicom.

We can close this issue.

from pydicom.