|
[Sponsors] |
[solidMechanics] Support thread for "Solid Mechanics Solvers added to OpenFOAM Extend" |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
June 27, 2019, 15:38 |
|
#461 | |
New Member
Iago Lessa de Oliveira
Join Date: May 2015
Posts: 23
Rep Power: 11 |
Quote:
I already compiled it before at it worked with this version. Do you think it could be related to the foam-extend version? I noted this same kind of warning the last time I compiled it. Bests Iago |
||
June 29, 2019, 14:44 |
|
#462 | |
Super Moderator
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,091
Rep Power: 34 |
Quote:
I am not sure about the warnings but I would not worry about them; for the error, it comes from compiler options not available with gcc5 (-Wno-ignored-attributes -Wno-misleading-indentation). I have removed these now and pushed the changes to the development branch. I will merge the changes to the master once I have performed checks. Philip |
||
July 2, 2019, 21:39 |
|
#463 | |
New Member
Iago Lessa de Oliveira
Join Date: May 2015
Posts: 23
Rep Power: 11 |
Quote:
Thank you very much! I will check the development version then! Iago |
||
August 7, 2019, 23:26 |
|
#464 | |||
Senior Member
Hojatollah Gholami
Join Date: Jan 2019
Posts: 171
Rep Power: 7 |
Quote:
In Article "A Lagrangian Cell-Centred Finite Volume Method for Metal Forming Simulation", Page (5), you mentioned "The relative deformation gradient is given in terms of the displacement increment as f = I + ∇(u)T". But I saw in solid mechanics book that the deformation gradient is f =I+∇(u), without transpose. In OpenFOAM the code of deformation gradient was Quote:
Quote:
because for grad different in OpenFOAM, I found this is it OK? |
||||
August 28, 2019, 09:09 |
friction BC without contact model
|
#465 |
New Member
Denis Maier
Join Date: Aug 2019
Posts: 17
Rep Power: 7 |
Hey all,
I am working on the poro-elastoplasitc solvers by Tian Tang. For a multitude if situations concerning geotechnical problems I need to specify a friction boundary condition. The BC should either specify the displacement or traction (depending on the situation) for the normal component of the DU field. For the tangential component DU should be 0 as long as the resulting shear stress doesn't exceed the maximum value given by Coulomb's friction law (maxShear proportional to normal traction). If it does exceed, it should chance to a fixed (tangential) traction BC for that face and iteration. I was looking at the solidContact Boundary condition, but i think it is a bit overkill for what i need, since i dont need the ability of detachment and re-attachment of the material (yet). So i was thinking, I should be able to build on the fixedDisplacementZeroShear BC. However i can not seem to find where the tangential components are specified. I think the confusion stems from the whole valueFraction-issue that is quite hard to get the head around at the start. Can someone point me to the right lines in the fixedDisplacementZeroShear to modify? Greetings Denis |
|
September 17, 2019, 13:30 |
descomposePar solid problem
|
#466 |
Senior Member
alberto
Join Date: Apr 2016
Location: Mexico
Posts: 119
Rep Power: 10 |
Hello,
I have a problem, I hope some one can help me. I am trying to do a FSI simulation. I create a Mesh for the fluid and use the utility extrudeMesh to get the solid Mesh. When I run my case in series I dont have problem. But when I try to run my case in parallel, and use the decomposePar utility for the solid region I get this error, and when I descompose the fluid region doesnt have problem. Code:
Decomposing mesh solid Create time Time = 0 Create mesh for region solid Calculating distribution of cells Selecting decompositionMethod simple Finished decomposition in 0.02 s Calculating original mesh data Distributing cells to processors Distributing faces to processors Calculating processor boundary addressing Distributing points to processors Constructing processor meshes Violación de segmento (`core' generado) |
|
September 17, 2019, 15:44 |
|
#467 | |
Member
Lilian Chabannes
Join Date: Apr 2017
Posts: 58
Rep Power: 9 |
Quote:
I had a similar problem. My 2D mesh was imported from ICEM, but not perfectly 2D, you can check this by running checkMesh -region solid. You'll have warnings if it's not perfectly 2D, and that would most likely be the cause of your problem. However the case can still run in serial for some reasons. To solve the problem, simply make it properly 2D. If that is not the problem, I don't know then. Try different decomposition method (scotch method is cool).
__________________
Feel free to join the OpenFOAM Discord https://discord.gg/P9p9eHn, a live chat about OpenFOAM |
||
September 17, 2019, 21:28 |
|
#468 | |
Senior Member
Hojatollah Gholami
Join Date: Jan 2019
Posts: 171
Rep Power: 7 |
Quote:
maybe you describe your case, we can find your problem. |
||
November 19, 2019, 12:01 |
fsiFoam&foam-extend4.0: Restart issue
|
#469 |
New Member
Join Date: Mar 2017
Posts: 15
Rep Power: 9 |
Hi to everyone,
I'm working on fsi problems with foam-extend/4.0 and Fsifoam4.0. I'm currently trying to make a restart with initial data from specific time-step. The fluid side is not a problem and I'm sure the issue comes from the solid solver. I tried several possibilities but for now, I'm stuck with this error that I can't understand: Code:
Create time Create dynamic mesh for time = 0 Selecting dynamicFvMesh dynamicMotionSolverFvMesh Selecting motion solver: refVelocityLaplacian --> FOAM Warning : From function dlLibraryTable::open(const dictionary& dict, const word& libsEntry, const TablePtr tablePtr) in file /soft/foam-extend-4.0/foam/foam-extend-4.0/src/foam/lnInclude/dlLibraryTableTemplates.C at line 67 library "libfvMotionSolver.so" did not introduce any new entries Selecting motion diffusion: quadratic Selecting motion diffusion: inverseDistance Reading stress mesh [9] [9] [9] --> FOAM FATAL ERROR: [9] Cannot find file "points" in directory "constant/solid/polyMesh" [9] [9] From function Time::findInstance(const fileName&, const word&, const IOobject::readOption) [9] in file db/Time/findInstance.C at line 148. [1] [1] My first question is: Did anyone face the same issue ? Meanwhile, when I post-process my solid results for parallel cases, I'm unable to reconstruct them. (With paraview, I only use Decomposed Case.) It seems that I need meshPhi to reconstruct the solid domain. For now, I have changed the IOobject in unsTotalLagrangianSolid.C with no success because meshPhi is not written. Code:
// meshPhi must be present in order to reconstruction procedure works surfaceScalarField meshPhi ( IOobject ( "meshPhi", runTime().timeName(), mesh(), IOobject::READ_IF_PRESENT, IOobject::AUTO_WRITE ), mesh(), dimensionedScalar("0", dimVolume/dimTime, 0.0) ); meshPhi.write(); } My second question is: How can I nicely reconstruct the solid domain ? (in order to make a restart possible.) Until today, I'm executing this: Code:
#!/bin/bash mkdir tmp cd fluid for proc in processor*; do mkdir ../tmp/$proc for time in $proc/*; do ln -s ../../fluid/$time/solid ../tmp/$time done done ln -s ../solid/system ../tmp/system ln -s ../solid/constant ../tmp/constant ln -s ../solid/0 ../tmp/0 cd ../tmp touch solid.foam Thanks in advance, Paul |
|
November 19, 2019, 12:27 |
|
#470 |
Super Moderator
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,091
Rep Power: 34 |
Hi Paul,
Although it will not directly solve your problem, it might be useful to try it out in solids4foam as some of these issues may have been fixed; PM me with your email address if you would like to use it. Philip |
|
January 15, 2020, 13:32 |
|
#471 |
Member
Kellis
Join Date: Mar 2017
Posts: 39
Rep Power: 9 |
Good afternoon,
When attempting to start the elasticOrthoNonLinULSolidFoam solver from a time other than zero, it complains of not being able to locate the materialDirections file in the timestep folder. Checking the orthotropicLinearElastic.C file, the materialDirections file is set to NO_WRITE. Is there any reason it shouldn't be changed to write in the saved timestep directories, to allow for the case to restart at a non-zero time? Thanks, Kellis |
|
January 17, 2020, 00:29 |
|
#472 | |
Senior Member
Hojatollah Gholami
Join Date: Jan 2019
Posts: 171
Rep Power: 7 |
Hi
I'm not familiar with this solver, but usually you can change IOobject to writing file in disk, it only increase storage. In general solvers, usually use NO_Write to make less storage. Quote:
|
||
January 17, 2020, 03:55 |
Did you solve this?
|
#473 |
Member
Torsten Schenkel
Join Date: Jan 2014
Posts: 69
Rep Power: 12 |
Hi,
if you did solve this, could you let us know, what combination worked? I have the same errors. Thanks |
|
January 17, 2020, 05:07 |
|
#474 |
New Member
Erik
Join Date: Jul 2019
Posts: 7
Rep Power: 7 |
Hi,
i'm currently writing my master thesis with geotechnical background. For my thesis i'm using the elasticSolidFoam Solver. Because of pressuretests i'm doing for my testcase models, i need to know what SI Unit foam-extend exactly uses. So my Boundary Conditions need some pressures. I'm guessing Pa for pressure? Has the pressure of the BC to be normalized with the density of the material? It would be very great, if you could help me. My BC for U looks like: boundaryField { pressureside { type solidTraction; traction uniform (0 0 0); // I would like to set 80 bar pressure pressure uniform 8e+06; value uniform (0 0 0); } side with role conditon { type symmetryPlane; } } Whats the difference between setting the pressure bc from: traction uniform (0 0 8e+06) to my current bc setting pressure uniform 8e+06 ? Or would the result be the same, if my pressure bc has to be set in z-direction? As i understand traction uniform () you can set different vectors in traction uniform (), right? Can i set the pressure bc with time variation, too? So like to set the pressure bc with increasing pressure from 10 to 80 bar? Sorry for so many questions i have. Kind regards Erik Last edited by erik87; January 17, 2020 at 12:27. |
|
January 17, 2020, 13:00 |
|
#475 | ||||||
Super Moderator
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,091
Rep Power: 34 |
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Code:
myPatch { type solidTraction; traction uniform (0 0 0); pressureSeries { fileName "$FOAM_CASE/constant/timeVsPressure; outOfBounds clamp; } value uniform (0 0 0); } Code:
( (0 10e5) (10 80e5) ) Philip |
|||||||
January 20, 2020, 17:28 |
|
#476 |
New Member
Erik
Join Date: Jul 2019
Posts: 7
Rep Power: 7 |
Thank you very much Philip
Is it correct to say, that using only the nonuniform internalField from U volVectorField would be enougth for initial conditon for stress simulation? I'm using mapFields for getting the nonuniform internalField, but in the first step of my simulations i'm just getting the U Field interpolated to my next mesh. |
|
January 20, 2020, 18:02 |
|
#477 |
Member
Torsten Schenkel
Join Date: Jan 2014
Posts: 69
Rep Power: 12 |
||
January 21, 2020, 06:15 |
|
#478 |
New Member
Join Date: Mar 2017
Posts: 15
Rep Power: 9 |
Hello everyone,
While using Solids4foam for my new cases, I need to finish some works with fsifoam (and FE4.0). I have mainly two situations: 1) I needed to refine my fluid mesh and it doesn't matter the time step value, the number of processors used for the decomposition, etc..., this kind of error appears (while my case was running with larger cells..): Code:
[1] --> FOAM FATAL ERROR: [1] face 1268 area does not match neighbour by 0.102887% -- possible face ordering problem. patch: procBoundary1to2 my area: 2.50158e-05 neighbour area: 2.49901e-05 matching tolerance: 1 Mesh face: 300506 vertices: 4((0.060402 -0.0942063 0.248161) (0.0538921 -0.0941869 0.237484) (0.053892 -0.096 0.238672) (0.060402 -0.0959902 0.250003)) Rerun with processor debug flag set for more information. [1] [1] From function processorPolyPatch::calcGeometry() [1] in file meshes/polyMesh/polyPatches/constraint/processor/processorPolyPatch.C at line 230. [1] FOAM parallel run exiting 2) As I'm not sure where my problem comes from, I tried to use the FE dynamic mesh solver, which I read gives much more robust results. I'm struggling to use it with fsiFoam and foam-extend/4.0. This error appears: Code:
--> FOAM FATAL ERROR: Field size: 213 does not match number of points: 979 From function tmp<Foam::Field<Type> > tetPolyPatchInterpolation::pointToPointInterpolate ( const Field<Type>& ff ) const in file /soft/foam-extend-4.0/foam/foam-extend-4.0/src/tetFiniteElement/lnInclude/tetPolyPatchInterpolate.C at line 112. Code:
if (ff.size() != patch_.patch().size()) { FatalErrorIn ( "tmp<Foam::Field<Type> >\n" "tetPolyPatchInterpolation::faceToPointInterpolate\n" "(\n" " const Field<Type>& ff\n" ") const" ) << "Field size: " << ff.size() << " does not match number of faces: " << patch_.patch().size() << abort(FatalError); } Could my second question solve the first one ? Any help is welcome on both situation... ! Best, Paul |
|
January 21, 2020, 18:40 |
|
#479 |
Member
Kellis
Join Date: Mar 2017
Posts: 39
Rep Power: 9 |
Paul,
Do you have your FSI boundaries declared as global face zones in the decomposeParDict for both fluid and solid? I.e.: Code:
globalFaceZones ( fsiBoundaryPatchName ) Thanks, Kellis |
|
January 22, 2020, 05:52 |
|
#480 | |
Super Moderator
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,091
Rep Power: 34 |
Quote:
Some fluid solvers (incompressible flow) in OpenFOAM use kinematic pressure and most solid solvers use pressure in Pa. It depends on the specific solver. However, for the solidTraction solid boundary condition, it assumes Pa regardless of the solid solver using it. Philip |
||
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
GPU Linear Solvers for OpenFOAM | gocarts | OpenFOAM Announcements from Other Sources | 37 | August 17, 2022 14:22 |
[Virtualization] OpenFOAM oriented tutorial on using VMware Player - support thread | wyldckat | OpenFOAM Installation | 2 | July 11, 2012 16:01 |
New OpenFOAM Forum Structure | jola | OpenFOAM | 2 | October 19, 2011 06:55 |
Cross-compiling OpenFOAM 1.7.0 on Linux for Windows 32 and 64bits with Mingw-w64 | wyldckat | OpenFOAM Announcements from Other Sources | 3 | September 8, 2010 06:25 |
OpenFOAM Debian packaging current status problems and TODOs | oseen | OpenFOAM Installation | 9 | August 26, 2007 13:50 |