Then, it may be that conversion fails, since the end of the file may contain some leftover data from the previous time, if the filelength has changed due to some other reason. One important warning is due: when you run a simulation for some reason twice, and you did not erase the previously created *.dat files, these files are overwritten (if the base_filename has not changed). ![]() The same steps are to be taken for obtaining any of the other precoded data formats. ** Note that all the steps below assume you're running on a single CPU. We now give some brief info on how to use the same executable amrvac (which you already compiled and used to obtain output *.dat files with), to convert a single or all *.dat file(s) to one of these formats. ![]() Furthermore, this part of the code is subject to continuous change and improvement, and we welcome extra contributions. ![]() Also, this info will not explain you how to use the mentioned software for visualization, but just explain how to do the conversion. The many possibilities include conversion to *.vtu ( VTK U*nstructured data format) directly readable by Paraview (or ViSiT), to _.plt_ format for the commercial package Tecplot. Therefore, we created the convert.t module, which ensures that this post-process data file conversion can be done with the same executable (but possibly even on a different platform). However, in many instances, one would like to use data formats that are directly readable by some of the more widespread visualization software packages. Since late 2019, it can be directly read, visualised and analysed with the Python package yt, see our documentation to get started with yt. Additional variables can be added in the *.dat files as explained here. the *.dat files usable for restart, contain all the conservative variables in all gridblocks, and hence suffice for visualization.
0 Comments
Leave a Reply. |