Following Cadence Design Systems’ acquisition of the Design & Engineering (D&E) business, the D&E Community Forum on the Nexus Community Center has been migrated in the Cadence Physical System Simulation Community. For more details and if you have any questions, please refer to the FAQ.

Stats

  • State Not Answered
  • Replies 5
  • Subscribers 3
  • Views 28
  • Members are here 0
More Content

Is there a way to speed up or control batch solver file generation?

SHonodel
I frequently generate hundreds or thousands of adm (and associated) files via mdi insight build command for a Monte Carlo analysis.  In this current​ MC analysis, my model is pretty large and has 3 flex bodies and 2MB of xmt_txt geometry so it takes about 15 seconds to generate each case.  So it takes 3 hours to generate 750 cases.  However, I am not changing the geometry between these cases so I assume the xmt_txt files are identical, right?  Is there an option to turn off the generation of the xmt_txt file and tell Solver (via .acf file, I assume) what xmt_txt file to use?
Parents
  • 0
    First things that'd come to my mind are not all ADAMS related:
    • How about speeding up file IO, i.e. installing a SSD ?
    • Are you solving the adm's parallel or sequential ? In the latter case: Have you tried internal solver instead of external ? That'd make the adm/xmt exports obsolete.
    • Is there any geometry used in calculation (like contacts)? If not, you could delete/deactivate the geometry before starting the batch runs which will avoid exporting any xmt's.
     
    And then a homework for MSC's development:
    If I defined geometry/parts a template/model by importing one ore more parasolid file(s), why "convert" that to a single parasolid on exporting the adm ?
    How about just keeping the original file references in the adm and save the re-write of huge geometry files ? I agree that in some cases I deliberately wanted this "conversion" and thus I'd vote for a setting to choose between the old and the newly proposed behaviour.
     
     
     
Reply
  • 0
    First things that'd come to my mind are not all ADAMS related:
    • How about speeding up file IO, i.e. installing a SSD ?
    • Are you solving the adm's parallel or sequential ? In the latter case: Have you tried internal solver instead of external ? That'd make the adm/xmt exports obsolete.
    • Is there any geometry used in calculation (like contacts)? If not, you could delete/deactivate the geometry before starting the batch runs which will avoid exporting any xmt's.
     
    And then a homework for MSC's development:
    If I defined geometry/parts a template/model by importing one ore more parasolid file(s), why "convert" that to a single parasolid on exporting the adm ?
    How about just keeping the original file references in the adm and save the re-write of huge geometry files ? I agree that in some cases I deliberately wanted this "conversion" and thus I'd vote for a setting to choose between the old and the newly proposed behaviour.
     
     
     
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.