Edit Sources in Hfss

[georgmichel]

Hi,

there was a related question in #5743. I want to export the far field of a multi-port setup in Hfss.

When I invoke Hfss.get_antenna_data().farfield_data , the exported field is always the same, no matter what excitation is set (either in Desktop or via PyAEDT). Am I missing something?

Another problem:

Hfss.get_antenna_data(link_to_hfss=False).farfield_data

gives the same result as

Hfss.get_antenna_data(link_to_hfss=True).farfield_data.farfield_data

Is this intentional? Thanks for your answer.

[georgmichel]

I tried some other way and I can crash AEDT with

app = ansys.aedt.core.Hfss(project=my_project, design=my_design)
data = app.post.get_solution_data(expressions = "dB(GainTotal)", primary_sweep_variable="Theta",
report_category = "Far Fields", context = "3D")

[Samuelopez-ansys]

Hi @georgmichel ,

Right, this is an AEDT bug that I will report. The problem is that by default PyAEDT tries the first sweep, but probably in your case, your 1st sweep does not contain any solved field, and then AEDT crashes.

Please pass the Setup you want to get:

data = app.post.get_solution_data(expressions="dB(GainTotal)", primary_sweep_variable="Theta",
                                  report_category="Far Fields", context="3D", setup_sweep_name="Setup1 : LastAdaptive")

[Samuelopez-ansys]

Hi @georgmichel ,

About your 1st question. When you get Hfss.get_antenna_data().farfield_data, you are obtaining an object of the class FfdSolutionData, it is explained here:

https://aedt.docs.pyansys.com/version/stable/API/visualization/advanced.html#farfield

So, once you have this data, you are independent of AEDT. It means, you can change the port magnitude and phase in pure python, so you do not need anymore Edit Source of HFSS, because the superposition of the FFD files of each port/antenna is performed inside the class.

THis is also used here:

https://examples.aedt.docs.pyansys.com/version/dev/examples/high_frequency/antenna/array.html

The difference between (link_to_hfss=True) or False, is that if you pass True, the return object will be the FfdSolutionData, if you pass False, the method will return the metadata file (json file), that you can use later in another script, calling directly the FfdSolutionData.

As I said, I think is quite well explained:

https://aedt.docs.pyansys.com/version/stable/API/visualization/advanced.html#farfield

[georgmichel]

Thanks Samuel,

I was not aware of the magnitude and phase properties of FfdSolutionData. I fiddled around a lot with ansys.aedt.core.Hfss.edit_sources and I wondered why it has no effect on the far field.