Page 2 of 2
Re: Mesh quality issue and slow running code
Posted: Mon Aug 11, 2014 3:55 pm
by David Vincent
Yvan Fournier wrote:Hello,
"Warnings" can be ignored (though it is recommended to check them to make sure they are not too important), but in your case, if the Preprocessor has a fatal error, either you file is corrupted (not too probable if it is a recent file generated by a recent version of SALOME), or there is a Preprocessor bug... According to the backtrace, the bug is in the I-deas reader, so it occurs at the earliest stages of preprocessing, basically during mesh import (long before quality can be "measured").
Could you post your mesh (ideally, the smallest mesh which produces the crash) to this forum. If it is confidential, you can send it to me by private message (if you are not allowed or do not want to send it, then building Code_Saturne with --enable-debug would at least add the code line numbers in the error traceback, but debugging on the real mesh will take must less time).
Regards,
Yvan
I failed to attach I-deas files ! Same thing by private message! Could you tell me how to post an attached file on the forum?
regards,
David Vincent
Re: Mesh quality issue and slow running code
Posted: Mon Aug 11, 2014 8:56 pm
by David Vincent
Yvan Fournier wrote:Hello,
"Warnings" can be ignored (though it is recommended to check them to make sure they are not too important), but in your case, if the Preprocessor has a fatal error, either you file is corrupted (not too probable if it is a recent file generated by a recent version of SALOME), or there is a Preprocessor bug... According to the backtrace, the bug is in the I-deas reader, so it occurs at the earliest stages of preprocessing, basically during mesh import (long before quality can be "measured").
Could you post your mesh (ideally, the smallest mesh which produces the crash) to this forum. If it is confidential, you can send it to me by private message (if you are not allowed or do not want to send it, then building Code_Saturne with --enable-debug would at least add the code line numbers in the error traceback, but debugging on the real mesh will take must less time).
Regards,
Yvan
I post the 2 mesh i-deas files into a zip.
regards,
David VINCENT
Re: Mesh quality issue and slow running code
Posted: Tue Aug 12, 2014 8:52 am
by Yvan Fournier
Hello,
There are 2 empty lines in you Block_1 mesh (one at 17310, the other just at 1765, 1 line before the last). Removing them, the mesh reads correctly. The second mesh reads fine in my case.
Did you edit the files under a text editor, or pass them through some filter, before reading them from Code_Saturne, or is this the "direct" Salome output ? In one case, it is a user error, in the other, a Salome Bug.
Regards,
Yvan
Re: Mesh quality issue and slow running code
Posted: Tue Aug 12, 2014 1:30 pm
by David Vincent
Yvan Fournier wrote:Hello,
There are 2 empty lines in you Block_1 mesh (one at 17310, the other just at 1765, 1 line before the last). Removing them, the mesh reads correctly. The second mesh reads fine in my case.
Did you edit the files under a text editor, or pass them through some filter, before reading them from Code_Saturne, or is this the "direct" Salome output ? In one case, it is a user error, in the other, a Salome Bug.
Regards,
Yvan
Hello,
I will remove the lines.
The files posted on the forum come from copies of .unv files, however Code_Saturne read the direct Salome Output mesh files - on attached pieces.
regards,
David Vincent
Re: Mesh quality issue and slow running code
Posted: Thu Aug 14, 2014 6:06 pm
by Yvan Fournier
Hello,
If Salome generated a bad file, it may be useful to report the bug on the salome-platform.org website (I can mention it to people on the Salome team, but a bug report would be most useful if you can provide them the scripts or the data which leads to this bug).
Regards,
Yvan