Jump to content

Search the Community

Showing results for tags 'external'.

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

Categories

  • New Features
  • Other

Blogs

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

Calendars

  • Community Calendar

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. Hi together, The pro edition of CAESES comes with a set of algorithms for design exploration and formal optimizations. However, people often already use an external optimization software in their company (such as HEEDS, Isight, modeFrontier, Optimus, optiSLang etc). In this case, one can make use of the batch mode of the CAESES pro edition, in order to automatically generate geometry design variants, using the given optimization tool. I attached a small setup (sweepbatch.zip) which demonstrates how simple this works: sweep.fdb Project file that contains the geometry model along with its design variables.sweep.fsc ASCII file that controls the batch run. It starts CAESES, sets the values of the design variables and exports an STL file. This fsc-file is the one that needs to be manipulated by the external optimization software, i.e. parameterize the values of the design variables (see the "setValue"-command).run.bat Run this file to execute the entire process. The run of sweep.fdb also writes out the number of open edges into a file called "openedges.dat". It is merely a simple check for a closed STL geometry, and this information can be used as well by the optimization tool (geometry validity check). Cheers Joerg PS: check out this related post as well. UPDATE AUGUST 2017: The call in the bat/script file needs to be "C:\Program Files (x86)\FRIENDSHIP-SYSTEMS\CAESES\bin\win64\CAESES_crt.exe" sweep.fsc with the newer versions of CAESES (and not CAESES-FFW). sweepbatch.zip
×
×
  • Create New...