Null metric det error


#1

Good evening to everyone,

I am using mmg2d (./mmg2d_03) to refine and I get the following output:

– MMG2D, Release 5.3.12 (Oct. 2, 2018)
Copyright © IMB-LJLL, 2004-
Nov 15 2018 10:45:36

– INPUT DATA
%% out_step=2.mesh OPENED
%% out_step=2.sol OPENED
– DATA READING COMPLETED. 0.043s

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
MODULE MMG2D: 5.3.12 (Oct. 2, 2018)
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

– MMG2DLIB: INPUT DATA
– INPUT DATA COMPLETED. 0.000s

– PHASE 1 : DATA ANALYSIS

– MESH QUALITY 22164
BEST 0.999997 AVRG. 0.962686 WRST. 0.637565 (17146)
HISTOGRAMM: 100.00 % > 0.12
– PHASE 1 COMPLETED. 0.006s

– PHASE 2 : ANISOTROPIC MESHING
1026 splitted, 0 collapsed, 318 swapped, 4 iter.

– GRADATION : 1.300000
5170 splitted, 5 collapsed, 1450 swapped, 4 iter.

Error: _MMG5_interpmet22: at least 1 negative eigenvalue: -0.000000

Error: _MMG2_intmet_ani: at least 1 naive interpolation.

Error: _MMG5_interpmet22: null metric det : 0.000000E+00

Error: _MMG2_movintpt_ani: impossible to locate at least 1 gradient - abort.

    15082 splitted,    10061 collapsed,     4272 swapped,   119465 moved, 4 iter. 

– PHASE 2 COMPLETED. 0.984s

– MESH QUALITY 44754
BEST 0.999999 AVRG. 0.949752 WRST. 0.048647 (17829)
HISTOGRAMM: 100.00 % > 0.12

– MESH PACKED UP
NUMBER OF VERTICES 22569 CORNERS 239
NUMBER OF TRIANGLES 44754
NUMBER OF EDGES 1317

MMG2DLIB: ELAPSED TIME 0.998s

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
END OF MODULE MMG2D
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

– WRITING DATA FILE out_step=2.o.mesh
%% out_step=2.o.mesh OPENED
%% out_step=2.o.sol OPENED
– WRITING COMPLETED

ELAPSED TIME 1.122s

I checked my metric and nowhere I have a null metric (i.e. the determinant of my metric), while instead I get.
null metric det : 0.000000E+00

What can I do to avoid this problem?

I attach my mesh and sol files.

Regards,

Riccardo

.out_step=2.mesh (782.1 KB)
out_step=2.sol (387.8 KB)


#2

Hi Riccardo,

Thank you for this bug report.
It is patched in the master branch and in the v5.3.13 hotfix.

Regards,

Algiane


#3

Fixed solved, thank you!

Riccardo


#4