ansys / ansys/pysystem-coupling
Check for Fluent participant version and block execution if Fluent is newer than System Coupling
- Dominant language
- Python
- Stars
- 12
- Forks
- 6
- Avg merge
- 1d 18m
- Merged PRs (30d)
- 6
Description
### 🔍 Before submitting the issue
- [X] I have searched among the existing issues
- [X] I am using a Python virtual environment
### 🐞 Description of the bug
If I launch a Fluent instance using PyFluent and then pass that instance to PySystemCoupling via `add_participant` command, PySystemCoupling should compare the versions and if Fluent is from a newer release than System Coupling, an error should be thrown with a descriptive error message. Otherwise, the run will fail during the solve and potentially unclear error messages.
### 📝 Steps to reproduce
Start newer Fluent version:
`fluent = pyfluent.launch_fluent(product_version = "24.2")`
(set up Fluent case)
Start older System Coupling version:
`syc = pysyc.launch_fluent(version = "24.1")`
Add Fluent participant:
`syc.add_participant(participant_session = fluent)`
This should result in an error with a clear message.
### 💻 Which operating system are you using?
Windows
### 📀 Which ANSYS version are you using?
24.1 and 24.2
### 🐍 Which Python version are you using?
3.9
### 📦 Installed packages
```shell
n/a
```
Contributor guide
Research direction
Start at the PySystemCoupling add_participant entry point and inspect how the participant session and release versions are exposed. Reproduce the 24.2 Fluent with 24.1 System Coupling scenario, then verify that a descriptive error is raised before the solve begins when Fluent is newer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100