Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap

Clearly defined bug reports and their fixes
Post Reply
tomatoma
Posts: 12
Joined: 12 Feb 2016, 23:04
Antispam: Yes

Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap

Post by tomatoma »

Hello,

attached is a minimal example where 'Save Coordinates' crashes when the HeatGap between 2 bodies is active.
mesh_image.jpg
mesh_image.jpg (54.14 KiB) Viewed 1883 times
OS: Win 8.1

Thanks,
Matteo
Attachments
Mesh_1.7z
(64.64 KiB) Downloaded 136 times
Rich_B
Posts: 421
Joined: 24 Aug 2009, 20:18

Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap

Post by Rich_B »

Hello,

If one changes 'Discontinuous Galerkin' in Solver 1 to 'Discontinuous Bodies', then the example runs without a seg fault.

Rich.
tomatoma
Posts: 12
Joined: 12 Feb 2016, 23:04
Antispam: Yes

Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap

Post by tomatoma »

Hi Rich,

the purpose of the 'Discontinuous Galerkin' line is to implement a heat gap between the two bodies:
Result_OK.JPG
Result_OK.JPG (30.41 KiB) Viewed 1872 times
If one replaces the line 'Discontinuous Galerkin' with 'Discontinuous Bodies' in solver 1, then the heat gap is ignored by the solver:
Result_notOK.JPG
Result_notOK.JPG (29.35 KiB) Viewed 1872 times
Thanks,
Matteo
Rich_B
Posts: 421
Joined: 24 Aug 2009, 20:18

Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap

Post by Rich_B »

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.
raback
Site Admin
Posts: 4812
Joined: 22 Aug 2009, 11:57
Antispam: Yes
Location: Espoo, Finland
Contact:

Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap

Post by raback »

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
tomatoma
Posts: 12
Joined: 12 Feb 2016, 23:04
Antispam: Yes

Re: Save Coordinates Crashes with (Discontinuous Galerkin) Heat Gap [SOLVED]

Post by tomatoma »

Hello Peter,

problem solved!
Thanks!

Matteo
Post Reply