pyfluent: Issue with session.solution.report_definitions.volume gives unexpected error

🔍 Before submitting the issue

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

🐞 Description of the bug

When assigning volume reports to session.solution.report_definitions.volume it gives an unexpected error

From fluent GUI i get this error in console: Error: eval: unbound variable Error Object: allowed-values

I dont have this issue when assigning to session.solution.report_definitions.surface

I tried

`session.solution.report_definitions.volume.create(‘max-afe-chip-temp’) session.solution.report_definitions.volume.create(‘max-inv-chip-temp’) session.solution.report_definitions.volume.create(‘max-temp-heatsink-afe’) session.solution.report_definitions.volume.create(‘max-temp-heatsink-inv’)

session.solution.report_definitions[‘max-afe-chip-temp’] = settings[‘reportsVolume’][‘max-afe-chip-temp’] session.solution.report_definitions[‘max-inv-chip-temp’] = settings[‘reportsVolume’][‘max-inv-chip-temp’] session.solution.report_definitions[‘max-temp-heatsink-afe’] = settings[‘reportsVolume’][‘max-temp-heatsink-afe’] session.solution.report_definitions[‘max-temp-heatsink-inv’] = settings[‘reportsVolume’][‘max-temp-heatsink-inv’] ` I get an error for each of the fire last lines, but every time I run the next line the previous line in fluent GUI changes away from invalid. I also tried using method .set_state() but again same error

📝 Steps to reproduce

session.solution.report_definitions.volume.create(‘max-afe-chip-temp’) session.solution.report_definitions[‘max-afe-chip-temp’].set_state({‘report_type’: ‘volume-max’, ‘field’: ‘temperature’, ‘average_over’: 1, ‘per_zone’: False, ‘zone_names’: [‘dcb-1.1’, ‘dcb-1.2’, ‘dcb-1.3’], ‘expr_list’: None})

💻 Which operating system are you using?

Windows

🐍 Which Python version are you using?

3.9

📦 Installed packages

ansys-api-fluent==0.3.8
ansys-api-platform-instancemanagement==1.0.0b3
-e git+https://github.com/pyansys/pyfluent.git@472b0c088a0e5040ba23138e87c2cb5184db86c3#egg=ansys_fluent_core
ansys-platform-instancemanagement==1.0.3
appdirs==1.4.4
asttokens==2.2.1
backcall==0.2.0
cloudpickle==2.2.1
colorama==0.4.6
comm==0.1.2
debugpy==1.6.6
decorator==5.1.1
entrypoints==0.4
executing==1.2.0
googleapis-common-protos==1.58.0
grpcio==1.51.1
h5py==3.8.0
importlib-metadata==6.0.0
ipykernel==6.21.0
ipython==8.9.0
jedi==0.18.2
jupyter_client==7.4.9
jupyter_core==5.2.0
matplotlib-inline==0.1.6
nest-asyncio==1.5.6
numpy==1.24.1
packaging==23.0
pandas==1.5.3
parso==0.8.3
pickleshare==0.7.5
platformdirs==2.6.2
prompt-toolkit==3.0.36
protobuf==3.20.3
protoc-gen-swagger==0.1.0
psutil==5.9.4
pure-eval==0.2.2
Pygments==2.14.0
python-dateutil==2.8.2
pytz==2022.7.1
pywin32==305
pyzmq==25.0.0
six==1.16.0
spyder-kernels==2.4.2
stack-data==0.6.2
tornado==6.2
traitlets==5.9.0
wcwidth==0.2.6
zipp==3.12.0

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 16

Commits related to this issue

Most upvoted comments

@jharming, it’s still broken in 2023R2 so we’ll work for a fix. I will try to provide you a fix.

Then I have something to look forward to