Project solution as initial conditions
Hi,
Two questions about projecting a previous solution as initial condition for the next simulation:
1. Can I do it in Hypermesh? I only know how to do it in AcuCosolue
2. What it does is that it creates a nodal array of node id vs variable value, if I want to project a coarse mesh solution onto a fine mesh, the node ids will not match asI have more elements in the fine mesh, also the node numbering will be different. So this will not work?
Thanks.
Find more posts tagged with
When my problem/mesh with solution, plus the new mesh, are already on a remote machine, I typically use the tool acuProj to create the nodal initial condition files - projecting the solution onto a new .crd file. This will work nicely for your coarse-to-fine mesh study.
From the AcuSolve Cmd Prompt (or the Linux command) - for usage type
acuProj -h
I typically issue this in the directory with the original simulation for which I have results. Then (assuming my local Acusim.cnf has the problem specified), I just issue acuProj then specify the .crd (or .crd.B) file for the new mesh, already written out from the pre-processor. For example:
acuProj -pb old_model -crd ../NewModel/MESH.DIR/new_model.crd
It will then create the .nic files to be referenced in the input file for the new model. Move these .nic files to the new problem directory - then edit the input file. For example, in the NODAL_INTITIAL_CONDITION command for velocity:
NODAL_INITIAL_CONDITION( velocity ) {
type = nodal_values
nodal_values = Read( "old_model.vel.nic" )
}
Thank you Acupro, that was helpful.
Initially I thought that I should put the name of my log file as old_model but I was wrong, only the name of the model is needed as the program will search for Acusim.cnf file itself.
Altair EmployeeWhen my problem/mesh with solution, plus the new mesh, are already on a remote machine, I typically use the tool acuProj to create the nodal initial condition files - projecting the solution onto a new .crd file. This will work nicely for your coarse-to-fine mesh study.
From the AcuSolve Cmd Prompt (or the Linux command) - for usage type
acuProj -h
I typically issue this in the directory with the original simulation for which I have results. Then (assuming my local Acusim.cnf has the problem specified), I just issue acuProj then specify the .crd (or .crd.B) file for the new mesh, already written out from the pre-processor. For example:
acuProj -pb old_model -crd ../NewModel/MESH.DIR/new_model.crd
It will then create the .nic files to be referenced in the input file for the new model. Move these .nic files to the new problem directory - then edit the input file. For example, in the NODAL_INTITIAL_CONDITION command for velocity:
NODAL_INITIAL_CONDITION( velocity ) {
type = nodal_values
nodal_values = Read( "old_model.vel.nic" )
}
When my problem/mesh with solution, plus the new mesh, are already on a remote machine, I typically use the tool acuProj to create the nodal initial condition files - projecting the solution onto a new .crd file. This will work nicely for your coarse-to-fine mesh study.
From the AcuSolve Cmd Prompt (or the Linux command) - for usage type
acuProj -h
I typically issue this in the directory with the original simulation for which I have results. Then (assuming my local Acusim.cnf has the problem specified), I just issue acuProj then specify the .crd (or .crd.B) file for the new mesh, already written out from the pre-processor. For example:
acuProj -pb old_model -crd ../NewModel/MESH.DIR/new_model.crd
It will then create the .nic files to be referenced in the input file for the new model. Move these .nic files to the new problem directory - then edit the input file. For example, in the NODAL_INTITIAL_CONDITION command for velocity:
NODAL_INITIAL_CONDITION( velocity ) {
type = nodal_values
nodal_values = Read( "old_model.vel.nic" )
}