Enclosed attribute for volume response

Bocaj22
Bocaj22 Altair Community Member
edited December 2022 in Community Q&A

Hello,

I'd like to use the ATTA=ENCLOSED option for a volume response in my optimization. Is there a way to do this within hypermesh? I can do it by manually changing the solver deck, but it's quite inconvenient. I don't see any options when building the resposne, and I'm unable to do a card edit. Also, whenever I re-import the solver deck into hypermesh, it erases that property. So I need to manually change it in notepad before every run. Any recommendations would be helpful.

Thanks,

bocaj22

Best Answer

  • Adriano_Koga
    Adriano_Koga
    Altair Employee
    edited December 2022 Answer ✓

    I believe this is not supported yet in HM, that's why it gets erased when imported.

    My suggestion to you, as a workaround, is to edit this manually once, and give it the right values to it, and then, instead of leaving this explicitely defined in your main model, add it as an include file, and do not update it, if prompted.

     

    main_model.fem

    ...

    SUBCASES

    ..

    BEGIN BULK

    include volume_resp.fem

    GRIDS...

    ELEMENTS...

    ...

    ENDDATA

     

    volume_resp.fem has:

    ...

    DRESP1,......

    ..

Answers

  • Adriano_Koga
    Adriano_Koga
    Altair Employee
    edited December 2022 Answer ✓

    I believe this is not supported yet in HM, that's why it gets erased when imported.

    My suggestion to you, as a workaround, is to edit this manually once, and give it the right values to it, and then, instead of leaving this explicitely defined in your main model, add it as an include file, and do not update it, if prompted.

     

    main_model.fem

    ...

    SUBCASES

    ..

    BEGIN BULK

    include volume_resp.fem

    GRIDS...

    ELEMENTS...

    ...

    ENDDATA

     

    volume_resp.fem has:

    ...

    DRESP1,......

    ..

  • Bocaj22
    Bocaj22 Altair Community Member
    edited December 2022

    I believe this is not supported yet in HM, that's why it gets erased when imported.

    My suggestion to you, as a workaround, is to edit this manually once, and give it the right values to it, and then, instead of leaving this explicitely defined in your main model, add it as an include file, and do not update it, if prompted.

     

    main_model.fem

    ...

    SUBCASES

    ..

    BEGIN BULK

    include volume_resp.fem

    GRIDS...

    ELEMENTS...

    ...

    ENDDATA

     

    volume_resp.fem has:

    ...

    DRESP1,......

    ..

    Hi Adriano,

    Thank you for providing a workaround. Hopefully this card is added in the future.