Jump to content

Search the Community

Showing results for tags 'scripting'.

The search index is currently processing. Current results may not be complete.


More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CAESESĀ®
    • General Modeling
    • Software Connections
    • Variation & Optimization
    • Post-Processing
    • Feature Programming
    • Installation
    • Miscellaneous
    • Ideas and Suggestions
    • FAQ

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Blogs

  • Mr. Arne Bergmann's Blog
  • FSYS DAEHWAN PARK
  • Mr. Arne Bergmann's Blog
  • Rel 3.1
  • Joerg Palluch's Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hello, I'm working on a project where Caeses is used to modify geometry parameters easily, but an external optimization script will generate new parameter inputs and Caeses will be used to generate the new geometry (e.g., new .stl files). To accomplish this, I have setup a case, exported a *.fsc script from it, modified a design variable in that script, and then executed it with "CAESES_crt.exe" to save the geometry as .stl files. Everything works perfectly and I am happy with this setup, but there is one thing I would like to improve upon. I would like to save the base filename for the modified .stl files generated after externally modifying the .fsc script. So for example, the scope from the project I am working in that I want to export has "mixerExported" as the base .stl file name (I am using "exportStlExtractColors" to extract a separate .stl file for each geometry partitioned into their respective colors), so the files generated are called "mixerExported_outletTopCyl.stl", etc. My question is: is it possible to change this base .stl file name in the .fsc script generated from the same project file? I do not need to generate separate project files, but rather I am looking to just modifying several design parameters and generate a new geometry for each of these modifications. Is it possible then to generate geometries from running the script and also changing the baseline filename they are saved from, just through modifying the .fsc file (and not the project file)? There are lines commented in the script file that specify a path, but it doesn't seem like they are being read: // CAESES Executable C:\Program Files (x86)\FRIENDSHIP-SYSTEMS\CAESES5\bin\win64\CAESES.exe // CAESES Project ~\CAESES\simple_test_geometry_export_demo\Simple_test_geometry_final_export.cdb // Design Name baseline // Project Units meters The outputs are saved in a folder created called "/manual_results/baseline/input". It would be great if there could be a way to generate a new folder called "/manual_results/mod1/input" etc. I'm not sure if this is something to be done just with the script, or if the project file does need to be modified, but I thought I would post it here for some advice or inputs from the experts. Thanks very much for your time! Best, Katherine
×
×
  • Create New...