![]() ![]() ![]() This function imports SpaceClaim scripting for ACTĬlr.AddReference('') In this chapter, ANSYS DesignModeler is selected. ACT can call and run the definition, but it doesn't work. ANSYS provides two tools for geometry development: ANSYS Discovery SpaceClaim and ANSYS DesignModeler. dimensions display on the drawing sheet (if you are dimensioning a model in a drawing sheet). all dimensions are placed on an annotation plane in design mode, which you can toggle on or off for display purposes. I've tried to define the following default definition that "imports" the default SpaceClaim IronPython definitions. to create dimensions for annotating a part, use the dimension tool in the annotation group on the detailing tab. My conclusion is therefore that: ACT does not recognize the internal SpaceClaim IronPython functions as default. Extracting the geometrical values from 4., to be used further in the IronPython code.Īfter that the ACT program crashes on a line where I define:.Setting up the workbench interface (separate load cases).So far I've achieved the following in ACT: Modified the input geometry variables to extract the values from the user (see example below)īr_h.Add().py files, the script and the definition (def) I've defined I've modified the IronPython SpaceClaim script slightly to work better with ACT by: The SpaceClaim script works perfectly within the SpaceClaim 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. I'm having difficulties implementing my previously developed SpaceClaim script, into an ACT scripting environment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |