Idesbald Van den Bosch

Changed MPI C++ bindings to C bindings, as the C++ bindings have been deprecated in recent MPI

Changed import from scipy to numpy.

Changed python to python3 in makepackage.py.

Changed copyright year to 2024.

Hi ioanna, what target/freq were you testing? For me, the simulation did not succeed at all. On Thu, Sep 26, 2019 at 4:52 PM Ioanna Did ioanna@users.sourceforge.net wrote: Hello, I am trying to find the monostatic RCS of a UAV using Puma-EM. I tried to run a few simulations with a different angle step size to decide how big the step size can be without greatly deteriorating the accuracy of the plotted result. What I noticed was that I got different RCS values for the same angle and, most importantly,...

Hi Ioanna, thanks for the feedback. Indeed, the mesh is often the issue in this type of simulations, and spotting it can be difficult, especially with millions of edges! On Thu, Sep 26, 2019 at 5:11 PM Ioanna Did ioanna@users.sourceforge.net wrote: Hello, In case someone faces a similar issue and goes through this thread, the issue was that the CAD model was too detailed and had self-intersections. Commercial software also failed to complete a simulation with it. In the end, based on the original...

Hi Ioanna, No I don't have an idea. Normally this stage takes a few seconds, even less here since there is no exchange at all since you only use one process... Short of trying the simulation myself, I cannot help you, sorry. Maybe try with two processes? On Tue, Jun 25, 2019 at 9:47 AM Ioanna Did ioanna@users.sourceforge.net wrote: Dear Ides, In order to scale the UAV that I would like to run a simulation on, I used -meshscale in GMSH, as -scale did not seem to work. The simulation stops progressing...

Dear Ioanna, this is always a problem when the design and/or mesh is from a third party. The best is to design it yourself, that way you control the process. If this is not possible, then the designer should do his work according to your requirements. If this is not possible, then a back-and-forth is as inevitable as it is inefficient :( As to your question: sometimes it is easy to see what the mesh problems are, sometimes it is not. Some CAD software duplicate points, and so the surfaces are artificially...