Open MakisH opened 4 months ago
Renaming the file to .vtk
seems to work. Not sure if this is a ParaView issue, or if the files ASTE writes (via its VTK dependency) are broken.
Note that the .vtu
files that preCICE exports are ASCII, while the .vtu
files that ASTE writes are binary.
Do you use a run script? Could you please provide the commands to use? The 'issue' here is that paraView selects a default reader according to the file prefix, which is wrong in our case.
Do you use a run script? Could you please provide the commands to use? The 'issue' here is that paraView selects a default reader according to the file prefix, which is wrong in our case.
I am just executing the steps of the training course. Task 3 of the MAP module:
precice-aste-run -p B --mesh Propagator-Mesh --data "Color" -c ../precice-config.xml \
--output Propagator-Mesh-out
I switched the preCICE exports from
.vtk
to.vtu
and I usedprecice-aste-run
to compute the mapping, outputting to a thirdPropagator-Mesh-out.vtu
file. If I try to open thisPropagator-Mesh-out.vtu
in ParaView, ParaView crashes (5.12 crashes, 5.11.2 tells me it does not have a reader).The preCICE exports (also
vtu
) work normally on ParaView.One difference is that the file is binary: mesh.tar.gz