[Paraview] Starting paraview with --server option
Hello, I need to start Paraview with connexion to pvserver 3.4.0 on port 1 on Windows XP SP3 . I start pvserver in a command shell. I start paraview 3.4.0 in another shell with the following syntax. paraview --server=localhost paraview --server=127.0.0.1 paraview --server=127.0.0.1:1 paraview --server=cs://localhost:1 I got always a message of this type : Could not connect to requested server xx . Creating default builtin connection where x is the string given after --server= What is the right syntax ? Thanks Guy ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] problems with Xdmf-file
Hi! Well, Paraview still crashes when I try to read an .xmf file. That´s what it looks like now: ?xml version=1.0 ? !DOCTYPE Xdmf SYSTEM Xdmf.dtd [] Xdmf Domain Grid Name=Curvilinear GridType=Uniform Topology TopologyType=2DSMesh Dimensions = 140 350 /Topology Geometry GeometryType=XY DataStructure Name=Coordinates DataType=Float Precision=4 Dimensions=49000 2 Format=HDF C:\\Dokumente und Einstellungen\\Natalie Happenhofer\\Eigene Dateien\\xdmf_files\\c1d-T132-30SEPT-deep_0.h5:/Curvilinear /Coordinates /DataStructure /Geometry Attribute Name=Density Active=1 Type=Scalar Center=Node DataItem DataType=Float Precision=4 Dimensions=140 350 Format=HDF C:\\Dokumente und Einstellungen\\Natalie Happenhofer\\Eigene Dateien\\xdmf_files\\c1d-T132-30SEPT-deep_0.h5:/Curvilinear/dg /DataItem /Attribute /Grid /Domain /Xdmf Well, Paraview obviously reads my .xmf file as I see my Grid and the associated attribute data in the object inspector in paraview. When I click the Apply button, I get and output message from paraview which says that there has been caught an exception of a qt-eventhandler.?! Debugging, I get the error Access violation. Concerning my .h5 file, it looks ok, i.e I have my group Curvilinear which is my grid and then two datasets associated with it, Coordinates and dg. Coordinates is a 2D-array with dimensions 49000x2, i.e. in the first column is the xCoordinate, in the second the yCoordinate. dg is a 350x140 array with the densitiy values associated with each node. I believe that I set the dimensions wrong in my .xmf file, but I don´t know how to set it right! I have a 2D-mesh, specifying every point with coordinates and I have attribute data associated with each node. thx for help, NH From: [EMAIL PROTECTED] Subject: Re: [Paraview] problems with Xdmf-file Date: Tue, 14 Oct 2008 15:27:22 +0100 To: [EMAIL PROTECTED] Hi Natalie. I too had some difficulties when I was getting started with xmdf. I had similar problems of paraview crashing a lot when I was first migrating my data over to the format. I found this crashing behaviour was due to any problem with the formation of my h5 or xmf file. Therefore although you suspect the h5 file it could easily be your xml too. In reading your email I have a few ideas you might want to try out: 1 - I couldn't get the xmdf API to work either so I had to resort to writing the xmf files by hand. However, rather than using the hdf5 api directly I made use of a python module called PyTables which wraps the hdf5 api and works seamlessly with Numpy. For me it worked well well because I was dealing with Numpy information already. 2 - Another piece of handy software is an hdf5 viewer. There is one available from the hdf people directly called hdfview I think, but I have used another one called vitables which is by the same people as pytables. The niece thing here is that you can open up the hdf5 file and actually look at how the array came into the file. If for example there is something wrong with the hdf file it should either be visible as an anomaly in the data or the file simply won't open if the problem is serious. 3 - For the geometry you should check that your array is the shape you think it is. You are specifying XYZ which means that it needs to be in a Nx3 array like like: 2 3 51 2 47.1 5.12 4. If your xyz data is in a different format you could should use another format like X_Y_Z where each coordinate is in its own vector. I think you have this ok in your example but it would be worth checking that your coordinate information is in fact the right shape. 4 - In the xml you might want to check how to handle spaces in window's paths when specifying the heavy data. I don't use windows much so I'm not sure if this matters but under Linux this would be bad. Small errors like this (or misspelled words in the path) can cause hard crashes like this. 5 - In the xml the dimensions should be specified with the slowest varying dimension first (i.e. KJI order). In your xml you have the reverse. This was taken right from the xdmf website but I had some difficulty in figuring out exactly what they meant by it. It looked to me that there were contradictory examples on the xdmf website so you might have to play around with the permutations of the order here to get it right if this is the problem. Oh - and in reference to your other email regarding a crash that happens after you've gone through a few timesteps. One guess could be that you are running out of memory. I had this problem when I was using very large datasets (5 million unstructured points) with an older version of Xdmf and Paraview. They have really increased the time support in both recently (within
Re: [Paraview] Starting paraview with --server option
Guy, You'll have to setup the server configuration first from the GUI. Start paraview then choose File|Connect. In the Choose Server dialog you can set up your server configuration using Add Server and give it a name -- say myLocalHost. Then you can use the following: paraview --server=myLocalHost Utkarsh Guy HUBERT wrote: Hello, I need to start Paraview with connexion to pvserver 3.4.0 on port 1 on Windows XP SP3 . I start pvserver in a command shell. I start paraview 3.4.0 in another shell with the following syntax. paraview --server=localhost paraview --server=127.0.0.1 paraview --server=127.0.0.1:1 paraview --server=cs://localhost:1 I got always a message of this type : Could not connect to requested server xx . Creating default builtin connection where x is the string given after --server= What is the right syntax ? Thanks Guy ___ 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
[Paraview] HDF5 1.8
I have been building CVS Paraview against my own HDF5 1.8.1 install by defining H5_USE_16_API with no problems. After a recent CVS update, my compile failed due to an ABI change in the (undocumented) struct H5FD_class_t used in Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx. I don't know why Xdmf2 needs to use this undocumented struct, but the patch below is a simple way to make things work with 1.8 again. It would be better for CMake to define a variable for the real version of HDF5 rather than branch on H5_USE_16_API. Index: Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx === RCS file: /cvsroot/ParaView3/ParaView3/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx,v retrieving revision 1.5 diff -r1.5 XdmfH5Driver.cxx 134a135,139 #ifdef H5_USE_16_API static haddr_t H5FD_dsm_get_eoa(const H5FD_t *_file, H5FD_mem_t); static herr_t H5FD_dsm_set_eoa(H5FD_t *_file, H5FD_mem_t, haddr_t addr); static haddr_t H5FD_dsm_get_eof(const H5FD_t *_file); #else 137a143,144 #endif 596a604,606 #ifdef H5_USE_16_API H5FD_dsm_get_eoa(const H5FD_t *_file, H5FD_mem_t) #else 597a608 #endif 624a636,638 #ifdef H5_USE_16_API H5FD_dsm_set_eoa(H5FD_t *_file, H5FD_mem_t, haddr_t addr) #else 625a640 #endif 665a681,683 #ifdef H5_USE_16_API H5FD_dsm_get_eof(const H5FD_t *_file) #else 666a685 #endif When I build with testing, I get an error because these directories don't exist. Index: VTK/Examples/Infovis/Cxx/CMakeLists.txt === RCS file: /cvsroot/ParaView3/ParaView3/VTK/Examples/Infovis/Cxx/CMakeLists.txt,v retrieving revision 1.6 diff -r1.6 CMakeLists.txt 27,33d26 # If Qt is enabled include the EasyView example IF(VTK_USE_QVTK) SUBDIRS(ChartView) SUBDIRS(EasyView) SUBDIRS(StatsView) ENDIF(VTK_USE_QVTK) Jed pgpGRMUld5BAi.pgp Description: PGP signature ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Ensight and FLUENT
Hi All, I have spent some more time to use paraview for FLUENT now with the latest 3.4.0 I still have problems with import: * direct import works fine mostly. However, I am unable to extract surface zones. There is no way to do postporcessing for external flows that way. Is there any way to split the surface? * Using Ensight imports surface parts. This allows postprocessing. However, I get sementation faults quite often with that. E.g. FLUENT tutorial 6 exported as Ensight (node based, binary or ascii) gives a segfault for me. Am I the only one with this problem? Maybe someone out there has some tips? Thanks. BastiL ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
