Hello,
attached is a minimal example where 'Save Coordinates' crashes when the HeatGap between 2 bodies is active.
OS: Win 8.1
Thanks,
Matteo
Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap
Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap
- Attachments
-
- Mesh_1.7z
- (64.64 KiB) Downloaded 184 times
Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap
Hello,
If one changes 'Discontinuous Galerkin' in Solver 1 to 'Discontinuous Bodies', then the example runs without a seg fault.
Rich.
If one changes 'Discontinuous Galerkin' in Solver 1 to 'Discontinuous Bodies', then the example runs without a seg fault.
Rich.
Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap
Hi Rich,
the purpose of the 'Discontinuous Galerkin' line is to implement a heat gap between the two bodies: If one replaces the line 'Discontinuous Galerkin' with 'Discontinuous Bodies' in solver 1, then the heat gap is ignored by the solver: Thanks,
Matteo
the purpose of the 'Discontinuous Galerkin' line is to implement a heat gap between the two bodies: If one replaces the line 'Discontinuous Galerkin' with 'Discontinuous Bodies' in solver 1, then the heat gap is ignored by the solver: Thanks,
Matteo
Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap
Hello Matteo,
If one changes 'Discontinuous Bodies' in the Result Solver section to 'Discontinuous Galerkin', it also lead to the seg fault. Note that the .vtu output file becomes significantly larger when both sections include 'Discontinuous Galerkin'. It also seems that the Result Solver and Save Scalar solver both perform the requested output, and then the seg fault occurs.
Rich.
If one changes 'Discontinuous Bodies' in the Result Solver section to 'Discontinuous Galerkin', it also lead to the seg fault. Note that the .vtu output file becomes significantly larger when both sections include 'Discontinuous Galerkin'. It also seems that the Result Solver and Save Scalar solver both perform the requested output, and then the seg fault occurs.
Rich.
-
- Site Admin
- Posts: 4841
- Joined: 22 Aug 2009, 11:57
- Antispam: Yes
- Location: Espoo, Finland
- Contact:
Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap
Hi
For DG you need some special steps to choose the value related to a node. These were missing and I just made the fix in devel branch.
For historical reasons (implemented first) the "save coordinates" chooses the closest node. Usually it is actually better to perform interpolation. This is activated by "Exact Coordinates = True" and works even with the old version.
-Peter
For DG you need some special steps to choose the value related to a node. These were missing and I just made the fix in devel branch.
For historical reasons (implemented first) the "save coordinates" chooses the closest node. Usually it is actually better to perform interpolation. This is activated by "Exact Coordinates = True" and works even with the old version.
-Peter
Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap [SOLVED]
Hello Peter,
problem solved!
Thanks!
Matteo
problem solved!
Thanks!
Matteo