How to generate reports for HFSS Antenna Parameters? #4949
-
I'm attempting to use PyAEDT verstion 0.9 to generate a report for the radiation efficiency of an antenna. It works great when done through the AEDT GUI, but I can't get a trace to show up when doing it through AEDT. I'm using this command:
I get a rectangular plot labeled "RadiationEfficiency", but there is no trace. I've tried multiple variations of the command based on this discussion: "#4927" , but none of them seem to work for the antenna parameters category. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
Hi @wsp6 , This code should work:
As you can see you can plot or get the data. "data" is an object that you can use to plot the trace in matplotlib or use for your own workflow. Please close the issue if this helps you. |
Beta Was this translation helpful? Give feedback.
-
I am just wondering, if there is a need to "SaveFileds" even in the Parametrics setup. |
Beta Was this translation helpful? Give feedback.
-
Edit: forgot to include the line of code where I set that option. Here is how I'm setting the "SaveFields" option for the Parametrics setup. This line goes immediately after I import the parametrics setup from the CSV file.
hfss.set_oo_property_value(aedt_object=hfss.ooptimetrics, object_name="Parametrics_Setup_"), prop_name='SaveFields', value='True')
With this setting I can generate far field plots successfully. The following actions work
when I specify a particular variation from the parameters: create a polar
far field dB(gain) plot, export polar plot to jpg, create far field
dB(gain) table, and export far field gain table as csv.
Get_solution_data also partially works for dB(gain). I found an issue where
I can't get the information out of the exported object. The
solution_data.data_real() method of the object only outputs a one
dimensional vector instead of a two dimensional matrix. A separate issue
has already been created for this problem.
…On Sun, Aug 4, 2024, 7:53 AM Vamsi-Yaddanapudi ***@***.***> wrote:
I am just wondering, if there is a need to "SaveFileds" even in the
Parametrics setup.
—
Reply to this email directly, view it on GitHub
<#4949 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BCETRGE4OMIJKMAB5XT3I7DZPYIZTAVCNFSM6AAAAABLNE6OY2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRTGQ4TCMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Yes. The antenna parameters values, specifically Radiation Efficiency, are better values for my application than the far field gain.
I'm currently exporting a far field gain data table to CSV, reading it back in, and then finding the max value. That other thread addresses a bug in the solution_data.data_real() function (which is why I have to write then immediately read a CSV).
That works, but the radiation efficiency would work better.
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Vamsi-Yaddanapudi ***@***.***>
Sent: Monday, August 5, 2024 12:44:27 AM
To: ansys/pyaedt ***@***.***>
Cc: Perkins, Bill ***@***.***>; Mention ***@***.***>
Subject: Re: [ansys/pyaedt] How to generate reports for HFSS Antenna Parameters? (Discussion #4949)
Ok, I see you have another thread open. Do you still need some help for this thread?
—
Reply to this email directly, view it on GitHub<#4949 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCETRGEPIVIQUWTGWSIEESLZP37KXAVCNFSM6AAAAABLNE6OY2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRTHA4TMNQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hi @wsp6 , I have just launched your script, I think all the data is there. The problem is that by default PyAEDT creates the report with the Nominal variation, which in this case is not solved, you have solved only the parametric sweep.
|
Beta Was this translation helpful? Give feedback.
Hi @wsp6 ,
This code should work: