Open greschd opened 1 month ago
Hi @greschd - thanks for opening the issue. Seems like a backend problem IMO. Pinging @b-matteo @umutsoysalansys @smereu for evaluation
ImportOptions object might be expected in this scenario but the main issue is the difference in behavior when it gets imported.
🔍 Before submitting the issue
🐞 Description of the bug
When importing the attached
.step
file, the imported curves are incomplete unless theimport_points
option is also set toTrue
. ply_boundaries.step.txtScreenshot with![image](https://github.com/user-attachments/assets/7f518077-63fb-4f58-be53-ba3e515910cf)
import_points=False
[1]Screenshot with![image](https://github.com/user-attachments/assets/667bbeac-bbbb-411c-aa1d-73ec3e15007b)
import_points=True
Reproducing code:
The curves are defined as
B_SPLINE_CURVE_WITH_KNOTS
. These do referenceCARTESIAN_POINT
objects in their definition, but I don't understand why the curve import works in some cases, but not in others. Presumably, the curve import should read the points which make up the curve definition, but not import them as separate point objects. And indeed, in neither case are the points separately present in the imported geometry.[1] I am using
launch_modeler_with_discovery
for being able to make screenshots, but the issue originally occurred usinglaunch_modeler_with_geometry_service
.📝 Steps to reproduce
.txt
extension💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2025R1
🐍 Which Python version are you using?
3.10
📦 Installed packages