# Parallel rendering - Opening large raw dataset crash

**URL:** https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838
**Category:** ParaView Support
**Created:** [November 18, 2020, 5:51pm UTC](https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838 "2020-11-18T17:51:13Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![kmilo9999](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/k/cc9497/32.png) [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [November 18, 2020, 5:51pm UTC](https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838/1 "2020-11-18T17:51:14Z")

</div>

Hello,  
I am working on a cluste environment using parallel rendering.  
So far, it works with some datasets (TIFF stacks), but it crashes when I load a .raw file.  
[http://cdn.klacansky.com/open-scivis-datasets/pig\_heart/pig\_heart\_2048x2048x2612\_int16.raw](http://cdn.klacansky.com/open-scivis-datasets/pig_heart/pig_heart_2048x2048x2612_int16.raw)

I’m attaching the log in case you want to read it.[paraview\_log.txt](https://discourse.paraview.org/uploads/short-url/j4RzIoKs4NEiJm5K0sf8es9Nfhy.txt) (13.3 KB)

The file is too large to open on a single client and convert it to tiff stack.  
Any thoughts? Any ideas on how to convert it to tiff stack or something paraview can read?

Thanks

---

<div class="post-metadata">

### Author: ![jfavre](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5ac83/32.png) [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [November 19, 2020, 9:11am UTC](https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838/2 "2020-11-19T09:11:58Z")

</div>

Your file can be read, in parallel, without any issue with the following code

> reader = ImageReader(FileNames=[‘pig\_heart\_2048x2048x2612\_int16.raw’])  
> reader.DataScalarType = ‘unsigned short’  
> reader.DataExtent = [0, 2047, 0, 2047, 0, 2611]

the only issue is making sure you have enough RAM on your remote nodes and on your GPU. Reading your data on two nodes showed 10GB of memory being used on each GPU for volume rendering (default settings)

---

<div class="post-metadata">

### Author: ![kmilo9999](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/k/cc9497/32.png) [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [November 19, 2020, 3:12pm UTC](https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838/3 "2020-11-19T15:12:56Z")

</div>

Hello @jfavre  
It is a programable filter, correct?

---

<div class="post-metadata">

### Author: ![jfavre](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5ac83/32.png) [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [November 19, 2020, 3:15pm UTC](https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838/4 "2020-11-19T15:15:22Z")

</div>

no, this is not intended for a programmable filter. This is part of a regular pipeline. This code would be for the embedded python shell.

---

<div class="post-metadata">

### Author: ![kmilo9999](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/k/cc9497/32.png) [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [November 19, 2020, 9:10pm UTC](https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838/5 "2020-11-19T21:10:04Z")

</div>

It works! Thanks @jfavre.  
Do you know why it wasnt opening using the regular file-\>open option?

---

<div class="post-metadata">

### Author: ![jfavre](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5ac83/32.png) [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [November 19, 2020, 9:16pm UTC](https://discourse.paraview.org/t/parallel-rendering-opening-large-raw-dataset-crash/5838/6 "2020-11-19T21:16:38Z")

</div>

I can only guess…perhaps the wrong reader was inadvertently chosen, or the extents or data scalar type was wrong…Anyway, problem solved. 😀
