[Paraview] Problem with Xdmf/HyperSlab
Hello, either the implementation of the HyperSlab Itemtype, or my grasp of it is corrupted. To illustrate the problem which I am getting, see the attached XDMF file (no HDF5 needed, just plain XML), which is supposed to cut a 2x2x2 cube out of a larger 3x3x3x cube. My issues: 1. To extract the subgrid [0,1]^3 from the larger [0,2]^3 grid, I set the start-stride-count in the first DataItem to 0 0 0 1 1 1 2 2 2 in analogy to the example from [www.xdmf.org/index.php/XDMF_Model_and_Format], but this causes Paraview to crash. (*** glibc detected *** ... realloc(): invalid next size: 0x08e1a800 ***) The same happens if I try to access the opposite corner [1,2]^3 (the one with values in the [8,15] range) using 1 1 1 1 1 1 2 2 2 2. I can apparently avoid the crash using ranges whose count values are at least 3 (which should obviously be too large for the 2x2x2 target grid), and even grossly out-of-bound values such as 12 11 321 1 1 1 6 13 13 are accepted without complaints, and result in something that from visual inspection looks like 1 2 0 3 4 0 0 0 i.e. a copy of the beginning of the source array. Can anybody explain to me what is going on here? Any hint would be apprechiated. Best, Jens. PS: I have tried to get help from the Xdmf mailing list (so far without any response), but since this potentialle concerns both [Paraview] and [Xdmf] (and this list is apparently more active), I post this here again. !-- BEGIN hyperslab_test.xml -- ?xml version=1.0 ? !DOCTYPE Xdmf SYSTEM Xdmf.dtd [] Xdmf Version=2.0 Domain Grid Name=myGrid GridType=Uniform Topology TopologyType=3dCoRectMesh Dimensions=2 2 2/ Geometry GeometryType=Origin_DxDyDz DataItem Dimensions=3 NumberType=Float Format=XML 0.0 0.0 0.0 /DataItem DataItem Dimensions=3 NumberType=Float Format=XML 1.0 1.0 1.0 /DataItem /Geometry Attribute Name=dat_01 AttributeType=Scalar Center=Node DataItem Dimensions=2 2 2 NumberType=Float Format=XML 1 2 3 4 5 6 7 8!-- expected in [0,1]^3 -- /DataItem /Attribute Attribute Name=dat_12 AttributeType=Scalar Center=Node DataItem Dimensions=2 2 2 NumberType=Float Format=XML 8 9 10 11 12 13 14 15 !-- expected in [1,2]^3 -- /DataItem /Attribute Attribute Name=dat_hyper AttributeType=Scalar Center=Node DataItem ItemType=HyperSlab Dimensions=2 2 2 Type=HyperSlab DataItem Dimensions=3 3 Format=XML 0 0 0 1 1 1 2 2 2 /DataItem DataItem Dimensions=3 3 3 NumberType=Float Format=XML 1 2 0 3 4 0 0 0 0 5 6 0 7 8 9 0 10 11 0 0 0 0 12 13 0 14 15 /DataItem /DataItem /Attribute /Grid /Domain /Xdmf !-- END hyperslab_test.xml -- ___ 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://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Paraview Python Script with PVFWrap
Hi Fabian, Please remember to include the paraview mailing list when you reply. What you report is a bug, but you can avoid it- when you open your openfoam dataset you should check each block that you want to load *before you hit apply for the first time* The problem is the first time you load your data and click apply, paraview sees a multiblock dataset containing only unstructured grid data, so it creates an unstructured grid display. This display has properties related to volume rendering, and these properties are recorded in the trace script. Later you must have enabled more blocks, so that multiblock dataset now contains unstructured grid and polydata. When the trace script is replayed, paraview sees the unstructured grid and polydata datasets, so it creates a geometry display instead of an unstructured grid display. The geometry display lacks the volume rendering properties. Pat On Tue, Jan 25, 2011 at 2:33 PM, Fabian Braennstroem f.braennstr...@gmx.dewrote: Hi to you both, I just checked it with 3.8.1... a new trace_state file. There I got theses error messages (one after another), each time I got the errro I just commented out the lines in the python file, which I attached (I attached the openfoam case, if you need it): Traceback (most recent call last): File string, line 198, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute SelectedMapperIndex does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. Traceback (most recent call last): File string, line 225, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute ScalarOpacityUnitDistance does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. Traceback (most recent call last): File string, line 232, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute ScalarOpacityFunction does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. Traceback (most recent call last): File string, line 241, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute ExtractedBlockIndex does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. It works very nice, after commenting these lines out! Best Regards! Fabian On 01/24/2011 09:45 PM, pat marion wrote: You are using 3.8.0, not 3.8.1. If you use 3.8.1 to generate the trace script you will not receive these errors. Your script can also be fixed by hand- editing test_trace.py and move the lines at the very bottom modifying Slice1, Slice2 and Slice3. Moving the lines up so they appear after the constructors of Slice1, Slice2, and Slice3. Pat On Mon, Jan 24, 2011 at 3:08 PM, Fabian Braennstroem f.braennstr...@gmx.de mailto:f.braennstr...@gmx.de wrote: Hi, thanks. I get this error message: Traceback (most recent call last): File string, line 382, in module File /home/gcae504/HOME/Dissertation/simulation_calc/OpenFOAM/ThirdParty-1.7.x/platforms/linux64Gcc/paraview-3.8.0/lib/paraview-3.8/paraview/servermanager.py, line 201, in __setattr__ to add this attribute.) AttributeError: Attribute SelectedMapperIndex does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. I attached two pictures (test.png is the one create manually and test2.png the one create with the script) and the script. Thanks for your help! Best Regards! Fabian On 01/24/2011 08:57 PM, pat marion wrote: Hi Fabian, Regarding your issue of python trace state not replicating your paraview state exactly, I believe both issues you quote (camera position and cut filter's slice property) have been addressed in the latest version of paraview. If not, can you list the steps required to repeat the problem? I can't find bug reports for these issues, but below I have copied the git logs for the commits the addressed the issues. Pat commit
[Paraview] William Oquendo invited you to Dropbox
William Oquendo wants you to use Dropbox to sync and share files online and across computers. Get started here: http://www.dropbox.com/link/20.SR7vUURTak/NjYyMzYxMDkwNw?src=referrals_ab_bulk7 - The Dropbox Team To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/8ecef82742d2/paraview%40paraview.org___ 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://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] histogram
The Histogram filter requires a vtkDataSet on its input. vtkTable is not one since Tables have no inherent shape in a 3D space. The Table To Points and Table To Structured Grid filters convert vtkTables to vtkDataSets, but in either case you need to tell the filter which columns from the table it can use for the x,y and z coordinates of the vtkDataSet. A hackish way to do the conversion then is to add a column of dummy data to the file and then make a 1D vtkDataSet out of it. Feel free though to add a request for something more direct on user voice and we will consider adding it to upcoming ParaView releases. thanks, David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Tue, Jan 25, 2011 at 5:20 PM, Nima Emadi deeep...@gmail.com wrote: Dear all, I have a CSV file per snapshot which contains two large columns of data. I'd like to make histogram of those data. The idea is to have the animation of the histogram + the main visualisation in the same frame. I don't know how to build the input data needed for the histogram filter. Does anyone have an idea? Best, Nima ___ 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://www.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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] William Oquendo invited you to Dropbox
Sorry for this miss-sending! Please ignore it! Best regards / Cordialmente, -- William Oquendo Phd Candidate Simulation Of Physical Systems Group Universidad Nacional de Colombia Linux User # 321481 * Este correo puede carecer de tildes o eñes ya que el teclado no contiene estos caracteres. Presento excusas por eso. * On Wed, Jan 26, 2011 at 12:02 PM, Dropbox no-re...@dropboxmail.com wrote: William Oquendo wants you to use Dropbox to sync and share files online and across computers. Get started here.http://www.dropbox.com/link/20.a1_y6ujUtO/NjYyMzYxMDkwNw?src=referrals_ab_bulk7 - The Dropbox Team To stop receiving invites from Dropbox, click herehttp://www.dropbox.com/bl/8ecef82742d2/paraview%40paraview.org © 2011 Dropbox ___ 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://www.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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Paraview Python Script with PVFWrap
Hello Pat, thanks for the explanation and help! Best Regards! Fabian On 01/26/2011 04:42 PM, pat marion wrote: Hi Fabian, Please remember to include the paraview mailing list when you reply. What you report is a bug, but you can avoid it- when you open your openfoam dataset you should check each block that you want to load *before you hit apply for the first time* The problem is the first time you load your data and click apply, paraview sees a multiblock dataset containing only unstructured grid data, so it creates an unstructured grid display. This display has properties related to volume rendering, and these properties are recorded in the trace script. Later you must have enabled more blocks, so that multiblock dataset now contains unstructured grid and polydata. When the trace script is replayed, paraview sees the unstructured grid and polydata datasets, so it creates a geometry display instead of an unstructured grid display. The geometry display lacks the volume rendering properties. Pat On Tue, Jan 25, 2011 at 2:33 PM, Fabian Braennstroem f.braennstr...@gmx.de mailto:f.braennstr...@gmx.de wrote: Hi to you both, I just checked it with 3.8.1... a new trace_state file. There I got theses error messages (one after another), each time I got the errro I just commented out the lines in the python file, which I attached (I attached the openfoam case, if you need it): Traceback (most recent call last): File string, line 198, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute SelectedMapperIndex does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. Traceback (most recent call last): File string, line 225, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute ScalarOpacityUnitDistance does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. Traceback (most recent call last): File string, line 232, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute ScalarOpacityFunction does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. Traceback (most recent call last): File string, line 241, in module File /home/kitware/Kitware/ParaView-3.8.1/build/Utilities/VTKPythonWrapping/site-packages/paraview/servermanager.py, line 201, in __setattr__ AttributeError: Attribute ExtractedBlockIndex does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. It works very nice, after commenting these lines out! Best Regards! Fabian On 01/24/2011 09:45 PM, pat marion wrote: You are using 3.8.0, not 3.8.1. If you use 3.8.1 to generate the trace script you will not receive these errors. Your script can also be fixed by hand- editing test_trace.py and move the lines at the very bottom modifying Slice1, Slice2 and Slice3. Moving the lines up so they appear after the constructors of Slice1, Slice2, and Slice3. Pat On Mon, Jan 24, 2011 at 3:08 PM, Fabian Braennstroem f.braennstr...@gmx.de mailto:f.braennstr...@gmx.de mailto:f.braennstr...@gmx.de mailto:f.braennstr...@gmx.de wrote: Hi, thanks. I get this error message: Traceback (most recent call last): File string, line 382, in module File /home/gcae504/HOME/Dissertation/simulation_calc/OpenFOAM/ThirdParty-1.7.x/platforms/linux64Gcc/paraview-3.8.0/lib/paraview-3.8/paraview/servermanager.py, line 201, in __setattr__ to add this attribute.) AttributeError: Attribute SelectedMapperIndex does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. I attached two pictures (test.png is the one create manually and test2.png the one create with the script) and the script. Thanks for your help! Best Regards! Fabian
Re: [Paraview] Install Rules for System HDF5 absent
Sweet. Thanks. I'll pull the latest and see what happens.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Jan 24, 2011, at 10:03 PM, David Partyka wrote:
Hi Mike,
There is now an advanced option PARAVIEW_FIXUP_BUNDLE_SEARCH_PATHS that you
can append directories for fixup bundle to search.
On Thu, Dec 30, 2010 at 3:28 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
#2 I think would add the most flexibility as I have other libraries that I
also need to get included in the install.
#1- You are right of course. In my case (on windows) the location really
isn't a system library but I could see where on Linux and OS X it could go
VERY wrong by including those libraries. So #2 would just be dandy.
Thanks
___
Mike Jackson www.bluequartz.net
On Dec 30, 2010, at 3:03 PM, Dave Partyka wrote:
This isn't supported. Especially because USE_SYSTEM_ most likely means your
library is in /usr/lib on other platforms. Granted the same argument could
be made against the 4 libraries you listed. ;-)
What you could do is
1. add custom install rules via PARAVIEW_EXTRA_INSTALL_RULES_FILE ( I just
remembered you had a previous request to allow this to have multiple files.)
2. I could provide a cache variable for you to set that gets appended to
DIRS.
On Thu, Dec 30, 2010 at 1:49 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
I am using a system installed hdf5 for my builds of ParaView. The issue
is when I go to run the INSTALL rule in Visual Studio I get failures
because the HDF5 DLL file can not be found. This is because of the
following code::
IF(PARAVIEW_BUILD_QT_GUI)
list(APPEND DIRS ${QT_BINARY_DIR} ${QT_LIBRARY_DIR})
ENDIF(PARAVIEW_BUILD_QT_GUI)
IF(VTK_USE_FFMPEG_ENCODER)
get_filename_component(FFMPEG_DIR ${FFMPEG_avcodec_LIBRARY} PATH)
list(APPEND DIRS ${FFMPEG_DIR})
ENDIF(VTK_USE_FFMPEG_ENCODER)
IF(PARAVIEW_ENABLE_PYTHON)
get_filename_component(PYTHON_BIN_DIR ${PYTHON_EXECUTABLE} PATH)
get_filename_component(PYTHON_LIB_DIR ${PYTHON_LIBRARY} PATH)
list(APPEND DIRS ${PYTHON_BIN_DIR} ${PYTHON_LIB_DIR})
ENDIF(PARAVIEW_ENABLE_PYTHON)
IF(PARAVIEW_USE_MPI)
get_filename_component(MPI_LIB_DIR ${MPI_LIBRARY} PATH)
get_filename_component(MPI_BIN_DIR ${MPIEXEC} PATH)
list(APPEND DIRS ${MPI_LIB_DIR} ${MPI_BIN_DIR})
ENDIF(PARAVIEW_USE_MPI)
set(_extension)
set(_dir ${PV_INSTALL_LIB_DIR})
IF(WIN32)
set(_extension .exe)
set(_dir bin)
ENDIF(WIN32)
set(APPS \${CMAKE_INSTALL_PREFIX}/${_dir}/paraview${_extension}) # paths
to executables
INSTALL(CODE
include(\${ParaView_CMAKE_DIR}/BundleUtilities.cmake\)
fixup_bundle(\${APPS}\ \\ \${DIRS}\)
COMPONENT BrandedRuntime)
The issue is the DIRS variable which makes no attempt to add any of the
extra directories that might be needed in case a *_USE_SYSTEM_* variable
is set. I can hack in a rule for HDF5 but a much cleaner approach would be
to track which _USE_SYSTEM_* variables are set and loop over those to
setup the correct directories. Or did I just completely miss something?
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
___
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://www.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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Tracing Zoom
Hi, Anyone have an idea why the trace python shell don't record the zooming position and the images are not saved in the specified area! Any solution for that? Thanks, -Hussein ___ 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://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Tracing Zoom
Hi Hussein, Could you elaborate on the problem you are experiencing? I'm not sure what you mean when you say that the images are not saved in the specified area. As for zooming position, python trace should record camera properties such as position, focal point, and parallel scale depending if you are using parallel or perspective projection. Pat On Wed, Jan 26, 2011 at 5:04 PM, Hussein Ezzat hussein_ezzat2...@yahoo.comwrote: Hi, Anyone have an idea why the trace python shell don't record the zooming position and the images are not saved in the specified area! Any solution for that? Thanks, -Hussein ___ 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://www.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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Tracing Zoom
Pat, I am trying to save an animation happening on a map. So I record the trace, and use the button zoom to box and chose the specified area on the map; say the map is for North America and the specified Area if for Gulf of Mexico. When I run the script, it saved the images for the whole map North of America -zoom out you can say- not Gulf of Mexico. From: pat marion pat.mar...@kitware.com To: Hussein Ezzat hussein_ezzat2...@yahoo.com Cc: paraview paraview@paraview.org Sent: Wed, January 26, 2011 4:13:44 PM Subject: Re: [Paraview] Tracing Zoom Hi Hussein, Could you elaborate on the problem you are experiencing? I'm not sure what you mean when you say that the images are not saved in the specified area. As for zooming position, python trace should record camera properties such as position, focal point, and parallel scale depending if you are using parallel or perspective projection. Pat On Wed, Jan 26, 2011 at 5:04 PM, Hussein Ezzat hussein_ezzat2...@yahoo.com wrote: Hi, Anyone have an idea why the trace python shell don't record the zooming position and the images are not saved in the specified area! Any solution for that? Thanks, -Hussein ___ 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://www.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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Paraview
Would anyone have any knowledge of how to control the frame rendering rate when saving an animation?I notice that if I make an animation at 5 - 10 fps, the resulting avi file looks perfect. However, if I use the same animation sequence and render at 20 - 30 fps, the resulting avi file has many holes and greyed out areas in the frames beginning about half way through the animation. I'm wondering if it is possible for the frame rendering to get far enough ahead of the IO writing to disk such that frame information can be lost?If the buffer that is holding the frames renders fills up, wouldnt it wait for IO writing to disk to catch up first? thanks, Gerard Lunar and Planetary Lab Tucson AZ ___ 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://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Tracing Zoom
If you want to email me the trace script I'd be happy to take a look. It looks like an unwanted camera reset is ocuring. Pat On Wed, Jan 26, 2011 at 6:01 PM, Hussein Ezzat hussein_ezzat2...@yahoo.comwrote: I am using version 3.8.1 64bit Attached 2 pictures, Pic1 is what I want and record the trace for, Pic2 is the outcome of the script. I can't figure out why the trace script outcome is different from what is expected to be!! -- *From:* pat marion pat.mar...@kitware.com *To:* Hussein Ezzat hussein_ezzat2...@yahoo.com *Cc:* paraview paraview@paraview.org *Sent:* Wed, January 26, 2011 4:55:53 PM *Subject:* Re: [Paraview] Tracing Zoom Hi, Which version of paraview are you using? This bug should not occur in the latest paraview release. If you are using 3.8.0 you will need to upgrade. After the upgrade you'll need to re-record the trace script. Or, you can fix your existing trace script by adding a call to Render() before the camera position is set. Pat On Wed, Jan 26, 2011 at 5:21 PM, Hussein Ezzat hussein_ezzat2...@yahoo.com wrote: Pat, I am trying to save an animation happening on a map. So I record the trace, and use the button zoom to box and chose the specified area on the map; say the map is for North America and the specified Area if for Gulf of Mexico. When I run the script, it saved the images for the whole map North of America -zoom out you can say- not Gulf of Mexico. -- *From:* pat marion pat.mar...@kitware.com *To:* Hussein Ezzat hussein_ezzat2...@yahoo.com *Cc:* paraview paraview@paraview.org *Sent:* Wed, January 26, 2011 4:13:44 PM *Subject:* Re: [Paraview] Tracing Zoom Hi Hussein, Could you elaborate on the problem you are experiencing? I'm not sure what you mean when you say that the images are not saved in the specified area. As for zooming position, python trace should record camera properties such as position, focal point, and parallel scale depending if you are using parallel or perspective projection. Pat On Wed, Jan 26, 2011 at 5:04 PM, Hussein Ezzat hussein_ezzat2...@yahoo.com wrote: Hi, Anyone have an idea why the trace python shell don't record the zooming position and the images are not saved in the specified area! Any solution for that? Thanks, -Hussein ___ 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://www.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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Paraview
Maybe you could try writing individual images, and then stitch them together using some free software? As far as the individual frames goes, try opening up the Animation View, change the mode to Sequence, and the number of frames to 200. Next, try Filters/ Temporal/ Temporal Interpolator. If this doesn't save properly, please let me know what type of data you are using, and I will look into it. Alan -Original Message- From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On Behalf Of Gerard Droege Sent: Wednesday, January 26, 2011 4:22 PM To: paraview@paraview.org Subject: [Paraview] Paraview Would anyone have any knowledge of how to control the frame rendering rate when saving an animation?I notice that if I make an animation at 5 - 10 fps, the resulting avi file looks perfect. However, if I use the same animation sequence and render at 20 - 30 fps, the resulting avi file has many holes and greyed out areas in the frames beginning about half way through the animation. I'm wondering if it is possible for the frame rendering to get far enough ahead of the IO writing to disk such that frame information can be lost?If the buffer that is holding the frames renders fills up, wouldnt it wait for IO writing to disk to catch up first? thanks, Gerard Lunar and Planetary Lab Tucson AZ ___ 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://www.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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
