{"id":160509,"date":"2021-07-20T09:05:12","date_gmt":"2021-07-20T09:05:12","guid":{"rendered":"\/forum\/forums\/topic\/how-to-execute-spaceclaim-script-within-act\/"},"modified":"2022-05-31T19:31:25","modified_gmt":"2022-05-31T19:31:25","slug":"how-to-execute-spaceclaim-script-within-act","status":"closed","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/how-to-execute-spaceclaim-script-within-act\/","title":{"rendered":"How to execute SpaceClaim script within ACT?"},"content":{"rendered":"
\n
\n

Hello everyone<\/p>\n

I'm having difficulties implementing my previously developed SpaceClaim script, into an ACT scripting environment. I want to roll out this script solution out to my colleagues, as this design\/analysis is quite repetitive and I thought an ACT (APP) would be quite suitable for the task.<\/p>\n

The SpaceClaim script works perfectly within the SpaceClaim scripting environment. I've modified the IronPython SpaceClaim script slightly to work better with ACT by:<\/p>\n

    \n
  1. Splitting it into two .py files, the script <\/strong>and the definition (def) <\/strong>I've defined<\/li>\n
  2. Modified the input geometry variables to extract the values from the user (see example below)<\/li>\n<\/ol>\n

    br_h.Add(step.Properties["Geometry\/br_h_top"].Value) <\/code><\/p>\n

    br_h.Add(step.Properties["Geometry\/br_h_bot"].Value) <\/code>      <\/p>\n

     AC_geo.Add('br_h',br_h)<\/code><\/p>\n

    <\/p>\n<\/p>\n

    So far I've achieved the following in ACT:<\/p>\n

      \n
    1. Defining the steps<\/li>\n
    2. Setting up the workbench interface (separate load cases)<\/li>\n
    3. Opening SpaceClaim <\/li>\n
    4. Defining the geometry input<\/li>\n
    5. Extracting the geometrical values from 4., to be used further in the IronPython code.<\/li>\n<\/ol>\n

      After that the ACT program crashes on a line where I define: <\/p>\n

       variable = Direction.Create(1,0,0)<\/code><\/p>\n

      or:<\/p>\n

      variable = List[IComponent]()<\/code><\/p>\n

      My conclusion is therefore that: ACT does not recognize the internal SpaceClaim IronPython functions as default.<\/em><\/p>\n

      I've tried to define the following default definition <\/strong>that "imports" the default SpaceClaim IronPython definitions. ACT can call and run the definition <\/strong>, but it doesn't work…..<\/p>\n

      def script_import():<\/code><\/p>\n

        '''<\/code><\/p>\n

        This function imports SpaceClaim scripting for ACT<\/code><\/p>\n

        '''<\/code><\/p>\n

        import clr<\/code><\/p>\n

        clr.AddReference("Ansys.ACT.Interfaces")<\/code><\/p>\n

        import Ansys<\/code><\/p>\n

        clr.AddReference("SpaceClaim.Api.V19")<\/code><\/p>\n

        import SpaceClaim<\/code><\/p>\n

        clr.AddReference('SpaceClaim.Api.V19.Scripting')<\/code><\/p>\n

        from SpaceClaim.Api.V19 import Geometry<\/code><\/p>\n

        from SpaceClaim.Api.V19 import Modeler<\/code><\/p>\n

        return<\/code><\/p>\n

      I've searched for days for some kind of solution online and in the ANSYS guides, but I cannot find my way around this problem. Do any of you have any suggestions?<\/p>\n

      <\/p>\n<\/p>\n

      Note<\/strong>: I cannot share the source code as it owned by the company I work for, but I can share some of if it would help<\/p>\n","protected":false},"template":"","class_list":["post-160509","topic","type-topic","status-closed","hentry","topic-tag-act","topic-tag-application-1","topic-tag-scripting","topic-tag-spaceclaim","topic-tag-workbench"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t