# Transform filter memory usage
**URL:** https://discourse.paraview.org/t/transform-filter-memory-usage/12633
**Category:** ParaView Support
**Created:** [August 2, 2023, 3:12pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633 "2023-08-02T15:12:23Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@woodscn](https://discourse.paraview.org/u/woodscn)
#### Post date: [August 2, 2023, 3:12pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633/1 "2023-08-02T15:12:23Z")
I have a (rather large) set of segmented imagedata. I’d like to use the Transform filter to explode out the segmented layers, similar to this image: [https://cdn.24.co.za/files/Cms/General/d/10153/c2d878bd58aa44b1803afc3b3e473b81.jpg](https://cdn.24.co.za/files/Cms/General/d/10153/c2d878bd58aa44b1803afc3b3e473b81.jpg)
When I apply the Transform filter, Paraview suffers a crash. It’s possible I’m running out of memory, but I would have expected Transform to be a very light operation. Is it making a copy or something?
---
### Author:  [@woodscn](https://discourse.paraview.org/u/woodscn)
#### Post date: [August 2, 2023, 3:34pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633/2 "2023-08-02T15:34:20Z")
It appears that the Transform converts an Image data set to a Curvilinear structured data (makes sense). I think I know how to change the origin point in a Programmable filter. Is there an easier way to do it?
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [August 4, 2023, 12:09pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633/3 "2023-08-04T12:09:30Z")
For each individual source/filter, you can use the “Translation” property on the Display properties tab to move it.
Following shows a similar viz as yours (except with sillier dataset :))
---
### Author:  [@woodscn](https://discourse.paraview.org/u/woodscn)
#### Post date: [August 9, 2023, 7:57pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633/4 "2023-08-09T19:57:09Z")
Apparently this does weird things when volume rendering:
I think I’m likely to need to get creative to either extract a bunch of surface contours, or combine everything into a single transformed dataset, or something else.
I was surprised that changing the origin of the Image data set didn’t work as I expected. It was almost like it was a translation relative to the viewpoint of the camera, rather than relative to some global coordinate system.
---
### Author:  [@Kenneth\_Moreland](https://discourse.paraview.org/u/Kenneth_Moreland)
#### Post date: [August 11, 2023, 5:52pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633/5 "2023-08-11T17:52:10Z")
I think the weirdness you are experiencing has nothing to do with the translation. The problem is that ParaView just does not render multiple volumes together correctly. Volumes and solid surfaces work well. Multiple opaque surfaces work well together as well. But with multiple volume renderers, ParaView sort of gives up and just renders them in some arbitrary order. Thus, they are not blended correctly and some just appear on top of each other. This makes the inner shell, for example, _look_ like it is moved closer to the camera, but it is really just blended incorrectly on top of the others.
---
### Author:  [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [August 14, 2023, 1:43pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633/6 "2023-08-14T13:43:40Z")
fyi @LucasGandel
---
### Author:  [@woodscn](https://discourse.paraview.org/u/woodscn)
#### Post date: [August 14, 2023, 3:29pm UTC](https://discourse.paraview.org/t/transform-filter-memory-usage/12633/7 "2023-08-14T15:29:46Z")
I agree with your assessment. I had hoped to handle the image with volume rendering, but it’s looking like I’ll need to extract surfaces for everything, instead. In that case, the Transform filter issue won’t matter much anymore.