Unable to import Geometry into spaceclaim

[Leokek1]

Trying to import geometry to ansys, however whenever I run launch_modeler_with_spaceclaim I get the following error:
Code Inputted:

import os
import ansys.fluent.core as pyfluent
from ansys.geometry.core import Modeler
from ansys.geometry.core import launch_modeler_with_spaceclaim

# modeler = Modeler()

# Launch the modeler
modeler = launch_modeler_with_spaceclaim() #script doesn't get past this point

# Import geometry
design = modeler.open_file(
    os.path.join(
        os.getcwd(),
        f"003659.scdocx",
    )
)


# Retrieve the geometry
injector = design.bodies[0]

# Display the part
design.plot()'

Error Received:

'C:\Users\user.aad\OneDrive - Personal Project\General - PROJECT 21\Engineering\Analysis\Automated WindmillSimulations>C:/Users/user.aad/AppData/Local/Microsoft/WindowsApps/python3.11.exe "c:/Users/user.aad/OneDrive - Personal Project/General - PROJECT 21/Engineering/Analysis/Automated WindmillSimulations/named_selections.py"
CRITICAL -  -  logger - handle_exception - Uncaught exception
Traceback (most recent call last):
  File "c:\Users\user.aad\OneDrive - Personal Project\General - PROJECT 21\Engineering\Analysis\Automated WindmillSimulations\named_selections.py", line 9, in <module>
    modeler = launch_modeler_with_spaceclaim()
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\user.aad\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\ansys\geometry\core\misc\checks.py", line 403, in wrapper
    return method(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\user.aad\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\ansys\geometry\core\connection\launcher.py", line 855, in launch_modeler_with_spaceclaim
    return prepare_and_start_backend(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\user.aad\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\ansys\geometry\core\connection\product_instance.py", line 346, in prepare_and_start_backend
    return Modeler(
           ^^^^^^^^
  File "C:\Users\user.aad\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\ansys\geometry\core\modeler.py", line 106, in __init__
    self._grpc_client = GrpcClient(
                        ^^^^^^^^^^^
  File "<@beartype(ansys.geometry.core.connection.client.GrpcClient.__init__) at 0x16401c49ee0>", line 236, in __init__
  File "C:\Users\user.aad\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\ansys\geometry\core\connection\client.py", line 172, in __init__
    grpc_backend_response = self._admin_stub.GetBackend(Empty())
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\user.aad\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\grpc\_channel.py", line 1181, in __call__
    return _end_unary_response_blocking(state, call, False, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\user.aad\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\grpc\_channel.py", line 1006, in _end_unary_response_blocking
    raise _InactiveRpcError(state)  # pytype: disable=not-instantiable
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNIMPLEMENTED
        details = ""
        debug_error_string = "UNKNOWN:Error received from peer  {grpc_message:"", grpc_status:12, created_time:"2024-09-16T16:37:14.9870495+00:00"}"'

[RobPasMue]

Hi @Leokek1 - thanks for opening this issue. I have several questions for you:

• Can you share your python environment with us? (i.e. output from pip list)
• Which SpaceClaim version do you have installed?
• Has the script ever worked?
• Does SpaceClaim's GUI show up even though the error message appears?

[Leokek1]

I tried doing some debugging and I got SpaceClaim to import the file but now I am getting some new errors. This happens once the file is imported into SC. I do have an instance of Fluent running and a instance of WorkBench open:
Input Code:

import pkg_resources

# Enforce the recommended anays-geometry-core version to be compatible with ANSYS 2023R2
pkg_resources.require("ansys-geometry-core==0.3.2")

from ansys.geometry.core import launch_modeler_with_spaceclaim

modeler = launch_modeler_with_spaceclaim()

modeler.open_file(file_path=rf"[insert file path here'")

It then throws this following error:

[RobPasMue]

Hi @Leokek1

Based on your code I am assuming you are using Ansys 23R2 and ansys-geometry-core==0.3.2.

I am also guessing until here everything works fine:

import pkg_resources

# Enforce the recommended anays-geometry-core version to be compatible with ANSYS 2023R2
pkg_resources.require("ansys-geometry-core==0.3.2")

from ansys.geometry.core import launch_modeler_with_spaceclaim

modeler = launch_modeler_with_spaceclaim()

And then you are getting the error when running modeler.open_file(file_path=rf"[insert file path here}") - for your version 0.3.2 you can see the API docs here: https://geometry.docs.pyansys.com/version/0.3/api/ansys/geometry/core/modeler/Modeler.html#Modeler.open_file

I would recommend that you call the function with an additional argument: modeler.open_file(file_path=rf"[insert file path here}", upload_to_server=False). Since you are using SpaceClaim as your backend and it is running in your local machine you don't need to upload. I also recall some issues in the past with 23R2 and the upload functionality... give it a try and let me know! :)

[Leokek1]

Just gave that a try and it still returns the same exact error unfortunately!

Here is the image of the error for reference.

[RobPasMue]

That's sad to read... We dropped support early on the 23R2 version because we hit a lot of problems. The first stable release starts with 24R1.

You can see some older discussions we had here: #754 (reply in thread) - on 23R2 we did "the best we could" with SpaceClaim and Discovery but it surely wasn't optimal. Do you have access to the Ansys Geometry Service? (i.e. is there a folder on you machine with the following path? C:\Program Files\ANSYS Inc\v232\GeometryService)

If so, I'd suggest you use the function launch_modeler_with_geometry_service and gave it a try as well.

[Leokek1]

Hi! Sorry for not following up, however gave it a go and it also has that problem. I was thinking of waiting to upgrade to the new ANSYS 24R1, but once I do I will try it once more and hopefully it won't have this issue. I did almost find some work arounds though in case anyone reads this in the future and wants to follow the lead. Spaceclaim has scripting capabilities with both block and scripts. Script editing allows the opening, naming, and everything that is desired. However, block editing gets AUTO-turned on as soon as a part is opened. Since both of these options can't take place at the same time and block editing has precedence, it just turns off the script. This issue is basically what I ran into, if someone figures out how to turn off the auto block editing start please do let me know! I would love to find out.

[RobPasMue]

HI @b-matteo - do you know if it is possible to do what @Leokek1 is asking for inside SpaceClaim directly?

[b-matteo]

Hi @Leokek1, @RobPasMue thanks for reaching out.
I think you can get the script to work:

• Open your document into Ansys SpaceClaim
• In the Design tab, disable the Blocks function.
• Save your changes

from now on, you shouldn't get the Blocks editing turned on when you open the file.

Please let us know if that worked.

Thanks

[Leokek1]

Hi @b-matteo, so I gave that a whirl. However, part of my script is to import a part. So whenever I import the part block recording gets auto-enabled in the NEW spaceclaim instance. So once I do deactivate block recording, that instance does work -- however, once I import the part (the first line of my script) it proceeds to just not work since both are activated and block recording takes precedence. If I don't have the import statement, import in the part myself and run the rest of the script, it works beautifully. Its just the automatic enabling of the block recording which stops it by importing it via the spaceclaim script.