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

Bug located in ...HFSS (AEDT) analyze() with acf_file parameter #5187

Open
2 tasks done
SteffenSee92 opened this issue Sep 20, 2024 · 0 comments
Open
2 tasks done

Bug located in ...HFSS (AEDT) analyze() with acf_file parameter #5187

SteffenSee92 opened this issue Sep 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@SteffenSee92
Copy link

Before submitting the issue

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

Description of the bug

Hello,

I used the analyze() method at first without the acf_file parameter, but with settings for my server or localhost (cores, RAM, gpu...). This generates me an acf_file in the .pyaedt directory created for my project.
In a second step I want to use now an acf file for the analysis configuration and tested exactly with the same file that was created by analyze method. The file seems to be identified (path is correct) and it also changes the settings like number of cores. which i checked in the GUI. But the analysis of my setup does not work, I get the following error message, which looks like a bug in the acf reading here with the analysis method:

"Invalid setup "test_config"." There is no error in the Jupyter lab given, but the message is given in the GUI.

Best regards

Steps To Reproduce

  • Open an HFSS project with valid analysis setup
  • Analyze with analyze() method (not the analyze_setup method), like this: hfss.analyze(setup="ATK_Solution", cores=4, gpus=0, machine="localhost") -> this solves the existing setup
  • Clean up solutions in the GUI to be able to solve again
  • Replace the hfss.analyze method above by one including the acp_file parameter, like this: hfss.analyze(setup="ATK_Solution", acf_file=acf). Here, acf is the full path to the acf file "pyaedt_config.acf", e.g. the original one that was created with the first analyze, or a modified version
  • The error message "Invalid setup "pyaedt_config" will appear in the GUI, the setup will not be analyzed again
  • But when checking the analysis configurations, there is an effect, which means, the acf file was read. I checked this by doing a modification to the pyaedt_config.acf, like changing the number of cores from 4 to 2

Which Operating System are you using?

Windows

Which Python version are you using?

3.10

Installed packages

(Env24R2) C:\Users\sseewald>python -m pip freeze
annotated-types==0.7.0
ansys-pythonnet==3.1.0rc3
anyio==4.4.0
argon2-cffi==23.1.0
argon2-cffi-bindings==21.2.0
arrow==1.3.0
asttokens==2.4.1
async-lru==2.0.4
attrs==24.2.0
babel==2.16.0
beautifulsoup4==4.12.3
bleach==6.1.0
certifi==2024.8.30
cffi==1.17.1
charset-normalizer==3.3.2
clr-loader==0.2.6
colorama==0.4.6
comm==0.2.2
debugpy==1.8.5
decorator==5.1.1
defusedxml==0.7.1
exceptiongroup==1.2.2
executing==2.1.0
fastjsonschema==2.20.0
fonttools==4.53.1
fpdf2==2.7.9
fqdn==1.5.1
h11==0.14.0
httpcore==1.0.5
httpx==0.27.2
idna==3.10
ipykernel==6.29.5
ipython==8.27.0
isoduration==20.11.0
jedi==0.19.1
Jinja2==3.1.4
json5==0.9.25
jsonpointer==3.0.0
jsonschema==4.23.0
jsonschema-specifications==2023.12.1
jupyter-events==0.10.0
jupyter-lsp==2.2.5
jupyter_client==8.6.3
jupyter_core==5.7.2
jupyter_server==2.14.2
jupyter_server_terminals==0.5.3
jupyterlab==4.2.5
jupyterlab_pygments==0.3.0
jupyterlab_server==2.27.3
MarkupSafe==2.1.5
matplotlib-inline==0.1.7
mistune==3.0.2
nbclient==0.10.0
nbconvert==7.16.4
nbformat==5.10.4
nest-asyncio==1.6.0
notebook_shim==0.2.4
numpy==1.26.4
overrides==7.7.0
packaging==24.1
pandas==2.2.2
pandocfilters==1.5.1
parso==0.8.4
pillow==10.4.0
platformdirs==4.3.3
plumbum==1.8.3
prometheus_client==0.20.0
prompt_toolkit==3.0.47
psutil==6.0.0
pure_eval==0.2.3
pyaedt==0.10.2
pycparser==2.22
pydantic==2.9.1
pydantic_core==2.23.3
pyedb==0.28.0
Pygments==2.18.0
python-dateutil==2.9.0.post0
python-json-logger==2.0.7
pytomlpp==1.0.13
pytz==2024.2
pywin32==306
pywinpty==2.0.13
PyYAML==6.0.2
pyzmq==26.2.0
referencing==0.35.1
requests==2.32.3
rfc3339-validator==0.1.4
rfc3986-validator==0.1.1
rpds-py==0.20.0
rpyc==6.0.0
Rtree==1.3.0
scikit-rf==1.3.0
scipy==1.14.1
Send2Trash==1.8.3
six==1.16.0
sniffio==1.3.1
soupsieve==2.6
stack-data==0.6.3
terminado==0.18.1
tinycss2==1.3.0
toml==0.10.2
tomli==2.0.1
tornado==6.4.1
traitlets==5.14.3
types-python-dateutil==2.9.0.20240906
typing_extensions==4.12.2
tzdata==2024.1
uri-template==1.3.0
urllib3==2.2.3
wcwidth==0.2.13
webcolors==24.8.0
webencodings==0.5.1
websocket-client==1.8.0

@SteffenSee92 SteffenSee92 added the bug Something isn't working label Sep 20, 2024
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