|
[Sponsors] |
March 13, 2024, 22:45 |
SpaceClaim Python Script Issue
|
#1 |
Member
Jin Seok Lee
Join Date: Aug 2021
Posts: 52
Rep Power: 5 |
I'm encountering several issues while using SpaceClaim Python scripts for fan optimization.
1. Spline Sub Point Movement Issue: When drawing a spline as shown in Figure 1, auxiliary points appear. Moving these points using the "move" function records the action in the Python script. However, when I move point 1 by 2mm and execute the script, the entire line moves instead of just the selected point. It seems like a naming issue where all points are identified similarly. How can I ensure that only the desired points move? 2. Problem with Tangent Constraint: To address the previous issue, I attempted a different approach. Figure 2 illustrates tangent constraints set for parameterizing wing angles. While manual operations correctly constrain the dashed line to the leading edge point, executing the Python script enforces the constraint on the trailing edge point (Figure 3). Why does this occur only when running the Python script, and how can I resolve it? 3. Sketch Difference and Parameter Interpretation: Unable to parameterize wing angles due to the previous issue, I resorted to a workaround. Instead of sketching curves, I imported curve data and set parameters by moving the points forming the curve. Although the Python script runs without errors, the workbench platform encounters errors during parameter interpretation, attributed to sketch setting changes. Why does this occur despite the script running smoothly? 4. Surface Naming Issue: After setting surface names in SpaceClaim, some names fail to synchronize during meshing. Renaming existing surfaces seems to trigger this issue. For example, I named three surfaces as "wall blade," "wall hub," and "wall shroud" (Figure 5), but synchronization errors persist. Why do these errors occur, unlike previous experiences where similar tasks were performed without issues? 5. Problem with Copying Solid Location: When copying a solid (Figure 6), its position changes unexpectedly upon executing the Python script in its entirety, whereas sequential script execution doesn't cause issues. How can I ensure consistent solid positioning throughout script execution? Thank you for your assistance. I appreciate any advice you can offer. |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Workbench] SpaceClaim Script Integration into WB Journal | mertal1905 | ANSYS Meshing & Geometry | 4 | May 11, 2020 18:18 |
Slicing extracted part of a volume in Python script | wilmbas | OpenFOAM Post-Processing | 4 | April 28, 2016 18:14 |
[General] How can I use python script to generate animation from 2000 frames of vtk datasets | LieyuShi | ParaView | 3 | March 10, 2016 14:37 |
[General] Transfer variables into python script from bash-shell | cfdFreshman | ParaView | 0 | December 3, 2015 04:33 |
[General] Python script: Auto-scale color scale | julien.decharentenay | ParaView | 2 | December 9, 2013 06:39 |