ansys / ansys/ansys-tools-common
[Path tool] Inconsistency issue
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- Avg merge
- 26m
- Merged PRs (30d)
- 27
Description
See related PyMechanical issue
For this user, get_mechanical_path(False) poins to v212
ansys.tools.path.get_mechanical_path(False)
'C:\Program Files\ANSYS Inc\v212\aisol\bin\winx64\AnsysWBU.exe'
But,
ansys.mechanical.core.find_mechanical()[0].
apparently points to a newer installation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing ansys.tools.path.get_mechanical_path(False) and ansys.mechanical.core.find_mechanical(), then read the related PyMechanical issue 371 for context. Reproduce the differing paths on a system with multiple installations and determine which installation each entry point should select; done means their behavior is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100