ansys / ansys/pyworkbench-examples
Workbench commands take long time on customer environment
- Dominant language
- No language data
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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
### 📝 Steps to reproduce
1. `wb = launch_workbench()`
2. `geometry1 = system1.GetContainer(ComponentName="Geometry")`
`geometry1.SetFile(FilePath=geometry_path)`
`modelComponent1 = system1.GetComponent(Name="Model")`
`modelComponent1.Refresh()`
### 💻 Environment difference
Internal environment = IPv6
Customer environment = IPv4
- Does that make any difference?
### 💻 Which operating system are you using?
Windows
### 📀 Which ANSYS version are you using?
_No response_
### 🐍 Which Python version are you using?
3.9
### 📦 Installed packages
```shell
ansys-workbench-core 0.14.0
```
Contributor guide
Research direction
Start by reproducing the listed launch_workbench, SetFile, and Refresh sequence on Windows with Python 3.9 and ansys-workbench-core 0.14.0. Compare timings between IPv4 and IPv6 environments and use the issue's image and six-comment thread for additional context; done means identifying and documenting the cause of the customer-environment delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100