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

Using set_config_option on an operator's config does not actually change it server-side. #1917

Open
3 tasks done
PProfizi opened this issue Nov 22, 2024 · 0 comments
Open
3 tasks done
Labels
bug Something isn't working

Comments

@PProfizi
Copy link
Contributor

Before submitting the issue

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

Description of the bug

When using operator.config.set_config_option on an instance of an operator, the user would expect the config of the operator's instance to be modified in-place, which is not the case.

Steps To Reproduce

import ansys.dpf.core as dpf

op = dpf.operators.math.component_wise_divide_fc()
print(op.config.config_option_value("permissive"))

op.config.set_config_option(config_name="permissive", config_value=True)
print(op.config.config_option_value("permissive"))

new_config = op.default_config()
new_config.set_config_option(config_name="permissive", config_value=True)
print(new_config.config_option_value("permissive"))

op.config = new_config
print(op.config.config_option_value("permissive"))

Which Operating System causes the issue?

Windows, MacOS, Linux

Which DPF/Ansys version are you using?

DPF Server 2025.2.pre0

Which Python version causes the issue?

3.12

Installed packages

NA

@PProfizi PProfizi added the bug Something isn't working label Nov 22, 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