Hi all,
I am trying to formulate effect of nCellsBetweenLevels parameter. I have meshed one case with different value.

I was thinking that when nCellsBetweenLevels=10 ( which i thought that is a very high value) there will be 10 cells between 2 levels of refinement in each direction. But as u can see from the screenshots its not like that at all. When i increase the value to 50, i get hardly 6 cells between two levels.

Does anyone can explain me what does the value of nCellsBetweenLevels exactly refers to?

What happened when you set nCellsBetweenLayers to 0? can you upload that picture too?
I have some suggestions if you may consider them as valid point.
1. When you consider a case by default please specify OpenFOAM version so that one can understand which version can reproduce the same results.
2. Since I have observed the definition of some parameters changed with different versions, please give us Dict files so that one can have clear idea about other parameters too.

Thanks a lot for your time and efforts.

Best Regards,
CFDUser_

Quote:

Originally Posted by wyldckat

Greetings to all!

@laymelek: Sorry for the reaaaally late reply. That looks like a bug that existed on that older version of OpenFOAM .

I'm answering to this thread so that questions related to this parameter "nCellsBetweenLevels" this can be discussed in a single thread.

I have some suggestions if you may consider them as valid point.
1. When you consider a case by default please specify OpenFOAM version so that one can understand which version can reproduce the same results.

Coming 2-3 months are like hectic time for me. I will upload some of the valid cases in feature. My analysis are problem specific, so its not good to update in wiki pages. I will find out better way to post as I cant post my current cases as well.

Thanks & Regards,
CFDUser_

Quote:

Originally Posted by wyldckat

Hi CFDUser_,

If you document in that wiki page one or more parameter(s) with which you are already familiar with, I can try next weekend to figure out and document "gapLevelIncrement".

My analysis are problem specific, so its not good to update in wiki pages. I will find out better way to post as I cant post my current cases as well.

Well, the reason why I used one of the cases from the snappyWiki was because it was a very simple case in which certain features can be tested.

It's very likely that if you extract only the problematic location of your geometry and create a base mesh only for that location, you'll be able to test a lot faster and a lot more possible workarounds for the problems you are getting with the whole geometry on that particular location.
Furthermore, those small test cases will then be so unrelated to the real geometry, that it will probably be almost impossible to deduce what it was from.

Beyond this, I'm quoting some feedback you sent me over PM back on August 26th, because this way it'll be easier for me to keep track of the things I still want to do in the near future, and because this way it's kept a public record of who discovered what:

Quote:

Originally Posted by CFDUser_

If you see in your documentation for nCellsBetweenLevels, you said "it's an error of 1 missing layer at level 1" for level 2 to 3. Actual reason is level0 is not exactly equal to base mesh cell size. Its equal to a factor times base mesh level 0 size. That factor is defined to balance number of faces in two different levels fall adjacent to each other. Since for nCellsBetweenLevels 2 the ratio is very high, for the next level (means nCellsBetweenLevels = 3), it won't choose cells in level0 to refine. Instead of the it will refine mode cells in level1.
This explanation will not improve confidence to choose right value for nCellsBetweenLevels but it will give some in-depth understanding for it.

Update if you are fully convinced with reason.

It's the end of the week for me and my brain isn't very cooperative today I'll keep a note to look into this as soon as my brain is rested and able to figure this out