Changes to Fortran interface #53
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've made three changes each relates to one of my commits:
1: Fixes of bugs in API Fortran interface.
2: Addition of a new function PMMG_Get_NodeCommunicatorsf. Differs from the original function as it only returns the shared node information for a given neighbouring partition. This is because Fortran does not have the functionality to create a pointer pointer with different memory allocations on each index. Therefore the original function was not usable and just segfaulted.
3: Addition of a check when recovering global node/triangle numbers to check they have been calculated. Previously they are only calculated if the mesh was saved to file which always done when using the API.
I have created the pull request to the feature/tetFromTria-API as it had some added API functions required for Fortran interfacing.
With these changes ParMMG works with ElmerFEM (and Elmer/Ice) for both centralised and distributed meshes.
Let me know if you need any more information.
Best,
Iain