[Paraview] proper formatting of 2D data

2014-09-19 Thread Robert-Zoltan Szasz

Hi,

I tried to visualize 2D structured point data when I observed a strange 
behavior. If the spacing in Y direction is negative, the data is flipped 
upside-down in 'Slice' representation mode but shown properly as a  
'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit. 
Here is a small VTK file to test:


--8--
# vtk DataFile Version 2.0
testing
ASCII
DATASET STRUCTURED_POINTS
DIMENSIONS 3 4 1
ORIGIN 0.0 0.0 0.0
SPACING 0.5 -0.75 1.0
POINT_DATA 12
SCALARS test float
LOOKUP_TABLE default
0.0
1.0
2.0
1.0
2.0
3.0
2.0
3.0
4.0
3.0
4.0
5.0
--8--

I am wondering if I missed something when formatting the file or if you 
have any ideas how to avoid this behavior?

Thanks,
Robert

--
Robert-Zoltan Szasz
Div.Fluid Mechanics Tel: +46-46-222 0480
Dept. Energy Sciences, LTH  Fax: +46-46-222 4717
Lund University

___
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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] Client server volume rendering problem in 4.1 and 4.2RC1

2014-09-19 Thread ronald.fowler
Hi Utkarsh,
I have just downloaded the latest nightly build and it seems to work fine now 
(on Windows 7/64bit), doing remote volume rendering irrespective of the 
settings for remote/local. Many thanks for that quick fix.
Ron


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: 17 September 2014 17:30
To: Fowler, Ronald (STFC,RAL,SC)
Cc: ParaView
Subject: Re: [Paraview] Client server volume rendering problem in 4.1 and 4.2RC1

Ron,

Here's a fix that makes ParaView use remote-rendering irrespective of 
remote-rendering threshold when volume rendering:

http://review.source.kitware.com/#/t/4672

It'd be great if you could give it a try to confirm that it works.

Thanks
Utkarsh

On Wed, Sep 17, 2014 at 10:09 AM, Utkarsh Ayachit utkarsh.ayac...@kitware.com 
wrote:
 Ron,

 Those are good observations. I has been on my todo list to clean up 
 the remote-local rendering issue. I want ParaView to automatically 
 switch to remote rendering, if possible when volume rendering. I'll 
 see what I can do for that. The volume rendering code is currently 
 being revamped. I'd expect better smart rendering in near future.

 Utkarsh

 On Wed, Sep 17, 2014 at 6:29 AM,  ronald.fow...@stfc.ac.uk wrote:
 Hi,

 A post by Robert Atwood in June mentioned a problem with client 
 server volume visualisation in PV4.1, and I have also seen problems 
 in this case both on Linux and Windows systems.



 Fixes (0014794 and 0014792) have been added to 4.2RC1 which allow 
 correct rendering of the wavelet test case. I tried this on a Windows 
 7 system and works ok for 4.2RC1, but not for 4.1.



 However I think that the remote/local render problem for volume 
 visualisation is really very confusing and needs to be improved. 
 After spending more time then I should with it, I conclude that 
 (again on windows
 7 64 bit):

 (1)Volume rendering only works if done on the remote server, not the
 local on (as acknowledged in a tracker ticket, though I have not seen 
 it documented elsewhere).

 (2)For 4.1 to do this correctly for just a volume image this seems to
 need settings of “remote render threshold” ticked and “0 Mbytes” selected.
 It will work for cases when 0 Mbytes is selected, if there is also 
 another object displayed (e.g. an isosurface). This led me to think 
 an additional surface was always needed to see the volume, which is not the 
 case.

 (3)For 4.2RC1 the interface to settings has changed and there is no
 longer a tick box. Instead the slider for remote local render size 
 has a much greater range. This should be set to zero to force remote 
 render for volume views. It also works for non-zero values less than 
 the size of the volume data, e.g. 4Mbytes for a 256^3 volume. This 
 setting did not seem work for 4.1 to force a remote rendering of just volume 
 data.



 I think it would be useful if at least the tool tips in the settings 
 panel suggested how to make client server volume rendering work. It 
 would also be useful if a warning message were displayed when trying 
 (and failing) to do a local volume render in client server mode.



 Another problem that has been observed is that the “smart” option for 
 volume rendering is not necessarily that smart when the server nodes 
 have no GPUs and the client does. This was on a Linux 64 bit system with 4.1.



 Thanks,

 Ron fowler
















 --
 Scanned by iCritical.



 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


[Paraview] 3D contour smoothness

2014-09-19 Thread Philipp E
Hello everyone,

after extensive search I was desperate enough to post on this list:

It appears that the surface smoothing algorithm of the contour filter
does not work as aggressive as in older version (3.14.1 was the last
one we found to do so). As an example I prepared this two screenshots,
VTK data are scalars on a structured grid (200x100x100), legacy format.
(An additional call of the smooth filter does not help.)

3.14.1
http://s7.directupload.net/images/140919/euadfvko.png
4.0.RC1
http://s14.directupload.net/images/140919/84y689mi.png

Both versions are running with the shipped settings. Since the effect
could be reproduced on several workstations, we are wondering whether
there has been an (undocumented?) change in the filter mechanism or some
option we/setting/data problem we are not aware of.

Kind regards and thanks in advance
Philipp Engels.

___
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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] 3D contour smoothness

2014-09-19 Thread Cory Quammen
Philipp,

In the contour filter, is the option Compute Normals checked in 4.0 RC1?

Also, are the contour values the same between the two versions?

Thanks,
Cory

On Fri, Sep 19, 2014 at 10:25 AM, Philipp E pspeac...@gmail.com wrote:
 Hello everyone,

 after extensive search I was desperate enough to post on this list:

 It appears that the surface smoothing algorithm of the contour filter
 does not work as aggressive as in older version (3.14.1 was the last
 one we found to do so). As an example I prepared this two screenshots,
 VTK data are scalars on a structured grid (200x100x100), legacy format.
 (An additional call of the smooth filter does not help.)

 3.14.1
 http://s7.directupload.net/images/140919/euadfvko.png
 4.0.RC1
 http://s14.directupload.net/images/140919/84y689mi.png

 Both versions are running with the shipped settings. Since the effect
 could be reproduced on several workstations, we are wondering whether
 there has been an (undocumented?) change in the filter mechanism or some
 option we/setting/data problem we are not aware of.

 Kind regards and thanks in advance
 Philipp Engels.

 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] seg.fault when reading VRML files twice

2014-09-19 Thread Shawn Waldon
Hi Kazuyoshi,

The fix has been merged into the main branch of ParaView and should be
available in nightly builds as of today.

-Shawn

On Fri, Sep 5, 2014 at 9:37 AM, Shawn Waldon shawn.wal...@kitware.com
wrote:

 Hi Kazuyoshi,

 I've tracked down the segfault, which results from a bug in the VTK VRML
 importer class.  You will get the same thing if you delete a VRML Reader
 and re-create it.  It will affect any current build of ParaView.  Fixing it
 is going to require restructuring that class somewhat and will take a day
 or two.  For now, just try to avoid this particular use case if possible
 and I'll let you know as soon as it is fixed and merged into ParaView.

 -Shawn

 On Thu, Sep 4, 2014 at 6:27 PM, Kazuyoshi Furutaka 
 furutaka.kazuyo...@jaea.go.jp wrote:

 Updates:

   (v) also occurs w/ ParaView-4.2.0-RC1-Windows-32bit.exe as well
   as a 4.2.0-RC1 binary compiled on Fedora 20 (i386).

 Any suggestions?

 Thanks.
 Kazuyoshi

 From: Kazuyoshi Furutaka furutaka.kazuyo...@jaea.go.jp
 Subject: [Paraview] seg.fault when reading VRML files twice
 Date: Wed, 03 Sep 2014 11:50:11 +0900 (JST)

  Dear ParaView experts...
 
  As the subject says, I'm suffering from the segmentation faluts
  when reading VRML files.
 
  It occurs:
(i)  File-Open a VRML file, display the content,
 (File-Disconnect) then File-Open a VRML file and display it,
 
(ii) on linux (Fedora 20, binary package: paraview-4.1.0-1.fc20.i686)
 as well as on windows (Vista Business SP2, 4.1.0 32-bit,
 ParaView-4.1.0-Windows-32bit.exe, downloaded from
 http://www.paraview.org/download/
 
(iii) regardless of whether the second VRML file is the same as
 or different from the first one,
 
(iV) even with a simple VRML file as the attached one...
 
  It DOES NOT occur when loading/displaying multiple VRML files
  in the same session (w/o disconnecting)...
 
  How can I avoid/fix this?
 
  I'll attach a trimmed backtrace obtained on linux with gdb...
 
  Thanks in advance.
 
  Kazuyoshi
  --
  Kazuyoshi Furutaka
  furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp
 --
 Kazuyoshi Furutaka
 furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp
 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] 3D contour smoothness

2014-09-19 Thread Philipp E
Hi Cory,

thank you for your fast feedback.

a) Compute normal is checked. (Without normals, the contour is
completely stepped)
b) Contour values are the same.

Regards
Philipp

On 09/19/2014 04:40 PM, Cory Quammen wrote:
 Philipp,

 In the contour filter, is the option Compute Normals checked in 4.0 RC1?

 Also, are the contour values the same between the two versions?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:25 AM, Philipp E pspeac...@gmail.com wrote:
 Hello everyone,

 after extensive search I was desperate enough to post on this list:

 It appears that the surface smoothing algorithm of the contour filter
 does not work as aggressive as in older version (3.14.1 was the last
 one we found to do so). As an example I prepared this two screenshots,
 VTK data are scalars on a structured grid (200x100x100), legacy format.
 (An additional call of the smooth filter does not help.)

 3.14.1
 http://s7.directupload.net/images/140919/euadfvko.png
 4.0.RC1
 http://s14.directupload.net/images/140919/84y689mi.png

 Both versions are running with the shipped settings. Since the effect
 could be reproduced on several workstations, we are wondering whether
 there has been an (undocumented?) change in the filter mechanism or some
 option we/setting/data problem we are not aware of.

 Kind regards and thanks in advance
 Philipp Engels.

 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] 3D contour smoothness

2014-09-19 Thread Cory Quammen
Phillipp,

Do you have a data set similar to the one you've shown that you can share?

Thanks,
Cory

On Fri, Sep 19, 2014 at 10:48 AM, Philipp E pspeac...@gmail.com wrote:
 Hi Cory,

 thank you for your fast feedback.

 a) Compute normal is checked. (Without normals, the contour is
 completely stepped)
 b) Contour values are the same.

 Regards
 Philipp

 On 09/19/2014 04:40 PM, Cory Quammen wrote:
 Philipp,

 In the contour filter, is the option Compute Normals checked in 4.0 RC1?

 Also, are the contour values the same between the two versions?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:25 AM, Philipp E pspeac...@gmail.com wrote:
 Hello everyone,

 after extensive search I was desperate enough to post on this list:

 It appears that the surface smoothing algorithm of the contour filter
 does not work as aggressive as in older version (3.14.1 was the last
 one we found to do so). As an example I prepared this two screenshots,
 VTK data are scalars on a structured grid (200x100x100), legacy format.
 (An additional call of the smooth filter does not help.)

 3.14.1
 http://s7.directupload.net/images/140919/euadfvko.png
 4.0.RC1
 http://s14.directupload.net/images/140919/84y689mi.png

 Both versions are running with the shipped settings. Since the effect
 could be reproduced on several workstations, we are wondering whether
 there has been an (undocumented?) change in the filter mechanism or some
 option we/setting/data problem we are not aware of.

 Kind regards and thanks in advance
 Philipp Engels.

 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] 3D contour smoothness

2014-09-19 Thread Cory Quammen
Philipp,

I can confirm what you see with a pre 4.2 version of ParaView.
However, the number of produced cells is the same.

I will try to track down why this changed.

Thanks,
Cory

On Fri, Sep 19, 2014 at 11:17 AM, Philipp E pspeac...@gmail.com wrote:
 Hi Cory

 I managed to compress the data set to a fair size and attached it to
 this mail. The data set is pressure, contour value is 0.55.

 By looking again at the data (contour - information), I just found that
 the old version (3.14.1) uses 148432 cells , while the the new one
 employs 75232 cells. Hope that helps.

 Kind regards
 Philipp

 Errata: I meant 4.2.0RC1 in the previous mails.

 On 09/19/2014 04:59 PM, Cory Quammen wrote:
 Phillipp,

 Do you have a data set similar to the one you've shown that you can share?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:48 AM, Philipp E pspeac...@gmail.com wrote:
 Hi Cory,

 thank you for your fast feedback.

 a) Compute normal is checked. (Without normals, the contour is
 completely stepped)
 b) Contour values are the same.

 Regards
 Philipp

 On 09/19/2014 04:40 PM, Cory Quammen wrote:
 Philipp,

 In the contour filter, is the option Compute Normals checked in 4.0 RC1?

 Also, are the contour values the same between the two versions?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:25 AM, Philipp E pspeac...@gmail.com wrote:
 Hello everyone,

 after extensive search I was desperate enough to post on this list:

 It appears that the surface smoothing algorithm of the contour filter
 does not work as aggressive as in older version (3.14.1 was the last
 one we found to do so). As an example I prepared this two screenshots,
 VTK data are scalars on a structured grid (200x100x100), legacy format.
 (An additional call of the smooth filter does not help.)

 3.14.1
 http://s7.directupload.net/images/140919/euadfvko.png
 4.0.RC1
 http://s14.directupload.net/images/140919/84y689mi.png

 Both versions are running with the shipped settings. Since the effect
 could be reproduced on several workstations, we are wondering whether
 there has been an (undocumented?) change in the filter mechanism or some
 option we/setting/data problem we are not aware of.

 Kind regards and thanks in advance
 Philipp Engels.

 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] 3D contour smoothness

2014-09-19 Thread Philipp E.
Sorry Cory,

you are right. The cell number is the same.

Regards
Philipp


Am 19.09.2014 um 17:46 schrieb Cory Quammen:
 Philipp,

 I can confirm what you see with a pre 4.2 version of ParaView.
 However, the number of produced cells is the same.

 I will try to track down why this changed.

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 11:17 AM, Philipp E pspeac...@gmail.com wrote:
 Hi Cory

 I managed to compress the data set to a fair size and attached it to
 this mail. The data set is pressure, contour value is 0.55.

 By looking again at the data (contour - information), I just found that
 the old version (3.14.1) uses 148432 cells , while the the new one
 employs 75232 cells. Hope that helps.

 Kind regards
 Philipp

 Errata: I meant 4.2.0RC1 in the previous mails.

 On 09/19/2014 04:59 PM, Cory Quammen wrote:
 Phillipp,

 Do you have a data set similar to the one you've shown that you can share?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:48 AM, Philipp E pspeac...@gmail.com wrote:
 Hi Cory,

 thank you for your fast feedback.

 a) Compute normal is checked. (Without normals, the contour is
 completely stepped)
 b) Contour values are the same.

 Regards
 Philipp

 On 09/19/2014 04:40 PM, Cory Quammen wrote:
 Philipp,

 In the contour filter, is the option Compute Normals checked in 4.0 RC1?

 Also, are the contour values the same between the two versions?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:25 AM, Philipp E pspeac...@gmail.com wrote:
 Hello everyone,

 after extensive search I was desperate enough to post on this list:

 It appears that the surface smoothing algorithm of the contour filter
 does not work as aggressive as in older version (3.14.1 was the last
 one we found to do so). As an example I prepared this two screenshots,
 VTK data are scalars on a structured grid (200x100x100), legacy format.
 (An additional call of the smooth filter does not help.)

 3.14.1
 http://s7.directupload.net/images/140919/euadfvko.png
 4.0.RC1
 http://s14.directupload.net/images/140919/84y689mi.png

 Both versions are running with the shipped settings. Since the effect
 could be reproduced on several workstations, we are wondering whether
 there has been an (undocumented?) change in the filter mechanism or some
 option we/setting/data problem we are not aware of.

 Kind regards and thanks in advance
 Philipp Engels.

 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] proper formatting of 2D data

2014-09-19 Thread Burlen Loring

Hi Robert,

Good one! The slice rep uses GPU textures and this behavior looks a bug 
in the logic that sets up the texture. You should file a bug report.


There's an easy workaround. Convert to a positive spacing and adjust the 
origin accordinigly. The data will the occupy the same region. Here's 
how your file looks then:


--8--
# vtk DataFile Version 2.0
testing
ASCII
DATASET STRUCTURED_POINTS
DIMENSIONS 3 4 1
ORIGIN 0.0 -2.25 0.0
SPACING 0.5 0.75 1.0
POINT_DATA 12
SCALARS test float
LOOKUP_TABLE default
0.0
1.0
2.0
1.0
2.0
3.0
2.0
3.0
4.0
3.0
4.0
5.0
--8--

Burlen

On 09/18/2014 11:56 PM, Robert-Zoltan Szasz wrote:

Hi,

I tried to visualize 2D structured point data when I observed a 
strange behavior. If the spacing in Y direction is negative, the data 
is flipped upside-down in 'Slice' representation mode but shown 
properly as a  'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 
on Linux 64 bit. Here is a small VTK file to test:


--8--
# vtk DataFile Version 2.0
testing
ASCII
DATASET STRUCTURED_POINTS
DIMENSIONS 3 4 1
ORIGIN 0.0 0.0 0.0
SPACING 0.5 -0.75 1.0
POINT_DATA 12
SCALARS test float
LOOKUP_TABLE default
0.0
1.0
2.0
1.0
2.0
3.0
2.0
3.0
4.0
3.0
4.0
5.0
--8--

I am wondering if I missed something when formatting the file or if 
you have any ideas how to avoid this behavior?

Thanks,
Robert



___
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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] [EXTERNAL] proper formatting of 2D data

2014-09-19 Thread Scott, W Alan
Robert,
I am pretty sure that is a bug.  Mind writing up a bug report?  Also, your 
description and example file are great.  Be sure to include them in the bug.

Alan

-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of 
Robert-Zoltan Szasz
Sent: Friday, September 19, 2014 12:57 AM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] proper formatting of 2D data

Hi,

I tried to visualize 2D structured point data when I observed a strange 
behavior. If the spacing in Y direction is negative, the data is flipped 
upside-down in 'Slice' representation mode but shown properly as a 'Surface' 
representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit. 
Here is a small VTK file to test:

--8--
# vtk DataFile Version 2.0
testing
ASCII
DATASET STRUCTURED_POINTS
DIMENSIONS 3 4 1
ORIGIN 0.0 0.0 0.0
SPACING 0.5 -0.75 1.0
POINT_DATA 12
SCALARS test float
LOOKUP_TABLE default
0.0
1.0
2.0
1.0
2.0
3.0
2.0
3.0
4.0
3.0
4.0
5.0
--8--

I am wondering if I missed something when formatting the file or if you have 
any ideas how to avoid this behavior?
Thanks,
Robert

--
Robert-Zoltan Szasz
Div.Fluid Mechanics Tel: +46-46-222 0480
Dept. Energy Sciences, LTH  Fax: +46-46-222 4717
Lund University

___
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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] [EXTERNAL] proper formatting of 2D data

2014-09-19 Thread Cory Quammen
Is negative spacing really supported in VTK/ParaView? The VTK File
Formats document for legacy data
(http://www.vtk.org/VTK/img/file-formats.pdf) states under the
description of the structured points data:

The data spacing sx, sy, sz must be greater than 0.

This is apparently not enforced in the reader, however.

Thanks,
Cory

On Fri, Sep 19, 2014 at 1:01 PM, Scott, W Alan wasc...@sandia.gov wrote:
 Robert,
 I am pretty sure that is a bug.  Mind writing up a bug report?  Also, your 
 description and example file are great.  Be sure to include them in the bug.

 Alan

 -Original Message-
 From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of 
 Robert-Zoltan Szasz
 Sent: Friday, September 19, 2014 12:57 AM
 To: paraview@paraview.org
 Subject: [EXTERNAL] [Paraview] proper formatting of 2D data

 Hi,

 I tried to visualize 2D structured point data when I observed a strange 
 behavior. If the spacing in Y direction is negative, the data is flipped 
 upside-down in 'Slice' representation mode but shown properly as a 'Surface' 
 representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit.
 Here is a small VTK file to test:

 --8--
 # vtk DataFile Version 2.0
 testing
 ASCII
 DATASET STRUCTURED_POINTS
 DIMENSIONS 3 4 1
 ORIGIN 0.0 0.0 0.0
 SPACING 0.5 -0.75 1.0
 POINT_DATA 12
 SCALARS test float
 LOOKUP_TABLE default
 0.0
 1.0
 2.0
 1.0
 2.0
 3.0
 2.0
 3.0
 4.0
 3.0
 4.0
 5.0
 --8--

 I am wondering if I missed something when formatting the file or if you have 
 any ideas how to avoid this behavior?
 Thanks,
 Robert

 --
 Robert-Zoltan Szasz
 Div.Fluid Mechanics Tel: +46-46-222 0480
 Dept. Energy Sciences, LTH  Fax: +46-46-222 4717
 Lund University

 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] 3D contour smoothness

2014-09-19 Thread Cory Quammen
Just a little more info on this. The problem starts with 3.98.

On Fri, Sep 19, 2014 at 12:08 PM, Philipp E. pspeac...@gmail.com wrote:
 Sorry Cory,

 you are right. The cell number is the same.

 Regards
 Philipp


 Am 19.09.2014 um 17:46 schrieb Cory Quammen:
 Philipp,

 I can confirm what you see with a pre 4.2 version of ParaView.
 However, the number of produced cells is the same.

 I will try to track down why this changed.

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 11:17 AM, Philipp E pspeac...@gmail.com wrote:
 Hi Cory

 I managed to compress the data set to a fair size and attached it to
 this mail. The data set is pressure, contour value is 0.55.

 By looking again at the data (contour - information), I just found that
 the old version (3.14.1) uses 148432 cells , while the the new one
 employs 75232 cells. Hope that helps.

 Kind regards
 Philipp

 Errata: I meant 4.2.0RC1 in the previous mails.

 On 09/19/2014 04:59 PM, Cory Quammen wrote:
 Phillipp,

 Do you have a data set similar to the one you've shown that you can share?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:48 AM, Philipp E pspeac...@gmail.com wrote:
 Hi Cory,

 thank you for your fast feedback.

 a) Compute normal is checked. (Without normals, the contour is
 completely stepped)
 b) Contour values are the same.

 Regards
 Philipp

 On 09/19/2014 04:40 PM, Cory Quammen wrote:
 Philipp,

 In the contour filter, is the option Compute Normals checked in 4.0 
 RC1?

 Also, are the contour values the same between the two versions?

 Thanks,
 Cory

 On Fri, Sep 19, 2014 at 10:25 AM, Philipp E pspeac...@gmail.com wrote:
 Hello everyone,

 after extensive search I was desperate enough to post on this list:

 It appears that the surface smoothing algorithm of the contour filter
 does not work as aggressive as in older version (3.14.1 was the last
 one we found to do so). As an example I prepared this two screenshots,
 VTK data are scalars on a structured grid (200x100x100), legacy format.
 (An additional call of the smooth filter does not help.)

 3.14.1
 http://s7.directupload.net/images/140919/euadfvko.png
 4.0.RC1
 http://s14.directupload.net/images/140919/84y689mi.png

 Both versions are running with the shipped settings. Since the effect
 could be reproduced on several workstations, we are wondering whether
 there has been an (undocumented?) change in the filter mechanism or some
 option we/setting/data problem we are not aware of.

 Kind regards and thanks in advance
 Philipp Engels.

 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] How to simply Reload a data file

2014-09-19 Thread Richter, Christian, Dipl.-Ing.
We use this simple python script for file series (stl, vtk, particle data in 
LAMMPS text- or binary format (with our own reader)).
Feel free to use this as a starting point:
https://github.com/richti83/ParaView_Reader_for_LIGGGHTS/blob/master/python_macros/update.py

The if-condition in line 68 should be more generous, but for now it works and 
you can add every source (plane,line,...) there which does not support file 
series.

To use it: first build your tree in the pipeline browser by opening file series 
(need to have more than one file bc. otherwise the reader_core is used inside 
PV instead of PV_FileSeriesReader).
Than, while the simulation is running, just hit update macro button to reload 
the file series and jump to the last available timestep.

Best,
Christian.

Von: ParaView [paraview-boun...@paraview.org]quot; im Auftrag von 
quot;Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Gesendet: Donnerstag, 18. September 2014 14:46
An: Zenker, Dr. Matthias
Cc: paraview@paraview.org
Betreff: Re: [Paraview] How to simply Reload a data file

Sorry, didn't get around to it yet. Over this weekend is more likely,
since I am tracking down some last minute issues with 4.2 right now.

Utkarsh

On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias
matthias.zen...@erbe-med.com wrote:
 Hi Utkarsh,

 any news regarding a reload data function (see below)?

 Matthias

 -Ursprüngliche Nachricht-
 Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
 Gesendet: Montag, 15. September 2014 16:50
 An: Zenker, Dr. Matthias
 Cc: Cory Quammen; paraview@paraview.org
 Betreff: Re: [Paraview] How to simply Reload a data file

 Ah. since it's a file series, it would not work the way Cory is suggesting. 
 I'll see
 if I can cook up a Python script that can make this possible for now. We're
 putting this on the roadmap for the next release (I know I've said that a few
 times in the past :) ).

 Utkarsh

 On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias
 matthias.zen...@erbe-med.com wrote:
  Normally I load a time series, either a series of vtu files or a time 
  collection
 (pvd file containing the vtu file names with asociated timestamps). During
 the simulation, new files are added to the series. So it would be nice to 
 watch
 the simulation going on by reloading from time to time.
 
  Matthias
 
  -Ursprüngliche Nachricht-
  Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
  Gesendet: Montag, 15. September 2014 16:28
  An: Zenker, Dr. Matthias
  Cc: Cory Quammen; paraview@paraview.org
  Betreff: Re: [Paraview] How to simply Reload a data file
 
  I suspect will not work with vtu. To understand this better, what is
  that which is changing that you need to reload the file? Are you
  loading a file series or a single file?
 
  Utkarsh
 
  On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias
  matthias.zen...@erbe-med.com wrote:
   Hi  Cory,
  
   I use the reader for vtu format and pvd (vtu time collection). I
   tried to
  modify the xml as follows:
  
   ParaViewPlugin
   ServerManagerConfiguration
 ProxyGroup name=sources
   SourceProxy name=VTUrefresh base_proxygroup=sources
  base_proxyname=VTUReader class=vtuReader
 Property name=Refresh command=Modified
  panel_widget=command_button/
 Hints
   ReaderFactory extensions=vtu pvd file_description=vtu
   Reader
  (Refresh button) /
 /Hints
   /SourceProxy
 /ProxyGroup
 /ServerManagerConfiguration
 ParaViewReaders
   Reader name=ReaderWithButton /
 /ParaViewReaders
   /ParaViewPlugin
  
   But I cannot even load it as plugin. Presumably there are special
   keyword to
  use for the name of the original reader. Is there a documentation
  where I can find more information on that topic?
  
   Thanks,
  
   Matthias
  
   -Ursprüngliche Nachricht-
   Von: Cory Quammen [mailto:cory.quam...@kitware.com]
   Gesendet: Montag, 15. September 2014 15:05
   An: Zenker, Dr. Matthias
   Cc: paraview@paraview.org
   Betreff: Re: [Paraview] How to simply Reload a data file
  
   Matthias,
  
   The method I suggested requires modifying ParaView's source code,
   so it won't work for a binary distribution.
  
   As for the XML method, did you try to load an Xdmf file through
   what should be the new Xdmf Reader (Refresh button) reader? If
   you are loading a different type of file, this plugin will have no
   effect because it provides a Refresh button only for the Xdmf
   reader. You could modify the XML for other reader types, though.
  
   Thanks,
   Cory
  
   On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias
   matthias.zen...@erbe-med.com wrote:
Hi,
   
I wanted to try the Reload button which presumably can be
created by
   one of the methods outlined below. But I am maybe too naive or am
   missing
   something: I have a Windoze binary distribution of ParaView 4.0.1.
   I did not find the file indicated by Cory, and copying 

[Paraview] Plotting Nek5000 output data

2014-09-19 Thread Pradeep Jha
I am outputting my data from Nek5000 in the case.fld* format. I am creating
a case.nek5000 file which reads like:

filetemplate:case.fld%02d
firsttimestep: 1
numtimesteps: 2


When I am opening this *nek5000 file in Paraview 4.1, I don't see the
contours. In Visit I see them (images attached). Any tips?
___
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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] [EXTERNAL] Plotting Nek5000 output data

2014-09-19 Thread Scott, W Alan
Can you post the data here?

Alan

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Pradeep Jha
Sent: Friday, September 19, 2014 3:14 PM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] Plotting Nek5000 output data

I am outputting my data from Nek5000 in the case.fld* format. I am creating a 
case.nek5000 file which reads like:

filetemplate:case.fld%02d
firsttimestep: 1
numtimesteps: 2


When I am opening this *nek5000 file in Paraview 4.1, I don't see the contours. 
In Visit I see them (images attached). Any tips?

___
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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview