Changes between Version 4 and Version 5 of Examples/WRF

Timestamp:

07/20/18 12:09:38 (6 years ago)

Author:

Herwig Zilken

Comment:

--

Examples/WRF

@@ -89 +89 @@
 == !ParaView Script ==
 The images are generated by the script "paraview_movie_script.py", or, more specifically, by an upgraded version called "paraview_movie_script_test.py", which was developed later and can better handle the progression from time animation to the camera flight.
-This script loads structuredGrid.xdmf for 3D volume rendering and structuredGrid_2D.xdmf for surface coloring.
+This script loads "structuredGrid.xdmf" for 3D volume rendering and "structuredGrid_2D.xdmf" for surface coloring.
 Also some colortable are loaded from file (e.g. "colortable_qvapor.json") and assigned to the variables. The 3D structured grid is resampled to image data of size 1600x1600x100, which is volume rendered for one variable (e.g. CLDFRA or QVAPOR).
 Predefined camera positions are loaded from "cam4.pvcvbc" and are used in 3 keyframes for the camera flight.
 
-In a first try we had problems with !ParaView, because during the camera flight, which only shows the last timestep, !ParaView loaded this single timestep again and again for each camera move, slowing down the rendering process significantly. Therefore the script "paraview_movie_script_singletimestep.py" was developed, which (in connection with "make_xdmf_structuredgrid_singletimesteps.py") only loaded the last timestep for the camera flight. Actually, this approach is no longer necessary, as a workaround was found and implemented in "paraview_movie_script_test.py". The workaround was just to disable the timeTrack from using the animation time by "timeTrack.UseAnimationTime = 0".
+In a first try we had problems with !ParaView, because during the camera flight, which only shows the last timestep, !ParaView loaded this single timestep again and again for each camera move, slowing down the rendering process significantly. Therefore in a first try the script "paraview_movie_script_singletimestep.py" was developed, which (in connection with "make_xdmf_structuredgrid_singletimesteps.py") only loaded the last timestep for the camera flight. Actually, this approach is no longer necessary, as a workaround was found and implemented in "paraview_movie_script_test.py". The workaround was just to disable the timeTrack from using the animation time by "timeTrack.!UseAnimationTime = 0".