how to pass more granular error message from run_discovery_script_file during runtime error?

[dhtdean]

Hi, I am wondering if there are ways to get more detailed runtime error messages other than "Script run failed."?

Context: I am using .run_discovery_script_file(script_file_path) in jupyter notebook to run the script automatically, and would like to pass the error message from status history bar in spaceclaim back. For example, I can see in the status history the error message is " Must contain a selection of any type" in the spaceclaim console. Any ways to pass this back to jupyter notebook?

Thanks

[RobPasMue]

Hi @dhtdean - thanks for opening this thread and using PyAnsys Geometry! In order to try and improve your user experience, could you share a minimal reproducible example of this event? I would need both the PyAnsys Geometry script and the SpaceClaim scripting. Also, can you let us know which PyAnsys Geometry version you are using? (you can find this by running: python -c "from ansys.geometry.core import __version__; print(__version__)")

[dhtdean]

Hi @RobPasMue, thanks for responding! The spaceclaim script was meant to be a failure run

pyansys - 0.10.2

Key scripts below:

from ansys.geometry.core import launch_modeler, Modeler

script_filepath = FILE_PATH # to define
GEOMETRY_INSTANCE = launch_modeler(mode = 'spaceclaim')

try:
    GEOMETRY_INSTANCE.run_discovery_script_file(script_filepath)
    print("Script executed successfully")
except Exception as e:
    print(f"Script execution failed with error: {str(e)}")

---

Return:
Script execution failed with error: Script run failed.

Desired return (the error message shown in the interpreter in spaceclaim)

Must Contain a Selection of any Type
Stack Trace:
Document:"geo_par_script_1step.py", Line:14

geo_par_script_1step.py
------------------------------------------------------------------------
cutter_origin = Point.Create(0.0, 0.029, 0.0)
cutter_direction = Direction.Create(0.0, -1.0, 0.0)
# Fire the ray with absolute and relative tolerances to select the interface face (index 1 selects a face)
cutter_result = RayFire.Fire(cutter_origin, cutter_direction, 1e-6, 1e-6)
cutter_face = Selection.Create(cutter_result[1])

# Select the merged body using a ray from the model center (index 0 returns the body)
body_origin = Point.Create(0.0, 0.0, 0.0)
body_direction = Direction.Create(0.0, 0.0, 1.0)
body_result = RayFire.Fire(body_origin, body_direction)
merged_body = Selection.Create(body_result[0])

# Execute the split using the identified cutter face; do not extend surfaces
SplitBody.ByCutter(merged_body, cutter_face, False)

[RobPasMue]

Thank you for your answer @dhtdean! I did some research on my side together with @b-matteo. You are right, whenever we run against SpaceClaim or Discovery, the error message shown in the application is not forwarded to PyAnsys Geometry and we should definitely fix this. We are working on it as we speak -- I thank you for your patience!

However, the main problem takes place on the service layer we talk to that gets shipped by SpaceClaim and Discovery. Meaning, that the fix is not related to PyAnsys Geometry directly. It is related to the underlying service inside SpaceClaim/Discovery that we connect to.

We will get this fix before the 25R2 release (early July) - and you would have to update your SpaceClaim/Discovery version once that's out. But up until then, I am sorry to say that there's little we can do.

[RobPasMue]

I opened #1891 to track this issue - thanks a lot @dhtdean