Skip to content

Conversation

@iwheel
Copy link
Contributor

@iwheel iwheel commented Apr 4, 2022

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

iwheel added 3 commits April 4, 2022 11:37
…G (PMMG_Get_NodeCommunicators_nodesf). This is required as Fortran cannot create a pointer to a pointer with different memory allocations on each index. The index of the neighbouring partition/process is given as an input and shared nodes with this partition returned. All shared nodes can be returned by looping through this function when using the Fortran API.
…as not previously guarenteed as global number calculation was only invoked when saving the mesh to file which is not always desirable when using the API.
@Algiane
Copy link
Member

Algiane commented Apr 8, 2022

Hi @iwheel ,

Thanks for your very clean work and contribution and for its comprehensive dexcription.

I would like to propose to rename the new PMMG_Get_NodeCommunicator_nodesf in PMMG_Get_ithNodeCommunicator_nodes as it seems more consistent with the other API names: does this look ok to you ?

Best Regards,
Algiane

@iwheel
Copy link
Contributor Author

iwheel commented Apr 8, 2022

That makes more sense and looks good to me. I assumed the new routine would be renamed but thought I'd leave that up to you.

Best,
Iain

@Algiane
Copy link
Member

Algiane commented Apr 8, 2022

Is it possible to authorize me to push inside your fork so I can bring modifications to the PR?
(I think that the doc to do this is here)

Thank you by advance,

@iwheel
Copy link
Contributor Author

iwheel commented Apr 8, 2022

I don't seem to have the option described in the link. I can just give you temporary write permission to the fork if that works?

@Algiane Algiane merged commit 5b4622a into MmgTools:feature/tetFromTria-API Apr 9, 2022
@Algiane
Copy link
Member

Algiane commented Apr 9, 2022

Thanks again for your contribution: I will merge the PR and submit a new one to integrate the feature/tetFromTria-API branch inside the develop one.

Have a nice day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants