Hi Eduardo, On 05/11/2018 13:46, Eduardo Ramos Fernandez wrote: > I realised I will have to be a bit invasive and change the baseline PyFR > code and add files to the package source tree to achieve my goals (maybe > I am wrong). > > There are mainly 2 issues: > > a ) Changing COMM_WORLD communicator manually. It would be would in > later PyFR versions to not assume MPI_COMM_WORLD is the communicator > used. This would be really easy to implement by allowing the pertinent > functions to accept a 'comm' parameter that the user can provide.
We can certainly do this in a future release; heretofore we have had no uses cases which require changing the communicator and we generally try to avoid adding functionality before we have a good use case. > b) Plugins directory is inside the package structure. Can I define my > custom plugins in an arbitrary folder and register them in PyFR manually? Yes. The only requirement is that the plugins be a subclass of BasePlugin and known to Python at the time when the integrator class is being constructed. Practically, this means that you simply need to have imported the class somewhere in your code (where does not matter). Let us know if you need us to extend the plugin functionality at all. Regards, Freddie. -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. Visit this group at https://groups.google.com/group/pyfrmailinglist. For more options, visit https://groups.google.com/d/optout.
