optistruct stops with no warnings or errors What next? - SOLVED

Carlton Matthew_20281
Carlton Matthew_20281 Altair Community Member
edited March 2023 in Community Q&A

I've set up my model in Hyperworks 2022, used Validate->Model to remove all warnings and errors.

On running I get only this in the .out file (how do I find the error?) 

 ************************************************************************
 **                                                                    **
 **                                                                    **
 **                     Altair OptiStruct(TM) 2022                     **
 **                                                                    **
 **             Advanced Engineering Analysis, Design and              **
 **        Optimization Software from Altair Engineering, Inc.         **
 **                                                                    **
 **   OptiStruct includes an enhanced proprietary version of NASTRAN   **
 **                                                                    **
 **                                                                    **
 **                Windows 10  (Build 9200)  RL-4015628                **
 **         12 CPU:  Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz         **
 **                    52131 MB RAM,  75096 MB swap                    **
 **                                                                    **
 ** Build: 1110680uwn33220_Ce64RB68UH14M:201153-000  46004004000000014 **
 ************************************************************************
 **  COPYRIGHT (C) 1996-2022                 Altair Engineering, Inc.  **
 ** All Rights Reserved.  Copyright notice does not imply publication. **
 **         Contains trade secrets of Altair Engineering, Inc.         **
 ** Decompilation or disassembly of this software strictly prohibited. **
 ************************************************************************
 
  
 *** OptiStruct defaults set from:
   install config file: C:/Program Files/Altair/2022/hwsolvers/optistruct.cfg.
  
  
 NOTE # 9199
 MSGLMT=STRICT is active, all messages will be printed.
 You can suppress some less important warning messages by use of
  MSGLMT=BRIEF or UNREF (in config file or in the input data).

Answers

  • PaulAltair
    PaulAltair
    Altair Employee
    edited March 2023

    Can you share your model? There is nothing to go on from that output

  • Carlton Matthew_20281
    Carlton Matthew_20281 Altair Community Member
    edited March 2023

    Unfortunately, I'm not at liberty to share the model. The .hm file is too large to pass our firewall anyway.

    I tried importing the .fem file int a clean Hyperworks, it gives the message

    Importing DA42Console_IssA.fem results in the message;

    Error:      Invalid value in integer field (********) on line 33431, file C:/QQData/5933_DA42Console/FEA_Console/DA42Console_IssA.fem

                    Resolution:  Quitting..

    Summary:Feinput finished with 1 errors and 0 warnings.
    The relevant section of the .fem file is shown below.

    image

  • Carlton Matthew_20281
    Carlton Matthew_20281 Altair Community Member
    edited March 2023

    Unfortunately, I'm not at liberty to share the model. The .hm file is too large to pass our firewall anyway.

    I tried importing the .fem file int a clean Hyperworks, it gives the message

    Importing DA42Console_IssA.fem results in the message;

    Error:      Invalid value in integer field (********) on line 33431, file C:/QQData/5933_DA42Console/FEA_Console/DA42Console_IssA.fem

                    Resolution:  Quitting..

    Summary:Feinput finished with 1 errors and 0 warnings.
    The relevant section of the .fem file is shown below.

    image

    SOLVED.

    The root cause of the problem was component IDs with 7 or more digits.

    This corrupts the .fem input file but is not spotted at the time when defined, or by the Validate->Model checks.

  • PaulAltair
    PaulAltair
    Altair Employee
    edited March 2023

    Odd, seems like a bug, the components are only HM comments and don't 'exist' as such in Optistruct, so while HM doesn't like them, I'm surprised it causes an issue when running the solver (the lines are all commented out so far as OptiStruct is concerned)

    Glad you found a resolution anyway!