Thanks for implementing nextfempy module

[Luciano Jacinto]

Thanks for implementing a new NextFEM interface for Python. I’ve tried using the recent module nextfempy and everything ran well.

At least at one point it seems faster than using pythonnet package: there is no need to call nextFEM app each time the model is analyzed.

I will convert my NextFEM templates to this newer interface.

[NextFEM Admin]

Dear Luciano,
thanks for your appreciation.
NextFEMpy was developed to allowing everyone to use NextFEM Designer without loading all the libraries, but through the REST API server (included in NextFEM Designer plugins).
A sample code for VIKTOR platform is already available in our GitHub page, we’ll show the usage also with VIKTOR asap.

NextFEMpy was designed to be compatible with all the previous API used with pythonnet. There’s no need to convert old code for more perfomance, it should be the same with both approaches.

Also NextFEM Server could be used with the same approach; we’ll provide samples.

[Luciano Jacinto]

It seems that there are some small differences between both API. For example, in the newer Python API the elemsNumber property returns a string while in the earlier API returns an integer. Or, at least, that seems to me. But that is not a big problem, because we can convert easily a string into an integer and vice versa in Python.

[Author]

Posts