BASEMENTBasic Simulation Environment for computation of environmental flow and natural hazard simulationLaboratory of Hydraulics, Hydrology and Glaciology (VAW)ETH Zurich |
You are not logged in.
Pages: 1
Dear Community,
I am facing a strange problem here: I succesfully run some morphological simulations and I can perfectly display the results with paraview!
Unfortunately, crayfish is having some issues:
some results are missing (ns_hyd_discharge and ns_mor_discharge)
the other results are not as expected, i.e. not the same as what I see in ParaView (which is much more reasonable)
I can solve this by producing some rasters with ParaView and importing them to QGIS.
I will also write on github to the Lutra guys!
Cheers
Matteo
Offline
Partial answer to my post:
as for point 1: it is reasonable that ns_hyd_discharge is not present in qgis, since it is a nodestring result (time series).
So far still no answers by Lutra people, the link to the request is this
Offline
Apparently it is a matter of "file format" (not sure what they mean by that!)
Maybe you guys could look up the issue on BASEMENT side and see if it is only me having issues.
Again, the results are ok in ParaView and not corrrectly displayed in QGIS, which is "bad" because one cannot print the results over a georeferenced map.
Offline
Hi Matteo
The visualization with QGIS in the MDAL issue definitely looks strange, but i have not encountered similar issues with displaying the flow velocity in QGIS. I failed to reproduce the issue for the Flaz tutorial (B - unsteady inflow). I cross-verified the flow velocity magnitude in Paraview and QGIS and get the same results (aside from the slightly different color scale):
Since we are using different OS, I will see if it is related to this.
I am assuming you were comparing the exact same time step? Maybe you could verify for one specific cell via the cell ID, if the values in the .h5 file match the ones from QGIS or Paraview?
[Update]
Also under Windows I get identical flow velocity magnitudes in Paraview and QGIS. For further investigation it would be helpful to have a test case that reproduces the problem.
Best regards
Matthias
Offline
Hi Matthias,
I will look it up for sure, and report back to you!
Thanks,
Matteo
Offline
Hi Matthias,
I tried with the Flaz tutorial and everything works fine.
I will send you the data that cause the mess.
Thanks,
Matteo
Offline
Case closed thanks to Matthias support: the elements and nodes in the 2dm file must be listed in ascending order. Once this is done everything works fine again.
The problem has been solved on the BASEMENT side by correcting basemesh!
Thanks!
Offline
Pages: 1