raback wrote:Hi gos
This was just fixed.
Thanks Peter, the VTK files now work with Visit.
However, VTU files still have the same problem.
There is also a discrepancy between the names exported in the .SIF file, and the variable names in the VTK / VTU file:
The following variable names are exported to VTK or VTU file:
Equation = Result Output
Single Precision = True
Procedure = "ResultOutputSolve" "ResultOutputSolver"
Output File Name = VTK_Data
Output Format = Vtk
Binary Output = True
Scalar Field 1 = Temperature
Scalar Field 2 = Heat Source
The VTK file then lists:
SCALARS Temperature double /* This matches the variable name in the SIF file */
SCALARS Heat.source double /* This DOE NOT match the variable name in the SIF file */
The VTU file then lists:
<DataArray type="Float32" Name="temperature" NumberOfComponents="1" format="appended" offset="0"/> /* Same name as in SIF file, but Case DOES NOT match */
<DataArray type="Float32" Name="heat source" NumberOfComponents="1" format="appended" offset="556"/> /* Same name as in SIF file, but Case DOES NOT match */
Visit is case sensitive, so this leads to problems when I use scripts to process the files...Suggested Solution:
It would be very nice if the names in the SIF file would be reproduced exactly in the VTK & VTU files.