Fix HERMES reading of boundary nodes
Reference issue
Fix #1090 (closed)
Description
Boundary information on MED files is now correctly read, regardless of the presence or not of a boundary conditions file
Checklist
All Merge Requests:
-
Update NEWS.txt
to describe your changes. -
Run compile_telemac.py --check
to check FORTRAN coding conventions. -
Run pylint
to check Python coding conventions. -
If you added new files, run compile_telemac.py --clean --rescan
and commit the updatedcmdf
file(s) accordingly. -
Run compile_telemac.py --clean
for both normal and debug configurations. -
Run validate_telemac.py
for both normal and debug configurations. -
Run validate_telemac.py --notebook
for both normal and debug configurations. -
Run doc_telemac.py
if there are any modifications in the documentation. -
Run damocles.py --eficas
if there are any modifications in the dictionaries.
In addition, for a new feature:
-
Check that your feature works in both serial and parallel modes. -
Add at least one test case to check the functionality (with documentation, graphics and VnV script) -
Update the documentation for the module in which your feature will be available.
Edited by Boris Basic
Merge request reports
Activity
added lang:fortran type:bug type:enhancement labels
assigned to @boris.basic
added 6 commits
-
107f322d...a3840ea2 - 4 commits from branch
main
- 2b10cf57 - Fix HERMES reading of boundary nodes
- 420889a5 - Add NEWS.txt
-
107f322d...a3840ea2 - 4 commits from branch
requested review from @chi-tuan.pham
added 1 commit
- 66860ad5 - [hermes] Fix reading of MED boundary nodes and elements
mentioned in commit c86582cf
Please register or sign in to reply