HX: Billet not fully consumed
Hi all,
I am running a set of simulations using the same .grf file with the idea of varying parameters of temperature and ram speed.
Given that the ram speed affects the simulation time - time steps at all 4 levels are adapted and the new .hx data deck is prepared in such a way. Nevertheless, if I launch the solver using an already existing .grf and newly adapted .hx file with updated information on ram speed and time steps distribution - the billet is not fully consumed by the end of the successfully terminated simulation.
For example,
I have a ram speed of 1 mm/s, and a billet of length 170 mm approx -> timesteps are calculated as in the scheme proposed by guidelines (1.0 1 | (T_end/2 + 1.0)/2 numberOfTmstps(2 seconds approx) | T_end/2 numberOfTmstps(3 seconds approx) | T_end numberOfTmstps(4 seconds approx) ) which yields 52 timesteps. The billet length is fully consumed.
If I vary the ram speed and set it to 10 mm/s, and a billet length is still the same (170 mm approx) -> timesteps are calculated in the same scheme, but now the T_end is different (approx 170 mm / 10mm/s is approx 17 s).
When launching both simulations, the same reference .grf is used, but in the case of 10mm/s -> the billet is not fully consumed.
The only things that changed in the data deck .hx are the ram speed & time step size lines. What am I missing? What else should be changed in order for the billet to be fully consumed by the final timestep?
I am using Altair HyperMesh 2022 from which I launch the solver in the batch mode using the data deck which is in the folder with the respective .grf. I checked the naming, all the variables, parameters in the Utility tab etc. Also, simulation terminates successfully, but not with the correct, or, to be precise, the desired result.
Please let me know how can I avoid this problem occurring when varying the ram speed.
Thank you in advance.
Answers
-
Did you change anything in the grf file. I think the ram speed in the grf file should be changed too.
0