Skip to content
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

analyze_setup blocking argument does not work with parametrics #5872

Open
2 tasks done
DaveTwyman opened this issue Mar 6, 2025 · 1 comment
Open
2 tasks done

analyze_setup blocking argument does not work with parametrics #5872

DaveTwyman opened this issue Mar 6, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@DaveTwyman
Copy link
Contributor

DaveTwyman commented Mar 6, 2025

Before submitting the issue

  • I have searched among the existing issues
  • I am using a Python virtual environment

Description of the bug

The blocking=False argument was added to the analyze_setup method to allow PyAEDT to start solving one design or parametric and move into the next operation in the script, without having to wait for the previous setup to solve first.

This works if analyze_setup is given a 'Setup1' and blocking=False is used, however if the 'Setup1' is replaced with a 'ParametricSetup1' then it fails.

Steps To Reproduce

import os
from ansys.aedt.core import Maxwell3d

We have two Maxwell designs within the same project and wish to start the solve of both parametrics

at the same time

M3D = Maxwell3d(design="Maxwell3DDesign1",version="2025.1")

M3D.analyze_setup(name="Setup1") # Solves Design1/Setup1 'then' moves onto Design2/Setup1

M3D.analyze_setup(name="Setup1",blocking=False) # Starts solving Design1 'and' starts solving Design2 without waiting for first to solve.

M3D.analyze_setup(name="ParametricSetup1",blocking=False) # Blocking has no effect when applied to parametrics

M3D = Maxwell3d(design="Maxwell3DDesign2",version="2025.1")
M3D.analyze_setup(name="Setup1")

Which Operating System are you using?

Windows

Which Python version are you using?

3.9

Installed packages

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

(venv) PS C:\Users\detwyman\GithubRepos\PyAEDT3> python -m pip freeze
annotated-types==0.7.0
ansys-aedt-toolkits-common==0.6.3
ansys-magnet-segmentation-toolkit==0.5.1
ansys-pythonnet==3.1.0rc3
asttokens==2.4.1
attrs==24.2.0
backports.tarfile==1.2.0
blinker==1.8.2
build==1.2.2.post1
certifi==2024.8.30
cffi==1.17.1
cfgv==3.4.0
charset-normalizer==3.4.0
click==8.1.7
click-plugins==1.1.1
cligj==0.7.2
clr-loader==0.2.6
colorama==0.4.6
contourpy==1.3.0
coverage==7.6.4
cycler==0.12.1
decorator==5.1.1
defusedxml==0.7.1
distlib==0.3.9
docutils==0.21.2
et-xmlfile==1.1.0
exceptiongroup==1.2.2
execnet==2.1.1
executing==2.1.0
fast_simplification==0.1.7
filelock==3.16.1
fiona==1.10.1
Flask==3.0.3
fonttools==4.54.1
fpdf2==2.8.1
geopandas==0.14.4
identify==2.6.1
idna==3.10
imageio==2.36.0
importlib_metadata==8.5.0
importlib_resources==6.4.5
iniconfig==2.0.0
ipython==8.18.1
itsdangerous==2.2.0
jaraco.classes==3.4.0
jaraco.context==6.0.1
jaraco.functools==4.1.0
jedi==0.19.1
Jinja2==3.1.4
joblib==1.4.2
jsonschema==4.23.0
jsonschema-specifications==2024.10.1
keyring==25.4.1
kiwisolver==1.4.7
markdown-it-py==3.0.0
MarkupSafe==3.0.2
matplotlib==3.9.2
matplotlib-inline==0.1.7
mdurl==0.1.2
meshio==5.3.5
mock==5.1.0
more-itertools==10.5.0
networkx==3.2.1
nh3==0.2.18
nodeenv==1.9.1
numpy==1.26.4
openpyxl==3.1.5
osmnx==1.9.4
packaging==24.1
pandas==2.2.3
parso==0.8.4
pillow==11.0.0
pkginfo==1.10.0
platformdirs==4.3.6
pluggy==1.5.0
plumbum==1.9.0
pooch==1.8.2
pre_commit==4.0.1
prompt_toolkit==3.0.48
psutil==6.0.0
pure_eval==0.2.3
pyaedt @ file:///C:/Users/detwyman/GithubRepos/PyAEDT3
pycparser==2.22
pydantic==2.9.2
pydantic_core==2.23.4
pyedb==0.30.0
Pygments==2.18.0
pyparsing==3.2.0
pyproj==3.6.1
pyproject_hooks==1.2.0
PyQt5==5.15.11
PyQt5-Qt5==5.15.2
PyQt5_sip==12.15.0
PyQt6==6.7.1
PyQt6-Qt6==6.7.3
PyQt6_sip==13.8.0
pyqtgraph==0.13.7
PySide6==6.7.3
PySide6_Addons==6.7.3
PySide6_Essentials==6.7.3
pytest==8.3.3
pytest-cov==5.0.0
pytest-xdist==3.6.1
python-dateutil==2.9.0.post0
pytomlpp==1.0.13
pytz==2024.2
pyvista==0.44.1
pyvistaqt==0.11.1
pywin32==308
pywin32-ctypes==0.2.3
PyYAML==6.0.2
QDarkStyle==3.2.3
QtPy==2.4.1
readme_renderer==44.0
referencing==0.35.1
requests==2.32.3
requests-toolbelt==1.0.0
rfc3986==2.0.0
rich==13.9.2
rpds-py==0.20.0
rpyc==6.0.1
Rtree==1.3.0
scikit-learn==1.5.2
scikit-rf==1.3.0
scipy==1.13.1
scooby==0.10.0
shapely==2.0.6
shiboken6==6.7.3
six==1.16.0
SRTM.py==0.3.7
stack-data==0.6.3
threadpoolctl==3.5.0
toml==0.10.2
tomli==2.0.2
traitlets==5.14.3
twine==5.1.1
typing_extensions==4.12.2
tzdata==2024.2
urllib3==2.2.3
utm==0.7.0
virtualenv==20.26.6
vtk==9.3.1
wcwidth==0.2.13
Werkzeug==3.0.4
zipp==3.20.2
(venv) PS C:\Users\detwyman\GithubRepos\PyAEDT3>

@DaveTwyman DaveTwyman added the bug Something isn't working label Mar 6, 2025
@DaveTwyman DaveTwyman self-assigned this Mar 6, 2025
@DaveTwyman
Copy link
Contributor Author

TFS Bugs 1226423 and 1226442 raised against native script API, to summarize here:
In 2023.R2 parametrics only solve sequentially (And not in Parallel) when False Bool is used oModule.SolveSetup("ParametricSetup1",False)

From 2024.R1-2025.R2 parametrics solve in parallel but only two at a time
Only two Parametrics 1 and 4 solving in parallel (1,2,3,and 4 should have started right after each other)
1 finishes
2 starts and now we have 2 and 4 solving in parallel
4 finishes
2 solving
2 finishes
3 starts solving

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant