-
Notifications
You must be signed in to change notification settings - Fork 129
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into release/0.4
- Loading branch information
Showing
42 changed files
with
1,109 additions
and
889 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,22 +23,24 @@ PyAEDT includes functionality for interacting with the following AEDT tools and | |
What is PyAEDT? | ||
--------------- | ||
PyAEDT is a Python library that interacts directly with the AEDT API | ||
to make scripting simpler for the end user. It uses an architecture | ||
that can be reused for all AEDT 3D products (HFSS, Icepak, Maxwell 3D, | ||
Q3D and Mechanical) as well as 2D tools. It also provides support for circuit tools like | ||
to make scripting simpler for the end user. Its architecture | ||
can be reused for all AEDT 3D products (HFSS, Icepak, Maxwell 3D, and | ||
Q3D), 2D tools, and Ansys Mechanical. It also provides support for circuit tools like | ||
Nexxim and system simulation tools like Twin Builder. Finally it provides scripting | ||
capabilities in Ansys layout tools like HFSS 3D Layout and EDB. Its class and method structures | ||
simplify operation for the end user while reusing information as much as | ||
capabilities in Ansys layout tools like HFSS 3D Layout and EDB. Its class and method | ||
structures simplify operation for the end user while reusing information as much as | ||
possible across the API. | ||
|
||
Documentation and Issues | ||
------------------------ | ||
See the `API Documentation <https://aedtdocs.pyansys.com/API/>`_ and explore | ||
the `Examples <https://aedtdocs.pyansys.com/examples/index.html>`_. | ||
|
||
To post issues, questions, and code, go to `PyAEDT Issues | ||
<https://github.com/pyansys/PyAEDT/issues>`_. | ||
In addition to installation, usage, and contribution information, the PyAEDT | ||
documentation provides `API documentation <https://aedtdocs.pyansys.com/API/>`_, | ||
`examples <https://aedtdocs.pyansys.com/examples/index.html>`_, and `code guidelines | ||
<https://aedtdocs.pyansys.com/Resources/Code_Guidelines.html>`_. | ||
|
||
On the `PyAEDT Issues <https://github.com/pyansys/PyAEDT/issues>`_ page, you can | ||
create issues to submit questions, report bugs, and request new features. To reach | ||
the project support team, email `[email protected] <[email protected]>`_. | ||
|
||
Dependencies | ||
------------ | ||
|
@@ -48,10 +50,9 @@ PyAEDT supports AEDT versions 2021 R1 or newer. | |
Student Version | ||
--------------- | ||
|
||
PyAEDT now supports also AEDT Student version 2021 R2. Visit | ||
PyAEDT supports AEDT Student version 2021 R2. For more information, see | ||
`Student Version page <https://www.ansys.com/academic/students/ansys-e | ||
lectronics-desktop-student>`_ | ||
for more info. | ||
lectronics-desktop-student>`_. | ||
|
||
|
||
Why PyAEDT? | ||
|
@@ -81,23 +82,23 @@ The main advantages of PyAEDT are: | |
|
||
Example Workflow | ||
----------------- | ||
1. Initialize the `Desktop` class with the version of AEDT to use. | ||
1. Initialize the ``Desktop`` class with the version of AEDT to use. | ||
2. Initialize the application to use within AEDT. | ||
|
||
|
||
Connect to Desktop from Python IDE | ||
---------------------------------- | ||
PyAEDT works both inside AEDT and as a standalone application. | ||
It automatically detects whether it is running in an IronPython or CPython | ||
environment and initializes the Desktop accordingly. PyAEDT also provides | ||
advanced error management. Usage examples follow. | ||
environment and initializes AEDT accordingly. PyAEDT also | ||
provides advanced error management. Usage examples follow. | ||
|
||
Explicit Desktop Declaration and Error Management | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
.. code:: python | ||
# Launch AEDT 2021 R1 in Non-Graphical mode | ||
Launch AEDT 2021 R1 in non-graphical mode | ||
from pyaedt import Desktop, Circuit | ||
with Desktop(specified_version="2021.1", | ||
|
@@ -130,18 +131,20 @@ Implicit Desktop Declaration and Error Management | |
Remote Application Call | ||
~~~~~~~~~~~~~~~~~~~~~~~ | ||
You can make a remote application call on a CPython server | ||
or any Windows client machine. | ||
|
||
On a CPython Server | ||
On a CPython Server: | ||
|
||
.. code:: python | ||
Launch Pyaedt remote server on CPython | ||
Launch PyAEDT remote server on CPython | ||
from pyaedt.common_rpc import launch_server | ||
launch_server() | ||
On any Windows client machine | ||
On any Windows client machine: | ||
|
||
.. code:: python | ||
|
@@ -177,8 +180,8 @@ License | |
------- | ||
PyAEDT is licensed under the MIT license. | ||
|
||
This PyAEDT module makes no commercial claim over Ansys | ||
whatsoever. PyAEDT extends the functionality of AEDT by adding | ||
This module makes no commercial claim over Ansys whatsoever. | ||
PyAEDT extends the functionality of AEDT by adding | ||
an additional Python interface to AEDT without changing the core | ||
behavior or license of the original software. The use of the | ||
interactive control of PyAEDT requires a legally licensed | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.