Issues with .adf files betweeen hyperstudy motionview optimization
Hello all,
I'm experiencing issues with setting up an Hyperstudy optimization for a full vehicle manouvre built through Motionview.
The model itself is custom built, while the manouvre is a standard MotionView Event.
The manouvre is a normal constant radius turn, and runs perfectly if ran using MotionSolve:
However when the same model is plugged into Hyperstudy, it features the following error:
If I set up a full vehicle model only using the wizards belonging to the Vehicle Dynamics toolset within Motioview, Hyperstudy is able to read the .adf file an the optimization setup continues.
Has anyone experienced this before ? Does anyone have any ideas on how to fix this issue?
Answers
-
Hi Claudio - Most likely, the reason is that the .adf file hasnt been referenced in the Model Resource section when the model was first setup. I recommend that you repeat the setup in the following way:
1) Export a .mdl model archive from MotionView instead of the original .mdl (Top menu, File->Export->Model->Archive Model->Export). This will ensure that all externally referenced files are contained in the same folder, making it easy to do the next step.
2) Add all of the externally referenced files like .tir, .adf etc into the model resources, as shown:
3) Perform a nominal run to check if this works, then proceed as normal.
Thanks,
Ananth
1 -
Hi Ananth
The error persisits even after referencing all the external files in "Modl Resources". The .adf belongs to a sepecific `Road Course Event` simulation. Is there any other .adf to reference?
Any help at the earliest would be highly appreciated.
Best Regards
Yugal
0 -
Hello Yugal,
A workaround, you can utilize the adf as a parameterized model. Extract the desired parameters to use them as input variables.
Execute the parameterized file to generate the output folder.
Within the MotionView model, establish a dataset featuring a string input, then save the model.
In a text editor, modify the dataset string value to {Solver_Filename.path} + “ADFfilename.adf”
Revise the driver task file to match the input value from the dataset.
Save the file.
Incorporate the MotionView model into the Study. Within the model resources, establish a connection with the adf file generated from the parameterized file.
Best,
Christopher Fadanelli
1 -
Hello Yugal,
A workaround, you can utilize the adf as a parameterized model. Extract the desired parameters to use them as input variables.
Execute the parameterized file to generate the output folder.
Within the MotionView model, establish a dataset featuring a string input, then save the model.
In a text editor, modify the dataset string value to {Solver_Filename.path} + “ADFfilename.adf”
Revise the driver task file to match the input value from the dataset.
Save the file.
Incorporate the MotionView model into the Study. Within the model resources, establish a connection with the adf file generated from the parameterized file.
Best,
Christopher Fadanelli
Issue regarding reading in the adf file is fixed in version 2024.
Best,
Christopher Fadanelli
1
Altair Employee