Hi PhysicsAI users,
When performing prediction using inputs via ‘Global’ or ‘Nodal’ Hooks approach in PhysicsAI, the below mentioned considerations are important to be followed.
- The CAD or solver deck to be used for prediction should have an associated .json file named _predict_inp.json which should be saved in the _hooks folder. Make sure that the .json file has no prefix to it.
- The file structure of the _predict_inp.json file should be matching the .json files used for creating an input via ‘Global’ or ‘Nodal’ Hooks.
- Make sure to select the right ‘Solver Interface’ when importing the solver deck for prediction.For example, use OptiStruct when using .fem file as a solver deck, use RADIOSS when using .rad file as a solver deck, use ABAQUS (2D/3D) when using .inp file as a solver deck.
Incorrect naming of the .json file or incorrect structure in the _hooks folder will create an error (no model with label ABC found) during the prediction step.
- Here, ABC is a reference to the input label used during PhysicsAI model training.
- If Youngs Modulus ‘E’ has been used as an input during PhysicsAI model training, then, the error can be ‘no model with label E found'.
If the .json file is indeed correctly named & has no file-structure related issues, then, the error (no model with label ABC found) would still occur for any of the solver decks other than OptiStruct & RADIOSS.
To fix the issue related to non-HyperWorks solver deck (ABAQUS, LS-DYNA, Nastran etc.), one has to edit the global_inputs_hook.py/nodal_inputs_hook.py files as mentioned below (ABAQUS solver deck as an example).
- Edit the line 21 in the global_inputs_hook.py file to add ‘.inp’ as one of the acceptable formats.
- Edit the line 25 in the nodal_inputs_hook.py file to add ‘.inp’ as one of the acceptable formats.
Note:
- For Nastran solver decks, the .py files needs to be edited with ‘.bdf’ as the acceptable file format.
- For LS-DYNA solver decks, the .py files needs to be edited with ‘.k’ as the acceptable file format.
- For other formats not listed in the blog, kindly check the folder (where HyperMesh settings are saved) to see the extension of the solver deck once you import the file in HyperMesh & then use the same file format in the .py files.
