a defect of solidMechanics in foam-extend-3.0
hi,
I found a defect of solidMechanics in foam-extend-3.0 ! :confused: for example , I created a myelasticNonLinULSolidFoam just changing the elasticNonLinULSolidFoam from Code:
Info<< "Reading accumulated displacement field U\n" << endl; Code:
Info<< "Reading accumulated displacement field U\n" << endl; then, wmake to get the myelasticNonLinULSolidFoam ! and I created a case that replace U by Usolid too ! when we use this new solver to run a case which needs to use the accumulated displacement field(for example use the timeVaringFixedDisplacement boundary) , it will be error Code:
Starting time loop actually , I first found this problem in the icoFsiElasticNonLinULSolidFoam which use Usolid instead of U in solid part , for there is a U in fluid part ! I don't know what is wrong . maybe it is a bug ? what do you think ? thanks |
Hi,
Many of the solid mechanics boundary conditions (in $FOAM_SRC/solidModels/fvPatchFields) expect the displacement field to be called "U", and have this hard-coded into the boundary condition. So you would need to modify the specific boundary condition if you want to change the name of the displacement field, or add an optional variable to the boundary condition definition giving the name of the displacement field. Best regards, Philip |
All times are GMT -4. The time now is 21:43. |