Is there a way to vary the mnf file for a flex body within cases generated by Insight? It doesn't seem to take a design variable within View.

0 Jesper Slattengren over 3 years ago

In general I can see this being problematic. I believe that there might be some changes in the upcoming 2021.2 release that could help you out.

But what is it that you want to vary?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sarah.m.callan over 3 years ago

I have a couple different mnf files made from FEMs with different mass properties that I want to switch between during the runs
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Thomas Nygårds over 3 years ago

Hi @Sarah Callan !

To vary the mnf file you have to

1) create a design variable (string) containing the mnf filenames you wish to study like so:

var set var=.mymnfs string="c:/mnf1.mnf","c:/mnf2.mnf"

2) create another design variable (real) which you will vary in insight, think of it as the index of which file in .mymnfs you want to use.

var set var=.mymodel.mymnf_index real=1

3) create a simulation script (adam view commands) in which you do you simulations. But before the simulation commands you enter

part modify flexible_body name_and_position flex_body_name=.mymodel.myflexbody modal_neutral_file_name =(eval(.mymnfs[.mymodel.mymnf_index]))

Then export the model to insight and choose the variable mymnf_index as an factor to vary.

Hope this help

Regards

Thomas
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 michael.w.clarke over 3 years ago

The above approach should work if you are fine with running everything inside aview but I think you have to specify the index variable as a real type or insight won't list it as a candidate factor.

If you want to export the adm/acf files and run in the external solver (using "mdi insight build" to run a large # of cases in parallel on an HPC cluster) you can do some text manipulation tricks with swapping .mtx file references in the adm file (assuming the mnf geometry does not change and you have no aggregate_mass calls that reference the flexbody)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel