-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Field Calculator GetTopEntryValue(feildcalculator output result) #5678
Comments
Hi @Samuelopez-ansys , thanks for your reply. I’ve just tried it and have several observations. While calculating the H-field at a point using the expression "t" = PointValue(Point(MyPoint), Real(<Hx,Hy,Hz>)) I only get the value for the z-direction, not for all directions. See below:
when I wrote it to a file:
then, the output contains all directions.
If I ran it directly in the HFSS calculator manually, the output would be::
Did I miss something? How can I get the full top entry value? Ideally, I’d like to store it in a variable as a vector. Another observation: The methods listed in the link you shared are probably not up to date. therefore, I got an error during the first try.
Many thanks! |
one more remark: I tried to read the H value at a point, and when adding a new expression, I had to set the assignment to 'None'. Is it correct? It doesn't accept points. See below:
Is there a way to keep the assignment in an expression as a variable, so that one doesn't have to create a new one and delete the old one for every new point/object? My approach might be completely wrong... Thanks! |
Description of the feature
Hi,
I wish to be able to drive the Field Calculator with direct commands and read the top entry at the end. Now I have to create in API new expression, save it, than read it using PyAEDT and than create a plot to read the values from it. Not really straigh forward. Or am I doing something wrong?
Thanks!
Maslo
Steps for implementing the feature
No response
Useful links and references
No response
The text was updated successfully, but these errors were encountered: