ansys / pyfluent

Pythonic interface to Ansys Fluent
https://fluent.docs.pyansys.com
MIT License
276 stars 41 forks source link

Reading a casefile of the wrong dimensionality does not throw an error #2311

Open ansjsia opened 11 months ago

ansjsia commented 11 months ago

🔍 Before submitting the issue

🐞 Description of the bug

Reading a case file of the wrong dimensionality (e.g. 2D case into 3D Fluent or 3D case into 2D Fluent) throws an error in the TUI, but not in PyFluent. This could debugging tricky.

📝 Steps to reproduce

  1. Launch Fluent in 2D or 3D.
  2. Read in a case with the wrong dimensionality by calling root.file.read(), root.file.read_case, or by passing the case_file_name argument (in the PyFluent development build) to launch_fluent in Step 1.
  3. PyFluent will not throw an error, although the error can be seen in the TUI if show_gui=True.

💻 Which operating system are you using?

Windows

📀 Which ANSYS version are you using?

24R1 23R2

🐍 Which Python version are you using?

3.11

📦 Installed packages

accessible-pygments==0.0.4
alabaster==0.7.13
ansys-api-fluent==0.3.19
ansys-api-platform-instancemanagement==1.0.0
-e git+https://github.com/ansys/pyfluent.git@b0835a5e85185f158e875c928055a30dcf684c21#egg=ansys_fluent_core      
ansys-platform-instancemanagement==1.1.2
ansys-sphinx-theme==0.12.5
asttokens==2.4.1
attrs==23.1.0
autodocsumm==0.2.11
Babel==2.13.1
beartype==0.16.4
beautifulsoup4==4.12.2
bleach==6.1.0
build==1.0.3
certifi==2023.11.17
cfgv==3.4.0
charset-normalizer==3.3.2
colorama==0.4.6
comm==0.2.0
contourpy==1.2.0
coverage==7.3.2
cycler==0.12.1
debugpy==1.8.0
decorator==5.1.1
defusedxml==0.7.1
distlib==0.3.7
docker==7.0.0
docutils==0.20.1
executing==2.0.1
fastjsonschema==2.19.0
filelock==3.13.1
fonttools==4.46.0
grpcio==1.60.0
grpcio-health-checking==1.48.2
h5py==3.10.0
identify==2.5.33
idna==3.6
imagesize==1.4.1
importlib-metadata==7.0.0
iniconfig==2.0.0
ipykernel==6.27.1
ipython==8.18.1
ipywidgets==8.1.1
jedi==0.19.1
Jinja2==3.1.2
jsonschema==4.20.0
jsonschema-specifications==2023.11.2
jupyter-sphinx==0.4.0
jupyter_client==8.6.0
jupyter_core==5.5.0
jupyterlab-widgets==3.0.9
jupyterlab_pygments==0.3.0
kiwisolver==1.4.5
livereload==2.6.3
lxml==4.9.3
MarkupSafe==2.1.3
matplotlib==3.8.2
matplotlib-inline==0.1.6
mistune==3.0.2
nbclient==0.9.0
nbconvert==7.12.0
nbformat==5.9.2
nest-asyncio==1.5.8
nodeenv==1.8.0
numpy==1.26.2
numpydoc==1.6.0
packaging==23.2
pandas==2.1.4
pandocfilters==1.5.0
parso==0.8.3
Pillow==10.1.0
platformdirs==4.1.0
pluggy==1.3.0
pre-commit==3.6.0
prompt-toolkit==3.0.41
protobuf==3.20.3
psutil==5.9.6
pure-eval==0.2.2
pydata-sphinx-theme==0.14.4
Pygments==2.17.2
pypandoc==1.12
pyparsing==3.1.1
pyproject_hooks==1.0.0
pytest==7.4.3
pytest-cov==4.1.0
pytest-mock==3.12.0
pytest-sphinx==0.5.0
python-dateutil==2.8.2
pytz==2023.3.post1
pywin32==306
PyYAML==6.0.1
pyzmq==25.1.2
referencing==0.32.0
requests==2.31.0
rpds-py==0.13.2
setuptools==69.0.2
six==1.16.0
snowballstemmer==2.2.0
soupsieve==2.5
Sphinx==7.2.6
sphinx-autobuild==2021.3.14
sphinx-autodoc-typehints==1.25.2
sphinx-copybutton==0.5.2
sphinx-gallery==0.15.0
sphinx-notfound-page==1.0.0
sphinxcontrib-applehelp==1.0.7
sphinxcontrib-devhelp==1.0.5
sphinxcontrib-htmlhelp==2.0.4
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-qthelp==1.0.6
sphinxcontrib-serializinghtml==1.1.9
sphinxcontrib-websupport==1.2.6
sphinxemoji==0.2.0
stack-data==0.6.3
tabulate==0.9.0
tinycss2==1.2.1
tornado==6.4
traitlets==5.14.0
typing_extensions==4.9.0
tzdata==2023.3
urllib3==2.1.0
virtualenv==20.25.0
wcwidth==0.2.12
webencodings==0.5.1
wheel==0.42.0
widgetsnbextension==4.0.9
zipp==3.17.0
prmukherj commented 9 months ago

This is mostly a fluent side bug.

Initial triaging report:

  1. Launching in 2d and trying to read a 3d case, propagates the error message correctly.
  2. Issue occurs while reading a 2d case from 3d session. Then the error is not properly propagated.
mkundu1 commented 6 months ago

I see that error is not propagated to PyFluent in either cases. Only the error message in the transcript can be seen from PyFluent.

mkundu1 commented 6 months ago

Same behaviour in PyConsole - this should be first fixed there.

Fluent bug id - 1035244