Re: [Paraview] Can I generate a single file that contains data and filter settings?

[Wyatt Spear]

The data that I'm generating has a set of scalar values for every point in
the 2D matrix, so a single data row looks like
xcoord, ycoord, zcord(probably superfluous), scalar1, scalar2,...scalarN
Since the data in your example is being rendered as an image directly I'm
not sure how I could incorporate different scalar data which can be
selected from the UI, as I can when running the table-to-points filter on a
loaded CSV file.

Is there a way to have a python macro cause ParaView to request a file
selection through the UI? Then I could have this single macro loaded and it
could process any CSV file I select.

Thanks,
Wyatt

On Wed, Jan 31, 2018 at 8:23 AM, Cory Quammen 
wrote:

> Wyatt,
>
> Here's a simple script that sets up a 200 x 200 image data object like
> you might use for displaying a heat map.
>
>  import the simple module from the paraview
> from paraview.simple import *
>  disable automatic camera reset on 'Show'
> paraview.simple._DisableFirstRenderCameraReset()
>
> # Create a 2D image data object
> from paraview import vtk
> vtk_image = vtk.vtkImageData()
> vtk_image.SetDimensions(200, 200, 1) # Your size may vary
>
> # Wrap data in numpy interface
> from vtk.numpy_interface import dataset_adapter as dsa
> image = dsa.WrapDataObject(vtk_image)
>
> # Create numpy array. Set your data here
> import numpy as np
> arr = np.zeros(200*200)
>
> # Set the data in the image object
> image.PointData.append(arr, 'myarray')
>
> # Now set up a ParaView proxy for the image data
> tp = PVTrivialProducer()
> tp.GetClientSideObject().SetOutput(vtk_image)
> Show(tp)
>
>
> # Set up filters, display options, etc. below
>
>
> You can modify it as needed to set up your data array as a numpy array.
>
> Hope that helps,
> Cory
>
> On Mon, Jan 29, 2018 at 3:27 PM, Wyatt Spear 
> wrote:
> > I think the python scripting with embedded data is worth a try. I'm not
> > familiar with the built-in vs other server modes so I'm not sure what
> kind
> > of restrictions that entails.  Probably my ultimate goal is to build a
> > reader plugin that will parse the data out of my application's native
> format
> > but generating a script seems like a decent interim solution.
> >
> > Thanks,
> > Wyatt
> >
> > On Mon, Jan 29, 2018 at 5:57 AM, Cory Quammen 
> > wrote:
> >>
> >> Wyatt,
> >>
> >> ParaView provides extensive Python scriptability. One solution is to
> >> write out a Python script from your program. Within the Pythons
> >> script, you set up the data, set up filters and modify visualization
> >> settings just as you wish. Once it is loaded, you can continue to
> >> explore your data by creating new filters, changing visualization
> >> parameters, and so on.
> >>
> >> Creating example Python scripts is easy using the Trace functionality
> >> (Tools menu -> Start Trace) - you just interact with the UI and the
> >> equivalent Python operations will be written to the trace file. Use
> >> such a trace as a basis for what is written from your program.
> >>
> >> To save the data to the Python script and then load it is a different
> >> use case from what we typical support, but I think it is doable. It
> >> would just look a little ugly (and it would only work in built-in
> >> server mode). Basically, you could write out your data in a NumPy
> >> array within the script, as if you were entering the array information
> >> by hand, then provide that data to what's called a TrivialProducer
> >> source. This source would stand in place of a reader. There is a
> >> little bit of code required to do that that isn't super obvious -
> >> before sketching it out, would this approach work for your needs?
> >>
> >> Thanks,
> >> Cory
> >>
> >>
> >>
> >> On Sun, Jan 28, 2018 at 10:10 PM, Wyatt Spear 
> >> wrote:
> >> > Thanks, I'll take a look at this. My use case is pretty severely
> >> > underutilizing ParaView's capabilities though. I'm rendering very
> large
> >> > multi-variable heat maps. So color mapped 2d points are all I need
> >> > rendered,
> >> > (until I can figure out how to map glyph height to another variable).
> >> >
> >> > =Wyatt
> >> >
> >> >
> >> > On Sat, Jan 27, 2018 at 8:52 AM Samuel Key 
> >> > wrote:
> >> >>
> >> >> Wyatt--
> >> >>
> >> >> While ParaView can read CSV files and subsequently generate images,
> the
> >> >> CSV format for simulation results limits the functionality available
> to
> >> >> you
> >> >> in ParaView. My suggestion is that you write your simulation results
> in
> >> >> a
> >> >> format that contains geometry information, as well as, Point and Cell
> >> >> centered values like displacement, velocity, acceleration,
> temperature,
> >> >> concentrations, volume fractions, et cetera.
> >> >>
> >> >> The attached document is a good place to start. (This document is
> very
> >> >> concise and very complete, but the information is only written down
> >> >> once. As
> >> >> a result, the format information is sometimes not located where you
> >> >> need
> >> >> it.)
> >> >>
> >> >> If your simulat

Re: [Paraview] issue with savescreenshot in pvpython when having two renderviews

[Cory Quammen]

Hi Jens,

I was not able to reproduce the missing data in the bottom render view.

As for the legend size changing, I explained it and how to fix it in
your issue https://gitlab.kitware.com/paraview/paraview/issues/17938

Thanks,
Cory


On Wed, Jan 17, 2018 at 1:37 AM, Jens Dahl Kunoy
 wrote:
> Hi,
> I want to compare two vtk files by having two render views and dump these
> two renderviews into a single image file. The py script recorded by trace
> works from GUI but not from the command line using pvpython. Using pvpython
> the second renderview has no data and there is also other artefacts. You can
> see the difference in the attached two files.
>
> I put it up as an issue here:
> https://gitlab.kitware.com/paraview/paraview/issues/17938
>
> Any ideas?
>
> BR
> Jens
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1

[Cory Quammen]

Ufuk,

Thanks for the report. Is there a reliable way to reproduce the
behavior that you can share?

Best,
Cory

On Wed, Jan 31, 2018 at 12:16 PM, Ufuk Turuncoglu
 wrote:
> I don't know it is related or not. I have very similar behavior under 5.4.1. 
> If i save a state and load it later, Polar Axes show up and i need to disable 
> it from the properties panel. Somehow, ParaView loads Polar Axes even if it 
> is not activated in the original pipeline. It might help to find the source 
> of the issue.
>
> Best Regards,
>
> --ufuk
>
> - Original Message -
> From: "Cory Quammen" 
> To: "Joe Ping-Lin Hsiao" 
> Cc: "paraview" 
> Sent: Wednesday, January 31, 2018 6:44:45 PM
> Subject: Re: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1
>
> Hmm, that's weird. The Polar Axes should be off by default. Do the
> Polar Axes appear when creating a Sphere source?
>
> You should be able to force it off by adding the following line to the
> loadFile() function in your script:
>
> display.PolarAxes.Visibility = 0
>
> HTH,
> Cory
>
> On Tue, Jan 23, 2018 at 4:40 PM, Joe Ping-Lin Hsiao  wrote:
>> Yes exactly.
>>
>> On Tue, Jan 23, 2018 at 3:47 PM, Cory Quammen 
>> wrote:
>>>
>>> Hi Joe,
>>>
>>> Are you referring to the circular (polar axes) in the image? It says
>>> 90.0 deg, 45.0 deg., etc.
>>>
>>> Thanks,
>>> Cory
>>>
>>> On Tue, Jan 23, 2018 at 3:31 PM, Joe Ping-Lin Hsiao 
>>> wrote:
>>> > The attached image shows the unexpected measure with text. I tested two
>>> > versions of ParaView and it only happens in 5.4.1 but not 5.0.1.
>>> >
>>> > 180 stacks are loaded and set to volume rendering by my Python script,
>>> > which
>>> > is also attached.
>>> >
>>> > Thanks,
>>> > Joe
>>> >
>>> > ___
>>> > Powered by www.kitware.com
>>> >
>>> > Visit other Kitware open-source projects at
>>> > http://www.kitware.com/opensource/opensource.html
>>> >
>>> > Please keep messages on-topic and check the ParaView Wiki at:
>>> > http://paraview.org/Wiki/ParaView
>>> >
>>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>>> >
>>> > Follow this link to subscribe/unsubscribe:
>>> > https://paraview.org/mailman/listinfo/paraview
>>> >
>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> Staff R&D Engineer
>>> Kitware, Inc.
>>
>>
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Save Animation option in ParaView 5.4.0 vs 5.3.0

[Van Moer, Mark W]

Hi David,

Sorry for the delayed response, thanks for looking at this. I subscribed to the 
issue in GitLab.

Mark


From: David E DeMarle [mailto:dave.dema...@kitware.com]
Sent: Friday, January 26, 2018 11:59 AM
To: Van Moer, Mark W 
Cc: ParaView 
Subject: Re: [Paraview] Save Animation option in ParaView 5.4.0 vs 5.3.0

Hey Mark,

Looks like we took that out as part of the revamp described here:
https://gitlab.kitware.com/paraview/paraview/issues/15917

Specifically this merge request took out the "No. Frames" entry.
https://gitlab.kitware.com/paraview/paraview/merge_requests/896
because, at least at that time, apparently the control didn't do anything at 
all.

A 1 commit merge request that restores the widget and hooks it up to do what it 
apparently did at one time is
here. https://gitlab.kitware.com/paraview/paraview/merge_requests/2197

David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Jan 26, 2018 at 10:17 AM, Van Moer, Mark W 
mailto:mvanm...@illinois.edu>> wrote:
Hello,

In ParaView 5.3.0 and earlier, when Animation mode was Snap to TimeSteps, in 
the Save Animation dialog box there was an option for No. of Frames / timestep. 
This doesn’t show up in the 5.4.0 dialog box. Was this just moved or was it 
removed completely?

My use case for this is a data set with 25 timesteps, each of which is on the 
order of either 5 minutes or 30 minutes apart in real world time. I’d render 30 
frames / timestep to get a 25 second movie to show each discrete timestep for 
one second. The video should show those discrete jumps in time and not use 
interpolation.

I can do the frame replication in BASH but it was handy to have that option.

Thanks,
Mark

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1

[Ufuk Turuncoglu]

I don't know it is related or not. I have very similar behavior under 5.4.1. If 
i save a state and load it later, Polar Axes show up and i need to disable it 
from the properties panel. Somehow, ParaView loads Polar Axes even if it is not 
activated in the original pipeline. It might help to find the source of the 
issue.

Best Regards,

--ufuk

- Original Message -
From: "Cory Quammen" 
To: "Joe Ping-Lin Hsiao" 
Cc: "paraview" 
Sent: Wednesday, January 31, 2018 6:44:45 PM
Subject: Re: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1

Hmm, that's weird. The Polar Axes should be off by default. Do the
Polar Axes appear when creating a Sphere source?

You should be able to force it off by adding the following line to the
loadFile() function in your script:

display.PolarAxes.Visibility = 0

HTH,
Cory

On Tue, Jan 23, 2018 at 4:40 PM, Joe Ping-Lin Hsiao  wrote:
> Yes exactly.
>
> On Tue, Jan 23, 2018 at 3:47 PM, Cory Quammen 
> wrote:
>>
>> Hi Joe,
>>
>> Are you referring to the circular (polar axes) in the image? It says
>> 90.0 deg, 45.0 deg., etc.
>>
>> Thanks,
>> Cory
>>
>> On Tue, Jan 23, 2018 at 3:31 PM, Joe Ping-Lin Hsiao 
>> wrote:
>> > The attached image shows the unexpected measure with text. I tested two
>> > versions of ParaView and it only happens in 5.4.1 but not 5.0.1.
>> >
>> > 180 stacks are loaded and set to volume rendering by my Python script,
>> > which
>> > is also attached.
>> >
>> > Thanks,
>> > Joe
>> >
>> > ___
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at:
>> > http://paraview.org/Wiki/ParaView
>> >
>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > https://paraview.org/mailman/listinfo/paraview
>> >
>>
>>
>>
>> --
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.
>
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Paraview Not Reading Some Fields in Dataset

[Andy Bauer]

Glad to hear that you're able to read the file correctly now -- thanks for
reporting back to everyone!

On Wed, Jan 31, 2018 at 11:07 AM, Tate Fanning  wrote:

> I found a solution to the problem. The CFD code was writing the offsets
> incorrectly. When I adjust them manually, Paraview can read the file just
> fine.
>
> This thread goes into a little more detail: https://www.cfd-
> online.com/Forums/paraview/198220-paraview-not-reading-
> some-fields-dataset.html
>
> On Tue, Jan 30, 2018 at 1:24 PM, Andy Bauer 
> wrote:
>
>> It looks like you have integer overflow (https://en.wikipedia.org/wiki
>> /Integer_overflow). I'd suggest using a datatype with more precision and
>> see if that fixes the issue.
>>
>> On Tue, Jan 30, 2018 at 3:15 PM, Tate Fanning 
>> wrote:
>>
>>> I've output a vtu file from a CFD code. When trying to load the dataset
>>> into Paraview I get the following errors:
>>>
>>> [CODE]Error reading uncompressed binary data header. Read 0 of 4 bytes.
>>> ERROR: In 
>>> C:\bbd\7cc78367\source-paraview\VTK\IO\XMLParser\vtkXMLDataParser.cxx,
>>> line 609 vtkXMLDataParser (009CC7674520): Error reading uncompressed
>>> binary data header. Read 0 of 4 bytes.
>>>
>>> Cannot read point data array "Cyl_Velocity" from PointData in piece 0.
>>> The data array in the element may be too short. ERROR: In
>>> C:\bbd\7cc78367\source-paraview\VTK\IO\XML\vtkXMLDataReader.cxx, line
>>> 443 vtkXMLUnstructuredGridReader (009C837CFCE0): Cannot read point data
>>> array "Cyl_Velocity" from PointData in piece 0. The data array in the
>>> element may be too short.[/CODE]
>>>
>>> If I ask Paraview to not read the offending arrays, it reads the other
>>> arrays in fine. From these errors, it seems the data file has some issues
>>> with a few specific arrays.
>>>
>>> Upon inspection of the first part of the vtu file, the offending arrays
>>> (Cyl_Velocity and Rel_Velocity) have negative offsets.
>>>
>>> [CODE]>> byte_order="BigEndian">
>>> 
>>> 
>>>   
>>> >> NumberOfComponents="3" format="appended" offset="   0" />
>>>   
>>>   
>>> >> offset="   236520940" />
>>> >> offset="   541266416" />
>>> 
>>>   
>>>   
>>>  >> offset="   617452792" />
>>>  
>>>  >> offset="   775133424" />
>>>  >> offset="   853973740" />
>>>  >> offset="   932814056" />
>>>  >> offset="  1011654372" />
>>>  >> offset="  1090494688" />
>>>  >> offset="  1169335004" />
>>>  
>>>  >> offset="  1327015636" />
>>>  >> offset="  1405855952" />
>>>  >> offset="  1484696268" />
>>>  >> offset="  1563536584" />
>>>  >> offset="  1642376900" />
>>>  >> offset="  1721217216" />
>>>  >> offset="  1800057532" />
>>>  >> offset="  1878897848" />
>>>  >> offset="  1957738164" />
>>>  >> NumberOfComponents="3" format="appended" offset="  2036578480
>>> <(203)%20657-8480>" />
>>>  >> NumberOfComponents="3" format="appended" offset=" -2021867876" />
>>>  >> NumberOfComponents="3" format="appended" offset=" -1785346936" />
>>>   
>>> [/CODE]
>>>
>>> The CFD code also can output data files for a specific surface. When I
>>> load one of those into Paraview, it has no issues with any data array in
>>> that file, and everything works fine.
>>>
>>> Upon inspection of the first part of a single surface vtu file with no
>>> issues, no array has a negative offset.
>>>
>>> [CODE] >> byte_order="BigEndian">
>>> 
>>> 
>>>   
>>> >> NumberOfComponents="3" format="appended" offset="   0" />
>>>   
>>>   
>>> >> offset=" 4224604" />
>>> >> offset=" 7017056" />
>>> 
>>>   
>>>   
>>>  >> offset=" 8413288" />
>>>  
>>>  >> offset="11229696" />
>>>  >> offset="12637900" />
>>>  >> offset="14046104" />
>>>  >> offset="15454308" />
>>>  >> offset="16862512" />
>>>  >> offset="18270716" />
>>>  
>>>  >> offset="21087124" />
>>>  >> offset="22495328" />
>>>  >> offset="23903532" />
>>>  >> offset="25311736" />
>>>  >> offset="26719940" />
>>>  >> offset="28128144" />
>>>  >> offset="29536348" />
>>>  >> offset="30944552" />
>>>  >> offset="32352756" />
>>>  >> NumberOfComponents="3" format="appended" offset="33760960" />
>>>  >> NumberOfComponents="3" format="appended" offset="37985564" />
>>>  >> NumberOfComponents="3" format="appended" offset="42210168" />
>>>   
>>> [/CODE]
>>>
>>> So I think the offset sign is relevant to my problem, but I don't really
>>> know what it means or how to fix it. Does anyone know what I can do to fix
>>> my data set, or at least know what the underlying problem is?
>>>
>>> Thank yo

Re: [Paraview] Can I generate a single file that contains data and filter settings?

[Cory Quammen]

Wyatt,

Here's a simple script that sets up a 200 x 200 image data object like
you might use for displaying a heat map.

 import the simple module from the paraview
from paraview.simple import *
 disable automatic camera reset on 'Show'
paraview.simple._DisableFirstRenderCameraReset()

# Create a 2D image data object
from paraview import vtk
vtk_image = vtk.vtkImageData()
vtk_image.SetDimensions(200, 200, 1) # Your size may vary

# Wrap data in numpy interface
from vtk.numpy_interface import dataset_adapter as dsa
image = dsa.WrapDataObject(vtk_image)

# Create numpy array. Set your data here
import numpy as np
arr = np.zeros(200*200)

# Set the data in the image object
image.PointData.append(arr, 'myarray')

# Now set up a ParaView proxy for the image data
tp = PVTrivialProducer()
tp.GetClientSideObject().SetOutput(vtk_image)
Show(tp)


# Set up filters, display options, etc. below


You can modify it as needed to set up your data array as a numpy array.

Hope that helps,
Cory

On Mon, Jan 29, 2018 at 3:27 PM, Wyatt Spear  wrote:
> I think the python scripting with embedded data is worth a try. I'm not
> familiar with the built-in vs other server modes so I'm not sure what kind
> of restrictions that entails.  Probably my ultimate goal is to build a
> reader plugin that will parse the data out of my application's native format
> but generating a script seems like a decent interim solution.
>
> Thanks,
> Wyatt
>
> On Mon, Jan 29, 2018 at 5:57 AM, Cory Quammen 
> wrote:
>>
>> Wyatt,
>>
>> ParaView provides extensive Python scriptability. One solution is to
>> write out a Python script from your program. Within the Pythons
>> script, you set up the data, set up filters and modify visualization
>> settings just as you wish. Once it is loaded, you can continue to
>> explore your data by creating new filters, changing visualization
>> parameters, and so on.
>>
>> Creating example Python scripts is easy using the Trace functionality
>> (Tools menu -> Start Trace) - you just interact with the UI and the
>> equivalent Python operations will be written to the trace file. Use
>> such a trace as a basis for what is written from your program.
>>
>> To save the data to the Python script and then load it is a different
>> use case from what we typical support, but I think it is doable. It
>> would just look a little ugly (and it would only work in built-in
>> server mode). Basically, you could write out your data in a NumPy
>> array within the script, as if you were entering the array information
>> by hand, then provide that data to what's called a TrivialProducer
>> source. This source would stand in place of a reader. There is a
>> little bit of code required to do that that isn't super obvious -
>> before sketching it out, would this approach work for your needs?
>>
>> Thanks,
>> Cory
>>
>>
>>
>> On Sun, Jan 28, 2018 at 10:10 PM, Wyatt Spear 
>> wrote:
>> > Thanks, I'll take a look at this. My use case is pretty severely
>> > underutilizing ParaView's capabilities though. I'm rendering very large
>> > multi-variable heat maps. So color mapped 2d points are all I need
>> > rendered,
>> > (until I can figure out how to map glyph height to another variable).
>> >
>> > =Wyatt
>> >
>> >
>> > On Sat, Jan 27, 2018 at 8:52 AM Samuel Key 
>> > wrote:
>> >>
>> >> Wyatt--
>> >>
>> >> While ParaView can read CSV files and subsequently generate images, the
>> >> CSV format for simulation results limits the functionality available to
>> >> you
>> >> in ParaView. My suggestion is that you write your simulation results in
>> >> a
>> >> format that contains geometry information, as well as, Point and Cell
>> >> centered values like displacement, velocity, acceleration, temperature,
>> >> concentrations, volume fractions, et cetera.
>> >>
>> >> The attached document is a good place to start. (This document is very
>> >> concise and very complete, but the information is only written down
>> >> once. As
>> >> a result, the format information is sometimes not located where you
>> >> need
>> >> it.)
>> >>
>> >> If your simulations are concerned with the deformation of 3-D solids
>> >> and
>> >> structures, I can provide you with FORTRAN95 routines that you can use
>> >> to
>> >> write VTK-formatted simulation results.
>> >>
>> >> Once you can generate VTK-formatted datum sets, The File > Save State
>> >> command will generate *.pvsm files that will let you "recreate" a
>> >> previously
>> >> constructed Browser Pipeline. (The PV *.pvsm reader gives you the
>> >> opportunity to select a different datum set.)
>> >>
>> >> There is a small two-cell mesh file attached that might be helpful to
>> >> you
>> >> when constructing a VTK-formatted file writer in your application.
>> >>
>> >> --Sam
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On 1/27/2018 8:46 AM, Wyatt Spear wrote:
>> >>
>> >> Greetings,
>> >>
>> >> Currently I am using my own application to generate a simple CSV file
>> >> which can be loaded up in ParaView. I then create the visua

Re: [Paraview] Paraview Not Reading Some Fields in Dataset

[Tate Fanning]

I found a solution to the problem. The CFD code was writing the offsets
incorrectly. When I adjust them manually, Paraview can read the file just
fine.

This thread goes into a little more detail:
https://www.cfd-online.com/Forums/paraview/198220-paraview-not-reading-some-fields-dataset.html

On Tue, Jan 30, 2018 at 1:24 PM, Andy Bauer  wrote:

> It looks like you have integer overflow (https://en.wikipedia.org/
> wiki/Integer_overflow). I'd suggest using a datatype with more precision
> and see if that fixes the issue.
>
> On Tue, Jan 30, 2018 at 3:15 PM, Tate Fanning  wrote:
>
>> I've output a vtu file from a CFD code. When trying to load the dataset
>> into Paraview I get the following errors:
>>
>> [CODE]Error reading uncompressed binary data header. Read 0 of 4 bytes.
>> ERROR: In 
>> C:\bbd\7cc78367\source-paraview\VTK\IO\XMLParser\vtkXMLDataParser.cxx,
>> line 609 vtkXMLDataParser (009CC7674520): Error reading uncompressed
>> binary data header. Read 0 of 4 bytes.
>>
>> Cannot read point data array "Cyl_Velocity" from PointData in piece 0.
>> The data array in the element may be too short. ERROR: In
>> C:\bbd\7cc78367\source-paraview\VTK\IO\XML\vtkXMLDataReader.cxx, line
>> 443 vtkXMLUnstructuredGridReader (009C837CFCE0): Cannot read point data
>> array "Cyl_Velocity" from PointData in piece 0. The data array in the
>> element may be too short.[/CODE]
>>
>> If I ask Paraview to not read the offending arrays, it reads the other
>> arrays in fine. From these errors, it seems the data file has some issues
>> with a few specific arrays.
>>
>> Upon inspection of the first part of the vtu file, the offending arrays
>> (Cyl_Velocity and Rel_Velocity) have negative offsets.
>>
>> [CODE]> byte_order="BigEndian">
>> 
>> 
>>   
>> > NumberOfComponents="3" format="appended" offset="   0" />
>>   
>>   
>> > offset="   236520940" />
>> > offset="   541266416" />
>> 
>>   
>>   
>>  
>>  
>>  
>>  
>>  
>>  > offset="  1011654372" />
>>  > offset="  1090494688" />
>>  > offset="  1169335004" />
>>  
>>  > offset="  1327015636" />
>>  > offset="  1405855952" />
>>  > offset="  1484696268" />
>>  > offset="  1563536584" />
>>  > offset="  1642376900" />
>>  > offset="  1721217216" />
>>  > offset="  1800057532" />
>>  > offset="  1878897848" />
>>  > offset="  1957738164" />
>>  > format="appended" offset="  2036578480 <(203)%20657-8480>" />
>>  > NumberOfComponents="3" format="appended" offset=" -2021867876" />
>>  > NumberOfComponents="3" format="appended" offset=" -1785346936" />
>>   
>> [/CODE]
>>
>> The CFD code also can output data files for a specific surface. When I
>> load one of those into Paraview, it has no issues with any data array in
>> that file, and everything works fine.
>>
>> Upon inspection of the first part of a single surface vtu file with no
>> issues, no array has a negative offset.
>>
>> [CODE] > byte_order="BigEndian">
>> 
>> 
>>   
>> > NumberOfComponents="3" format="appended" offset="   0" />
>>   
>>   
>> > offset=" 4224604" />
>> > offset=" 7017056" />
>> 
>>   
>>   
>>  
>>  
>>  
>>  
>>  
>>  > offset="15454308" />
>>  > offset="16862512" />
>>  > offset="18270716" />
>>  
>>  > offset="21087124" />
>>  > offset="22495328" />
>>  > offset="23903532" />
>>  > offset="25311736" />
>>  > offset="26719940" />
>>  > offset="28128144" />
>>  > offset="29536348" />
>>  > offset="30944552" />
>>  > offset="32352756" />
>>  > format="appended" offset="33760960" />
>>  > NumberOfComponents="3" format="appended" offset="37985564" />
>>  > NumberOfComponents="3" format="appended" offset="42210168" />
>>   
>> [/CODE]
>>
>> So I think the offset sign is relevant to my problem, but I don't really
>> know what it means or how to fix it. Does anyone know what I can do to fix
>> my data set, or at least know what the underlying problem is?
>>
>> Thank you.
>>
>> --
>> *Tate Fanning*
>> Ph.D. Candidate
>> Turbomachinery Research Lab
>> BYU Mechanical Engineering
>> 360-953-7457 <(360)%20953-7457>
>> t8fann...@gmail.com
>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://para

Re: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1

[Cory Quammen]

Hmm, that's weird. The Polar Axes should be off by default. Do the
Polar Axes appear when creating a Sphere source?

You should be able to force it off by adding the following line to the
loadFile() function in your script:

display.PolarAxes.Visibility = 0

HTH,
Cory

On Tue, Jan 23, 2018 at 4:40 PM, Joe Ping-Lin Hsiao  wrote:
> Yes exactly.
>
> On Tue, Jan 23, 2018 at 3:47 PM, Cory Quammen 
> wrote:
>>
>> Hi Joe,
>>
>> Are you referring to the circular (polar axes) in the image? It says
>> 90.0 deg, 45.0 deg., etc.
>>
>> Thanks,
>> Cory
>>
>> On Tue, Jan 23, 2018 at 3:31 PM, Joe Ping-Lin Hsiao 
>> wrote:
>> > The attached image shows the unexpected measure with text. I tested two
>> > versions of ParaView and it only happens in 5.4.1 but not 5.0.1.
>> >
>> > 180 stacks are loaded and set to volume rendering by my Python script,
>> > which
>> > is also attached.
>> >
>> > Thanks,
>> > Joe
>> >
>> > ___
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at:
>> > http://paraview.org/Wiki/ParaView
>> >
>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > https://paraview.org/mailman/listinfo/paraview
>> >
>>
>>
>>
>> --
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.
>
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] ParaView 5.4.1 | Segmentation Fault

[Utkarsh Ayachit]

> In addition, execution of './paraview --mesa' works, meaning there's an
> issue with the graphics drivers?

That'd be my guess.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] ParaView 5.4.1 | Segmentation Fault

[Fastl, Thomas]

Dear Utkarsh,


I really appreciate your immediate response, thanks! I've check the graphics 
drivers as you suggested:


tf13@bioeng087-pc:~$ glxinfo
name of display: :0
X Error of failed request:  GLXBadContext
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  6 (X_GLXIsDirect)
Serial number of failed request:  26
Current serial number in output stream:  26

In addition, execution of './paraview --mesa' works, meaning there's an issue 
with the graphics drivers?

Best, Thomas


From: Utkarsh Ayachit 
Sent: Wednesday, January 31, 2018 12:48
To: Fastl, Thomas
Cc: paraview@paraview.org
Subject: Re: [Paraview] ParaView 5.4.1 | Segmentation Fault

Thomas,

Check your graphics drivers. You can use tools like `glxinfo` to tell
you which OpenGL version is supported. ParaView now requires 3.2 or
newer. If you cannot upgrade your graphics drivers, you can use
software OpenGL implementation packaged by ParaView binaries as
follows:

.../paraview --mesa

Hope that helps,
Utkarsh

On Wed, Jan 31, 2018 at 7:45 AM, Fastl, Thomas  wrote:
> Dear Community,
>
>
> I've recently upgraded to ParaView 5.4.1 since ParaView 5.0.0 stopped
> working on my workstation. Therefore, I've downloaded and unpacked
> ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz, however, receive the
> following error message upon execution:
>
>
> Warning: In
> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 838
> vtkGenericOpenGLRenderWindow (0x3846580): VTK is designed to work with
> OpenGL version 3.2 but it appears it has been given a context that does not
> support 3.2. VTK will run in a compatibility mode designed to work with
> earlier versions of OpenGL but some features may not work.
>
> Segmentation fault
>
>
> I'm running Ubuntu 14.04 on my workstation and should probably mention that
> I receive this error message right after execution of 'paraview', i.e., the
> Graphical User Interface never appears. Does anybody have a similar problem
> or know on how to resolve this issue? Thanks!
>
>
> Best, Thomas
>
>
>
> ___
> Powered by 
> https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7C993d45e7786e4b19834a08d568a8fcb3%7C8370cf1416f34c16b83c724071654356%7C0&sdata=SZhKd7MqGivGN2iRcdVgKqBlhOMLmAbiHBu2%2F9QpIZ8%3D&reserved=0
>
> Visit other Kitware open-source projects at
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7C993d45e7786e4b19834a08d568a8fcb3%7C8370cf1416f34c16b83c724071654356%7C0&sdata=w7OoCQ4j4nl9JlacJ1gclyH6xjS%2BlyOiCiWsmLMwZLk%3D&reserved=0
>
> Please keep messages on-topic and check the ParaView Wiki at:
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7C993d45e7786e4b19834a08d568a8fcb3%7C8370cf1416f34c16b83c724071654356%7C0&sdata=iztT%2FuRsTwGjJqFAVDrjVC8shkWcotLFyRIAtwqpSL8%3D&reserved=0
>
> Search the list archives at: 
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7C993d45e7786e4b19834a08d568a8fcb3%7C8370cf1416f34c16b83c724071654356%7C0&sdata=XWGfA1xajWrFh9Q0GH4lbl8eq0PR6M3kMhzA3FCUJyY%3D&reserved=0
>
> Follow this link to subscribe/unsubscribe:
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fparaview.org%2Fmailman%2Flistinfo%2Fparaview&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7C993d45e7786e4b19834a08d568a8fcb3%7C8370cf1416f34c16b83c724071654356%7C0&sdata=vZDJ7bgbhWBC9oSri22TWmW3EE9XARzz5sP%2F31FXmVg%3D&reserved=0
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Extracting data on the surface of a block?

[Steytler, Louis Louw]

Utkarsh,

Thanks very much, that helped very much!

Louis Steytler
Department of Mechanical Science and Engineering
University of Illinois at Urbana-Champaign
1206 West Green Street
Urbana, Il 61801
steyt...@illinois.edu

From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: 30 January 2018 11:25 AM
To: Steytler, Louis Louw
Cc: paraview@paraview.org
Subject: Re: [Paraview] Extracting data on the surface of a block?

Loius,

Looks like what you have is quite reasonable. You can drop the
"Extract Surface" filter and simply connect the "Plot On Intersection
Curves" to the "Merge Blocks" as the "Plot On .." filter does an
"Extract Surface" internally.

Another option, if you want finer control over the sampling resolution
would be to use the "Resample With Dataset" filter" with a custom
source that correponds to the sampling locations. I created one by
using a Sphere source and then slicing it. State attached. By changing
the resolution of the Sphere, you can change the refinement.

Hope that helps

Utkarsh



On Sat, Jan 27, 2018 at 12:16 PM, Steytler, Louis Louw
 wrote:
> Utkarsh,
>
> The attached state file should work with the data I sent.
>
> Thanks very much,
>
> Louis Steytler
> Department of Mechanical Science and Engineering
> University of Illinois at Urbana-Champaign
> 1206 West Green Street
> Urbana, Il 61801
> steyt...@illinois.edu
> 
> From: ParaView [paraview-boun...@paraview.org] on behalf of Steytler, Louis
> Louw [steyt...@illinois.edu]
> Sent: 26 January 2018 06:27 AM
> To: Utkarsh Ayachit
>
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] Extracting data on the surface of a block?
>
> Utkarsh,
>
> I forget, meant to say blocks 1 and 2 represent the drop. I actually
> extracted and merged these two in ParaView.
>
> Will send a state file soon, apologies for late, I have been traveling the
> past two days.
>
> Thanks again,
>
> Louis Steytler
> Department of Mechanical Science and Engineering
> University of Illinois at Urbana-Champaign
> 1206 West Green Street
> Urbana, IL 61801
> steyt...@illinois.edu
>
> On 24 Jan 2018 8:50 AM, Utkarsh Ayachit  wrote:
>
> Louis,
>
> Can you also attach a state file for the vis you're generating
> currently, so I get a starting point? I am not sure which block is the
> oil drop.
>
> Thanks,
> Utkarsh
>
> On Tue, Jan 23, 2018 at 8:12 PM, Steytler, Louis Louw
>  wrote:
>> Hi Utkarsh,
>>
>> My data file is rather large, but here is a link to the data:
>>
>> https://uofi.box.com/s/u4hpipt8kbo0u3oxhz92xeya75kzf6kd
>>
>> Please let me know if this is too large and I can try to send a smaller
>> version.
>>
>> I have been using "save data". It seems I have data sets under the
>> "Composite Data Set Index" list in the PlotOnIntersection pipeline.
>>
>> How is "Chart View" selected again? I didn't find it in the "View" drop
>> down menu at the top, but I was able to open a new layout and select
>> "SpreadSheetView".
>>
>> Thanks again,
>>
>> Louis Steytler
>> Department of Mechanical Science and Engineering
>> University of Illinois at Urbana-Champaign
>> 1206 West Green Street
>> Urbana, Il 61801
>> steyt...@illinois.edu
>> 
>> From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
>> Sent: 23 January 2018 09:32 AM
>> To: Steytler, Louis Louw
>> Cc: paraview@paraview.org
>> Subject: Re: [Paraview] Extracting data on the surface of a block?
>>
>> By "Export View", I meant "Export Scene" under the "File" menu.
>>
>> On Tue, Jan 23, 2018 at 10:31 AM, Utkarsh Ayachit
>>  wrote:
>>> Louis,
>>>
 This seemed to produce reasonable looking results, but I was not able to
 specify the number of points along the arc where data was extracted.
>>>
>>> PlotOnIntersectionCurves essentially slices the dataset using a
>>> implicit plane. The points you get are indeed the insection points
>>> between your polydata and the plane and hence there's no control over
>>> how many points there can be, besides what's determined by your mesh.
>>>
>>> If you can share the sample data (feel free to do it off the list,if
>>> you'd like), I can see what other options may work.
>>>
Also,  upon saving, three files were produced file0.csv, file1.csv,
 file2.csv, and
 file3.csv. Not sure why I am not getting just one file?
>>>
>>> Are you using "save data"? I'd suggest selecting the "Chart View" and
>>> then using "Export View" option to export the curves. That will give
>>> you a since CSV for the fields you've selected.
>>>
>>> Utkarsh
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] ParaView 5.4.1 | Segmentation Fault

[Utkarsh Ayachit]

Thomas,

Check your graphics drivers. You can use tools like `glxinfo` to tell
you which OpenGL version is supported. ParaView now requires 3.2 or
newer. If you cannot upgrade your graphics drivers, you can use
software OpenGL implementation packaged by ParaView binaries as
follows:

.../paraview --mesa

Hope that helps,
Utkarsh

On Wed, Jan 31, 2018 at 7:45 AM, Fastl, Thomas  wrote:
> Dear Community,
>
>
> I've recently upgraded to ParaView 5.4.1 since ParaView 5.0.0 stopped
> working on my workstation. Therefore, I've downloaded and unpacked
> ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz, however, receive the
> following error message upon execution:
>
>
> Warning: In
> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 838
> vtkGenericOpenGLRenderWindow (0x3846580): VTK is designed to work with
> OpenGL version 3.2 but it appears it has been given a context that does not
> support 3.2. VTK will run in a compatibility mode designed to work with
> earlier versions of OpenGL but some features may not work.
>
> Segmentation fault
>
>
> I'm running Ubuntu 14.04 on my workstation and should probably mention that
> I receive this error message right after execution of 'paraview', i.e., the
> Graphical User Interface never appears. Does anybody have a similar problem
> or know on how to resolve this issue? Thanks!
>
>
> Best, Thomas
>
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

[Paraview] ParaView 5.4.1 | Segmentation Fault

[Fastl, Thomas]

Dear Community,


I've recently upgraded to ParaView 5.4.1 since ParaView 5.0.0 stopped working 
on my workstation. Therefore, I've downloaded and unpacked 
ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz, however, receive the 
following error message upon execution:


Warning: In 
/home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
 line 838
vtkGenericOpenGLRenderWindow (0x3846580): VTK is designed to work with OpenGL 
version 3.2 but it appears it has been given a context that does not support 
3.2. VTK will run in a compatibility mode designed to work with earlier 
versions of OpenGL but some features may not work.

Segmentation fault


I'm running Ubuntu 14.04 on my workstation and should probably mention that I 
receive this error message right after execution of 'paraview', i.e., the 
Graphical User Interface never appears. Does anybody have a similar problem or 
know on how to resolve this issue? Thanks!


Best, Thomas

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] display problems paraview

[Utkarsh Ayachit]

This may be same as the issue described here:
https://gitlab.kitware.com/paraview/paraview/issues/17499
Try switching to NVidia GPU, if you can, if Intel graphics is indeed
the issue in your case.

Utkarsh

On Wed, Jan 31, 2018 at 6:09 AM, Ott  Richard  wrote:
> Hi,
>
> I am having problems using paraview because the whole window doesnt display
> properly. Meaning that the upper bar with File View etc is not displayed,
> but when I move the courser where the symbols should be the drop down menu
> shows up. Also the whole window seems slightly unfocused. Some buttons are
> where they are supposed to be and some arent really where they appear to be.
> It's very weird. I tried different paraview version etc and always have the
> same problem.
> I've attached a screenshot to this mail.
>
> It works totally fine on my other computer...
>
> Best,
> Richard
>
>
> Richard Ott
> ETH Zürich
> PhD student
>
> Sonneggstrasse 5
>
> 8092 Zürich
>
> +41 44 633 89 06
> richard@erdw.ethz.ch
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview