[Paraview] Using real timesteps in pvd files
Dear all, I'm using ParaView 3.4 to load the results of a transient simulation via a pvd file and a set of vtp XML PolyData files. Each vtp file corresponds to a particular real time value which are not evenly spaced. I tried to provide the real time values via the timestep key in the pvd file: ?xml version=1.0? VTKFile type=Collection version=0.1 byte_order=LittleEndian Collection DataSet timestep=1.23 group= part=0 file=sp_test000.vtp/ DataSet timestep=2.34 group= part=0 file=sp_test0002498.vtp/ DataSet timestep=3.15 group= part=0 file=sp_test0004496.vtp/ /Collection /VTKFile It seems that ParaView expects integer values for the timestep key, because it loads the files like expected but the time table in the Object Inspector - Information tab shows for the above pvd file: Index Value 0 1 1 2 2 3 I would be grateful for any help/suggestions. Thanks, Christian Wellmann ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Using real timesteps in pvd files
Christian ?xml version=1.0? VTKFile type=Collection version=0.1 byte_order=LittleEndian Collection DataSet timestep=1.08267 file=1800_001-static-0.vtmb/ DataSet timestep=1.08367 file=1800_001-static-1.vtmb/ DataSet timestep=1.08467 file=1800_001-static-2.vtmb/ ... DataSet timestep=1.34967 file=1800_001-static-00267.vtmb/ /Collection /VTKFile This works for me. Can't comment on why you are having trouble, but maybe try to remove the group, part unused tags. I use CVS paraview (3.4 should work) JB Dear all, I'm using ParaView 3.4 to load the results of a transient simulation via a pvd file and a set of vtp XML PolyData files. Each vtp file corresponds to a particular real time value which are not evenly spaced. I tried to provide the real time values via the timestep key in the pvd file: ?xml version=1.0? VTKFile type=Collection version=0.1 byte_order=LittleEndian Collection DataSet timestep=1.23 group= part=0 file=sp_test000.vtp/ DataSet timestep=2.34 group= part=0 file=sp_test0002498.vtp/ DataSet timestep=3.15 group= part=0 file=sp_test0004496.vtp/ /Collection /VTKFile It seems that ParaView expects integer values for the timestep key, because it loads the files like expected but the time table in the Object Inspector - Information tab shows for the above pvd file: Index Value 0 1 1 2 2 3 I would be grateful for any help/suggestions. Thanks, Christian Wellmann ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview -- John Biddiscombe,email:biddisco @ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82 ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Using real timesteps in pvd files
Thanks Stephen and John for your quick answers. Unfortunately any changes to the group and/or part tag not seem to solve the problem. What is strange is that, although ParaView seems to read an int value, it is able to handle DataSet timestep=-922337203685477580825263735124730 group= part=0 file=sp_test000.vtp/ DataSet timestep= 922337203685477580825263735124730 group= part=0 file=sp_test0002498.vtp/ correctly, what gives me Index Value 0-9.22337e+32 1 9.22337e+32 in the time table although the values are out of range of any standard integer representation I guess. However, as a workaround -considering the large range of representable integer values- I will simpliy change my scale to micro- or even nano-seconds to get integer time values. 2009/1/29 John Biddiscombe biddi...@cscs.ch: Christian ?xml version=1.0? VTKFile type=Collection version=0.1 byte_order=LittleEndian Collection DataSet timestep=1.08267 file=1800_001-static-0.vtmb/ DataSet timestep=1.08367 file=1800_001-static-1.vtmb/ DataSet timestep=1.08467 file=1800_001-static-2.vtmb/ ... DataSet timestep=1.34967 file=1800_001-static-00267.vtmb/ /Collection /VTKFile This works for me. Can't comment on why you are having trouble, but maybe try to remove the group, part unused tags. I use CVS paraview (3.4 should work) JB Dear all, I'm using ParaView 3.4 to load the results of a transient simulation via a pvd file and a set of vtp XML PolyData files. Each vtp file corresponds to a particular real time value which are not evenly spaced. I tried to provide the real time values via the timestep key in the pvd file: ?xml version=1.0? VTKFile type=Collection version=0.1 byte_order=LittleEndian Collection DataSet timestep=1.23 group= part=0 file=sp_test000.vtp/ DataSet timestep=2.34 group= part=0 file=sp_test0002498.vtp/ DataSet timestep=3.15 group= part=0 file=sp_test0004496.vtp/ /Collection /VTKFile It seems that ParaView expects integer values for the timestep key, because it loads the files like expected but the time table in the Object Inspector - Information tab shows for the above pvd file: Index Value 0 1 1 2 2 3 I would be grateful for any help/suggestions. Thanks, Christian Wellmann ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview -- John Biddiscombe,email:biddisco @ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82 ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Compiling last cvs: libKWCommon.so: cannot open shared object
On Thu, 29 Jan 2009, Stefan Melber wrote: Hi Ricardo, just switch the VTK_USE_RPATH off - then it should work (for me with the version checked out this moring) ... Forgot to mention, VTK_USE_RPATH was/is OFF I'm checking out and re-compiling. Does anyone know why using PYTHON implies SHARED LIBS ? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] [paraview] difficulties understanding results of the curvature filter
Is it possible that the lookup table range is incorrect? Can you edit color table range to not be as high as 820. On Thu, Jan 29, 2009 at 5:15 AM, Pierre JUILLARD pierre.juill...@gmail.com wrote: Hi all, I have been using the curvature filter in ParaView on a test case. Curvature seems indeed computed, but a single blue color is displayed on the screen. (picture joined) I was awaiting something more talkative: red color where the shape is curved, blue where it is flat... Did I miss a basic step? (you can see the pipeline on the screenshot) I can send the vtu file as well if that helps. (I don't do it because the mail limit size is quite low) Thanks in advance for your help! Regards, Pierre ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Paraview vs. nVidia Driver
Hmmm. What happens if you set the CMAKE_BUILD_TYPE to Release? -berk On Thu, Jan 29, 2009 at 2:29 PM, Rick Angelini an...@arl.army.mil wrote: It must be some part of our build process. If we download the precompiled Paraview executable, it works fine. If I do a generic build using the source code, it also works. So, there must be some flag or something in our production build tree that's causing a problem with the nVidia 180-xx drivers. Berk Geveci wrote: Huh, that's weird. vtkSMExtractDocumentation links against OpenGL but does not make any OpenGL calls. Can you build debug and try to get a stack trace? -berk On Tue, Jan 27, 2009 at 2:54 PM, Rick Angelini an...@arl.army.mil wrote: Has anyone had any trouble building Paraview with the latest nVidia GL libraries? On both RH4 and RH5, we've not been able to compile Paraview 3.4.0 (or 3.2.1) against nVidia driver 180.22 or 180.25.We can build against nVidia driver 173.14.xx. Also, if we build on a system that has driver 173.14.xx and then try to execute 'paraview' on a system with a 180.22 driver, we also get a floating point exception error. The compile failure is a floating point exception and looks like this: [89%] Built target pvpython-real Scanning dependencies of target pvbatch Scanning dependencies of target pvpython /bin/sh: line 1: 28655 Floating point exception../../bin/vtkSMExtractDocumentation /build/ParaView-3.2.1-x86_64-RHEL/Documentation /build/src/ParaView3.2.1/Qt/Components/Resources/XML/ParaViewWriters.xml make[2]: *** [Documentation/ParaViewWriters.html] Error 136 make[1]: *** [Servers/ServerManager/CMakeFiles/HTMLDocumentation.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Compiling last cvs: libKWCommon.so: cannot open shared object
Ricardo, This is a bug that got introduced recently. It should be fixed soon (if not already). -berk On Thu, Jan 29, 2009 at 5:28 AM, Ricardo Reis rr...@aero.ist.utl.pt wrote: I've compiled the last cvs version from source. PARAVIEW_ENABLE_PYTHON ON which sets BUILD_SHARED_LIBS ON If I run from the compilation directory everything is fine. If I run from the CMAKE_INSTALL_PREFIX directory (after doing make install) I get this message: /home/opt/paraview/lib/paraview-3.5/paraview-real: error while loading shared libraries: libKWCommon.so: cannot open shared object file: No such file or directory The install dir is /opt/paraview Any ideas? Thanks, Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/ ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Compiling last cvs: libKWCommon.so: cannot open shared object
Does anyone know why using PYTHON implies SHARED LIBS ? Because Python modules have to be built as shared libraries if you want to load them from the standard Python executable. On Thu, Jan 29, 2009 at 6:50 AM, Ricardo Reis rr...@aero.ist.utl.pt wrote: On Thu, 29 Jan 2009, Stefan Melber wrote: Hi Ricardo, just switch the VTK_USE_RPATH off - then it should work (for me with the version checked out this moring) ... Forgot to mention, VTK_USE_RPATH was/is OFF I'm checking out and re-compiling. Does anyone know why using PYTHON implies SHARED LIBS ? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/ ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Compiling last cvs: libKWCommon.so: cannot open shared object
On Thu, 29 Jan 2009, Berk Geveci wrote: Ricardo, This is a bug that got introduced recently. It should be fixed soon (if not already). Thanks Berk, great news :) best, Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Windows / building error on pqCommandServerStartup
Hi, I'm trying to build ParaView on Windows using MinGW - does anybody had this error in the past / not sure what to do at this point : [ 90%] Building CXX object Qt/Core/CMakeFiles/pqCore.dir/ pqCommandServerStartup.obj In file included from C:/MinGW/bin/../lib/gcc/ mingw32/3.4.5/../../../../include/windows.h:50, from C:/MinGW/bin/../lib/gcc/ mingw32/3.4.5/../../../../include/winsock2.h:22, from C:\Documents and Settings\podallaire\Desktop \ParaView3\Qt\Core\pqCommandServerStartup.cxx:39: C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1663: error: declaration of C function `LONG InterlockedCompar eExchange(volatile LONG*, LONG, LONG)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 387: error: previous declaration `long int InterlockedCompareE xchange(long int*, long int, long int)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1667: error: declaration of C function `LONG InterlockedDecrem ent(volatile LONG*)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 389: error: previous declaration `long int InterlockedDecremen t(long int*)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1668: error: declaration of C function `LONG InterlockedExchan ge(volatile LONG*, LONG)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 390: error: previous declaration `long int InterlockedExchange (long int*, long int)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1672: error: declaration of C function `LONG InterlockedExchan geAdd(volatile LONG*, LONG)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 391: error: previous declaration `long int InterlockedExchange Add(long int*, long int)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1676: error: declaration of C function `LONG InterlockedIncrem ent(volatile LONG*)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 388: error: previous declaration `long int InterlockedIncremen t(long int*)' here mingw32-make[2]: *** [Qt/Core/CMakeFiles/pqCore.dir/ pqCommandServerStartup.obj] Error 1 mingw32-make[1]: *** [Qt/Core/CMakeFiles/pqCore.dir/all] Error 2 mingw32-make: *** [all] Error 2 The same source code compiled fine on Linux and Mac. Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
