Working with VTK Files
The Visualization Toolkit (VTK) establishes a data format which is designed for use in high performance computing (HPC) applications. Detailed documentation of data format can be found on the website at VTK File Formats. This page provides a quick start guide to working with VTK files generated by FDS.
This section will demonstrate a basic example to generate VTK data with FDS and visualize the results in Paraview.
- Installed FDS: Examples/VTK/storage.fds
- Source FDS: Verification/VTK/storage.fds
- Add "WRITE_VTK=T" to the &DUMP namelist. This tells FDS to generate VTK data.
- Add "RESULTS_DIR='storage_results'" to the &DUMP namelist. This tells FDS to locate all the VTK and binary data in the subdirectory, "storage_results".
- The namelist should now be:
&DUMP NFRAMES=100, DT_CTRL=1., DT_DEVC=10., DT_HRR=10., SIG_FIGS=4, WRITE_VTK=T, RESULTS_DIR='storage_results' /
- Navigate to the directory with the input file
- Run fds with the command:
mpiexec -np 8 fds storage.fds
- Open Paraview
- Click File->Load State
- Select the "storage_paraview.py" file and click ok
- Manipulate the viewport by using the preset views or clicking in the window and dragging the mouse.
- Click play to start the animation of the fire, smoke, and sprinkler droplets.
- After sprinklers activate, the view should be similar to the following.
- Hide the fire, smoke, and particles by clicking the open "eye" icon next to these two datasets in the pipeline browser
- Show the slice at a z-axis height of 7.4m by clicking the closed "eye" icon in the pipeline browser.
- Click on the z-axis slice in the pipeline browser and the properties window will appear.
- Click the drop down icon under "Coloring" and change it to "TEMPERATURE".
- Use a similar approach to activate the "3D Slice Extraction" in the pipeline browser. Click on "3D Slice Extraction" in the pipeline browser and a plane visualization will appear in the viewport which can be used to translate and rotate extracted plane from the 3D data.
- Move the plane to Origin: -3, 0, 4.5 with Normal 1, 0, 0 and click apply.
- Click on the drop-down icon under "Coloring" and change it to "TEMPERATURE".
- Deselect the "3D Slice Extraction" from the pipeline browser by clicking any of the other datasets or the "builtin" root tree at the top. This will hide the plane which was used to move the slice extraction plane.
- Click the run icon to see the animation of slice data.
- Hide the slice data from the previous step by clicking the "eye" icon for each of the slice datasets in the pipeline browser.
- Click the "eye" icon next to the boundary data and select coloring by "HRRPUA". You may see overlap between the geometry and boundary data. This can be removed by hiding the geometry data.
The python state file interface in Paraview has syntax changes over different releases of Paraview. This error typically occurs when the configuration file generated by FDS tries to modify a parameter that does not exist in the version of Paraview used. If this occurs you can comment out the line in the Paraview state file and reload it. Please report these observations in the issue tracker with the tag "Paraview compatibility" and provide your FDS input file and Paraview version.
Using Paraview on a remote system depends on how the server is configured. Oak Ridge provides information a typical configuration OLCF Paraview Guide. See the user guides for existing HPC configurations and discuss with the system administrator for configuration of new systems.
Add the flag VTK_BINARY=F to the &MISC to change from binary to ASCII output in VTK files.
See the Paraview User's Guide.
See the Paraview User's Guide.
The process flow for reporting issues with the VTK output are the following:
- Verify that the VTK data output by FDS is valid. Swap to ASCII output for the files and verify the crash still occurs.
- If the crash occurs for binary data but not ASCII data, report the issue in the FDS Issue Tracker with the tag "VTK ASCII/Binary Data" and include the FDS input file, FDS version, and Paraview version.
- If the crash occurs in both data types, open the ASCII data and manually inspect the data fields for unexpected outputs (e.g., missing data, underflow/overflows, precision erors, etc.). If the crash occurs for binary data but not ASCII data, report the issue in the FDS Issue Tracker with the tag "VTK ASCII/Binary Data" and include the FDS input file, FDS version, and Paraview version.
- If no abnormalities are observed in the VTK data, report the issue to the Paraview Issue Tracker.
Report the feature request to the Paraview Issue Tracker.