CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM Native Meshers: snappyHexMesh and Others

Do only one snappyHexMesh stage

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old   January 31, 2014, 09:00
Talking Do only one snappyHexMesh stage
  #1
Member
 
James
Join Date: May 2013
Posts: 82
Rep Power: 4
Tensian is on a distinguished road
Hi,

A very simple question. Sometimes I use snappyHexMesh with addLayers option equal to false, because I am only interested in snapping.

If later I want to do only addLayer phase with the previous result obtained from snap (I have 1 folder from castellated and 2 folder from snap), I set addLayers equal to true and the others to false, but in this way snappy does nothing (in 10 seconds it has finished).

Does anybody know how to do only the addLayers stage if you have previously done the two first steps? I am wasting a lot of meshing time doing the three phases in every mesh...

Thanks people!
Tensian is offline   Reply With Quote

Old   January 31, 2014, 17:53
Default
  #2
Member
 
Julian Langowski
Join Date: May 2011
Location: Bremen, Germany
Posts: 91
Rep Power: 6
Ruli is on a distinguished road
Dear Tensian,
a log of snappy would be helpful.
Anyway, just a guess: Is your startFrom entry in controlDict startTime?

Best regards
Julian
__________________
πάντα ῥεῖ - Heraclitus
Ruli is offline   Reply With Quote

Old   February 2, 2014, 10:19
Smile
  #3
Member
 
James
Join Date: May 2013
Posts: 82
Rep Power: 4
Tensian is on a distinguished road
Hi jJulian and thanks for your reply,

In my first try, I was writting this:

FoamFile
{
version 2.0;
format ascii;
class dictionary;
location system;
object snappyHexMeshDict;
}

castellatedMesh true;
snap true;
addLayers false;

Then I ran snappy. When it has finished (I have now 1 and 2 folders corresponding to castellated and snapped phase), I changed to:

FoamFile
{
version 2.0;
format ascii;
class dictionary;
location system;
object snappyHexMeshDict;
}

castellatedMesh false;
snap false;
addLayers true;

and I execute snappy again but nothing is done.

Following your suggestion, I tried the same but I changed in controlDict:

FoamFile
{
version 2.0;
format ascii;
class dictionary;
object controlDict;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

application snappyHexMesh; ///previously I have here the name of the solver for ///simulation

startFrom startTime;
startTime 2; //this means snappy will start from the mesh located at folder "2"?
stopAt endTime;
endTime 3; ////this means snappy will finish when addLayers step writes the
"3" folder?
deltaT 1;
writeControl timeStep;
writeInterval 50;
purgeWrite 0;
writeFormat binary;
writePrecision 6;
writeCompression uncompressed;
timeFormat general;
timePrecision 6;
runTimeModifiable yes;

I am wainting yet but I guess this should work fine. What do you think? I thought that controlDict was only related with execution, not with meshing...

Best regards,

Tensian
Tensian is offline   Reply With Quote

Old   February 2, 2014, 13:54
Default
  #4
Member
 
Julian Langowski
Join Date: May 2011
Location: Bremen, Germany
Posts: 91
Rep Power: 6
Ruli is on a distinguished road
Quote:
Originally Posted by Tensian View Post
Following your suggestion, I tried the same but I changed in controlDict:

FoamFile
{
version 2.0;
format ascii;
class dictionary;
object controlDict;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

application snappyHexMesh; ///previously I have here the name of the solver for ///simulation

startFrom startTime;
startTime 2; //this means snappy will start from the mesh located at folder "2"?
stopAt endTime;
endTime 3; ////this means snappy will finish when addLayers step writes the
"3" folder?
deltaT 1;
writeControl timeStep;
writeInterval 50;
purgeWrite 0;
writeFormat binary;
writePrecision 6;
writeCompression uncompressed;
timeFormat general;
timePrecision 6;
runTimeModifiable yes;

I am wainting yet but I guess this should work fine. What do you think? I thought that controlDict was only related with execution, not with meshing
Hi Tensian,
I am not absolutely sure if controlDict also controls snappy, just was a guess. I would keep it on startTime "latestTime" and application "SOLVER".

How does your snappyHexMeshDict look like?

By the way, the use of
Code:
Code Markers
makes it easier to read it

Best regards
Julian
__________________
πάντα ῥεῖ - Heraclitus
Ruli is offline   Reply With Quote

Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Error in SnappyHexMesh gooya_kabir OpenFOAM Native Meshers: snappyHexMesh and Others 2 October 23, 2013 04:41
Stage Interface errors & requirements Teradil CFX 0 April 16, 2013 02:36
Strange Results With snappyHexMesh calebamiles OpenFOAM Running, Solving & CFD 0 August 14, 2011 16:02
stitchMesh and snappyHexMesh gdbaldw OpenFOAM 0 December 23, 2009 03:09
SnappyHexMesh not generate mesh first time mavimo OpenFOAM Mesh Utilities 4 August 26, 2008 07:08


All times are GMT -4. The time now is 07:41.