Well, as far as i understand local time stepping theory/algorithm, it is not possible to use it for any unsteady simulation (for now...)
Also which version of Foam are you using. Last time i checked it was not possible to run simulation with both waves and forward speed. Am i wrong ? |
3 Attachment(s)
Sorry to come back again on this thread, I still have lot of issue with my calculations.
I try to simulate flow aroudn a ship hull with LTSInterFoam, everything looks find and stable and it suddenly diverges (see forces plot attached) I'm using the fv Schemes and fvSolution files from the DTCHull tutorial. I've studied the BC wich are very close to those used in this tutorial. What looks weird in the velocity fields is that I have high velocity spot close to the free surface at the bow of the boat and behind the boat (just abve the free surface). Any hints to solve this???? Regards Jordan |
romainRH,
I am using OpenFoam 2.3.1 |
Unwanted wave field
4 Attachment(s)
Hi,
I have now issue with a DTMB5415 test case. I have made some test with relatively good results but I encounter some weird wave fields at low froud number. I have unwanted wave in my domain. I tried to increase domain size, change BC, no real effect. I think I have reflexion of the waves downstream the hull, but what is really weird is the sort of wave I have in front of the boat (see attached pictures). I'm solving this problem with interFoam, so no fluid structure interaction. I attached two different set of BC if someone want have a look and tell me if anything is completely wrong about that. Has anyone got the same problem? Or an idea o solve this? Thanks a lot !!! |
Hi Jojosaxo,
I do not know if this will help, but when I had similar problems it was a matter of mesh. Also, the interface from coarse to fine (refined) generates waves, I suggest using multi grading to avoid this effect. Good lack, Carlos. |
1 Attachment(s)
Hi!
Thank you for your help! How did you solve this from a matter of mesh? Here is a screenshot of the mesh at the level of the free surface! How would you change it? |
Snappyhexmesh for refinement on bow, transom, kelvin wake
Hello,
I've been working through learning about the DTChull case. I am trying to get volume refinements at the bow and transom and have surface refinement around the kelvin wake. I have created two searchablebox geometries and an stl file of the triangular kelvin wake. In addition I have the free surface refinement of the original DTCHull example, that I have adapted to fit my domain and water depth. It keeps throwing me errors. Is there something I should be doing differently? Should I be making the bow and transom refinements as stl and trim out the part of the bow that intersects the hull? How can I get these refinements to play nicely with each other? Does anyone have any tricks to getting intersecting refinement regions to work? Thank you for your help! /*--------------------------------*- C++ -*----------------------------------*\ | ========= | | | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox | | \\ / O peration | Version: 2.4.0 | | \\ / A nd | Web: www.OpenFOAM.org | | \\/ M anipulation | | \*---------------------------------------------------------------------------*/ FoamFile { version 2.0; format ascii; class dictionary; object snappyHexMeshDict; } // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // // Which of the steps to run castellatedMesh true; snap true; addLayers true; // Geometry. Definition of all surfaces. All surfaces are of class // searchableSurface. // Surfaces are used // - to specify refinement for any mesh cell intersecting it // - to specify refinement for any mesh cell inside/outside/near // - to 'snap' the mesh boundary to the surface geometry { DTC-scaled.stl { type triSurfaceMesh; name hull; patchInfo { type wall; } } Kelvin-Wake.stl { type triSurfaceMesh; name kelvin; patchInfo { type wall; } } bowrefinementBox { type searchableBox; min (7.18401 -1 -0.149903); max (10.0931 1 0.662375); } transomrefinementBox { type searchableBox; min (-0.509046 -1.18756 -0.0440771); max (1.71845 1.18756 0.475878); } }; // Settings for the castellatedMesh generation. castellatedMeshControls { // Refinement parameters // ~~~~~~~~~~~~~~~~~~~~~ // If local number of cells is >= maxLocalCells on any processor // switches from from refinement followed by balancing // (current method) to (weighted) balancing before refinement. maxLocalCells 500000; // Overall cell limit (approximately). Refinement will stop immediately // upon reaching this number so a refinement level might not complete. // Note that this is the number of cells before removing the part which // is not 'visible' from the keepPoint. The final number of cells might // actually be a lot less. maxGlobalCells 2000000; // The surface refinement loop might spend lots of iterations refining just a // few cells. This setting will cause refinement to stop if <= minimumRefine // are selected for refinement. Note: it will at least do one iteration // (unless the number of cells to refine is 0) minRefinementCells 0; // Number of buffer layers between different levels. // 1 means normal 2:1 refinement restriction, larger means slower // refinement. nCellsBetweenLevels 3; // Explicit feature edge refinement // ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Specifies a level for any cell intersected by its edges. // This is a featureEdgeMesh, read from constant/triSurface for now. features ( { file "DTC-scaled.eMesh"; level 0; } { file "Kelvin-Wake.eMesh"; level 0; } ); // Surface based refinement // ~~~~~~~~~~~~~~~~~~~~~~~~ // Specifies two levels for every surface. The first is the minimum level, // every cell intersecting a surface gets refined up to the minimum level. // The second level is the maximum level. Cells that 'see' multiple // intersections where the intersections make an // angle > resolveFeatureAngle get refined up to the maximum level. refinementSurfaces { hull { // Surface-wise min and max refinement level level (0 0); } kelvin { // Surface-wise min and max refinement level level (0 0); } } resolveFeatureAngle 45; // Region-wise refinement // ~~~~~~~~~~~~~~~~~~~~~~ // Specifies refinement level for cells in relation to a surface. One of // three modes // - distance. 'levels' specifies per distance to the surface the // wanted refinement level. The distances need to be specified in // descending order. // - inside. 'levels' is only one entry and only the level is used. All // cells inside the surface get refined up to the level. The surface // needs to be closed for this to be possible. // - outside. Same but cells outside. refinementRegions { bowrefinementBox { mode inside; levels ((4 4)); } transomrefinementBox { mode inside; levels ((4 4)); } } // Mesh selection // ~~~~~~~~~~~~~~ // After refinement patches get added for all refinementSurfaces and // all cells intersecting the surfaces get put into these patches. The // section reachable from the locationInMesh is kept. // NOTE: This point should never be on a face, always inside a cell, even // after refinement. locationInMesh (-2 -1 0); // Whether any faceZones (as specified in the refinementSurfaces) // are only on the boundary of corresponding cellZones or also allow // free-standing zone faces. Not used if there are no faceZones. allowFreeStandingZoneFaces true; } // Settings for the snapping. snapControls { //- Number of patch smoothing iterations before finding correspondence // to surface nSmoothPatch 3; //- Relative distance for points to be attracted by surface feature point // or edge. True distance is this factor times local // maximum edge length. // tolerance 4.0; tolerance 1.0; //- Number of mesh displacement relaxation iterations. nSolveIter 100; //- Maximum number of snapping relaxation iterations. Should stop // before upon reaching a correct mesh. nRelaxIter 5; nFeatureSnapIter 10; } // Settings for the layer addition. addLayersControls { // Are the thickness parameters below relative to the undistorted // size of the refined cell outside layer (true) or absolute sizes (false). relativeSizes true; // Per final patch (so not geometry!) the layer information layers { hull { nSurfaceLayers 3; } } // Expansion factor for layer mesh expansionRatio 1.5; // Wanted thickness of final added cell layer. If multiple layers // is the thickness of the layer furthest away from the wall. // Relative to undistorted size of cell outside layer. // See relativeSizes parameter. finalLayerThickness 0.7; // Minimum thickness of cell layer. If for any reason layer // cannot be above minThickness do not add layer. // See relativeSizes parameter. minThickness 0.25; // If points get not extruded do nGrow layers of connected faces that are // also not grown. This helps convergence of the layer addition process // close to features. // Note: changed(corrected) w.r.t 17x! (didn't do anything in 17x) nGrow 0; // Advanced settings // When not to extrude surface. 0 is flat surface, 90 is when two faces // are perpendicular featureAngle 60; // Maximum number of snapping relaxation iterations. Should stop // before upon reaching a correct mesh. nRelaxIter 5; // Number of smoothing iterations of surface normals nSmoothSurfaceNormals 1; // Number of smoothing iterations of interior mesh movement direction nSmoothNormals 3; // Smooth layer thickness over surface patches nSmoothThickness 10; // Stop layer growth on highly warped cells maxFaceThicknessRatio 0.5; // Reduce layer growth where ratio thickness to medial // distance is large maxThicknessToMedialRatio 0.3; // Angle used to pick up medial axis points // Note: changed(corrected) w.r.t 17x! 90 degrees corresponds to 130 in 17x. minMedianAxisAngle 90; // Create buffer region for new layer terminations nBufferCellsNoExtrude 0; // Overall max number of layer addition iterations. The mesher will exit // if it reaches this number of iterations; possibly with an illegal // mesh. nLayerIter 50; // Max number of iterations after which relaxed meshQuality controls // get used. Up to nRelaxIter it uses the settings in meshQualityControls, // after nRelaxIter it uses the values in meshQualityControls::relaxed. nRelaxedIter 20; } // Generic mesh quality settings. At any undoable phase these determine // where to undo. meshQualityControls { #include "meshQualityDict" } // Advanced // Flags for optional output // 0 : only write final meshes // 1 : write intermediate meshes // 2 : write volScalarField with cellLevel for postprocessing // 4 : write current intersections as .obj files debug 0; // Merge tolerance. Is fraction of overall bounding box of initial mesh. // Note: the write tolerance needs to be higher than this. mergeTolerance 1E-6; // ************************************************** *********************** // |
Hi Juli, may i know how you get the results for your 3rd picture?
|
Problem with KVLCC2 tanker mesh
5 Attachment(s)
Hello! I am running a case of the KVLCC2 tanker, but for some reason i can't make the mesh properly. I am posting in this thread, because it is related to ship cases. I use the DTC tutorial in OpenFOAM as a basis and modify it in order to be OK for my model. The iges file, from which i created the stl for OpenFOAM, was downloaded from the SIMMAN 2008 website. There were some problems with it, because it was filled with holes, which i tried to fill in using SALOME and sewing tool. Even after all this the stern looks strange and creates problems. Also the timestep continuity error for the pressure if enormously high as are the results for the forces too, but I believe it is due to the bad geometry. Here are the checkMesh results:
Code:
/*---------------------------------------------------------------------------*\ Attachment 54084 Attachment 54085 Attachment 54086 Attachment 54087 Attachment 54088 Thank you very much in advance! Best regards, Kiril Todorov |
Quote:
I`m investigating the problems you studied around ten years ago. I searched the internet and your work still looks most impressive. It is possible to get your files, as it is not available to download now. My email is luofeng0515@hotmail.com. Many thanks Best regards, Luofeng |
Quote:
|
Unable to get a proper wave pattern !!
3 Attachment(s)
Dear Foamers,
I spent many weeks trying to get the good wave pattern (KIM measurements 2001) from KCS model. I noticed that if the mesh are very elongated (see pictures attached mesh is around 1.5 M cells) the wave pattern is damped. Are you ok with that ? (In this paper http://www.academia.edu/28622908/THE...OURCE_OVERVIEW they achieve to get a wonderful wave pattern with a mesh very close to mine) How they do it ? The ratio near outlet is voluntary huge to avoid wave reflexion. I tried another mesh strategy by using a refinement Box on the free surface (so cubic mesh and no elongation). The results in term of wave pattern seem better (less damping) but the cells number goes to 3 M. Another problem I noticed is the behavior of the pressure coefficient. My pressure coefficient oscillate strongly (and reach positive values !!) (at least during 5000 iterations and sometimes more). Is it possible to obtain reliable results with a cell number around 1.5 M (like in the study) ? What is the influence of shemes and solver settings ? What are the good boundaries conditions ? Actually I am using the same as DTC HULL tutorial : alpha.water inlet fixedValue outlet : variableHeightFlowrate top : inletOutlet hull : zeroGradient others : symmetry U inlet fixedValue outlet : outletPhaseMeanVelocity top : pressureInletOutletVelocity hull : noSlip others : symmetry p_rgh inlet fixedFluxPressure outlet : fixedFluxPressure top : totalPressure hull : fixedFluxPressure others : symmetry nut inlet calculated outlet : calculated top : calculated hull : nutkWallFunction others : symmetry omega and k inlet fixedValue outlet : inletOutlet top : inletOutlet hull : nutkWallFunction or kqRWallFunction others : symmetry Thanks a lot for your help ! PS : I am using OF5 with LTSInterfoam (interFoam with localEuler scheme) PPS : Here are my fvScheme and fvSolution files Quote:
Quote:
|
Hi everyone,
I changed my BC setup, mesh and also solver setting but it's also impossible to calculate the true kelvin wave pattern. I tried to mesh the interface water/air with cell size of 5 mm but the wave pattern remains damped. I tried interFoam without LTS option without success on the kelvin wave pattern. I also tried several schemes for alpha.water : linear, vanleer or interfaceCompression but no real influence on the results. I changed the BC setup to the following (without success): inlet, side, top and bottom as inlet for U, fixedFLuxPressure for p_rgh. for outlet : fixedValue 0 for p_rgh and zeroGradient for U. In all the cases the wave pattern is strongly damped behind the hull and no waves are calculated after x = -0.5/Lpp EDIT : switch on the momentum predicator in the PISO loop improve the results. I am going to try with the last version of openFoam.com (17.06) wich provide an improved way to capture water/Air interface. Any advices ? Thanks :) |
Fauster,
can you show the wave pattern? can you show the mesh on the water plane? thanks in advance, |
Quote:
Since my last post I increased the calculation box and refined the number of cells in the longitudinal direction. I also noticed an important fact : it's important to avoid polyhedral cells near the free surface. This cells are created by the refineMesh operation for transitioning between two levels. From my experience this cells affect the result in a bad manner. |
Dear Foamer,
I am still working on CFD for ship resistance and I would like to know your initialization strategy. For example if I want to run a transient analysis with interfoam or interdymfoam case (like DTChull tutorial) I put at t = 0 sec the hull in a non zero velocity field. By doing this you creates a large wave at the bow and depending of the mesh you can produce numerical ventilation. Moreover if you have a 2DOF you will get significant accelerations and numerical instabilities. Do you have an idea to avoid this behavior by having a smart strategy ? Thanks in advance ! F |
Quote:
With the ventilation I can not help you, the only thing that I usually do is to use a variable time step based on the Courant number and I think that this improve ventilation, but maybe is my imagination... XD Regards! |
Quote:
For the ventilation I found out that interfaceCompression BC is designed for avoiding numerical ventilation. On my last run it appears to be very promising. |
Dear Foamer,
For all my hull resistance simulation the pressure coefficient shows large oscillations (as I described in a previous post). This behavior really slow down the time before reaching a quasy steady state. I thought it came from the boundary condition used in the tutorials DTChull :
Is it possible that it comes from fvsolution settings ? (I used the same as the tutorial). Has someone experienced the same thing ? Thanks Paul |
DTC Hull tutorial
Hi all,
I recently started using OpenFOAM (5.1-x on Scientific Linux cluster) for marine hydrodynamics applications. To start with I went through the DTC Hull tutorials that come with the standard installation, the interFoam and interDyMFoam ones. Does anyone know whether there is some more information available about these tutorials, e.g. on how and why boundary condition types, solver settings, schemes, etc. were chosen? I searched through this forum and on Google, but couldn't find much on these tutorials (most of the links posted here no longer work). I'd greatly appreciate any help! Thanks in advance, Sita |
All times are GMT -4. The time now is 02:57. |