[giampippetto]

Hi,

I'm using icoTopoFoam to study the use of topological changes in the mesh; with the sliders i'm ok, but I have problems wit layer addition/removal.
The following case stops when it tries to remove a cell layer: lvl_3d.zip

I've tried to set up another case, but this one doesn't even start, the solver gives this error:

--> FOAM FATAL ERROR : gradientInternalCoeffs cannot be called for a calculatedFvPatchField.
You are probably trying to solve for a field with a calculated or default boundary conditions.

From function calculatedFvPatchField<type>::gradientInternalCoef fs() const
in file fields/fvPatchFields/basicFvPatchFields/calculated/calculatedFvPatchField.H at line 174.

FOAM exiting

linearValveLayers.tar.gz

I've double-checked my boundary conditions and all other things but I can't find anything wrong, can you give me some help?

Thanks
Andrea

[hjasak]

This is the message you get when a calculated boundary condition is created in one of your fields as default. The code cannot work with the calculated patch field type because calculated means "I don't know what to do here".

Find out which field has got the calculated b.c. and how it got there, once you fix that, all will be well.


Hrv

[giampippetto]

Well, i've rewritten another case from scratch, I don't know what's changed exactely but now it works. If you find it useful, you can include this case as an example case in openfoam.

btw, i haven't clear yet if there is some real difference between insideSlider and outsideSlider, can someone explain me this? I mean, can insideSlider and outsideSlider be safely swapped?

Bye
Andrea

linearValveLayers.tar.gz

[hjasak]

btw, i haven't clear yet if there is some real difference between insideSlider and outsideSlider, can someone explain me this? I mean, can insideSlider and outsideSlider be safely swapped?

Only in point projection. The slave patch gets projected onto the master and in cases where the shape of the two sides is not identical, it is the master that preserves its shape. In general, projecting the points one way is "easier" :-) that the other (also means faster, because the algorithm is a surface wals with corrections) so that's the criterion you should use.

Enjoy,

Hrv

[giampippetto]

Hi,

I still have problems with the 3d case, when it's time to remove a layer the courant number rises quickly until it aborts. I've tried several things like changing the grid, the piston speed and other things but with no results, so... what should I care about when setting up a layer addition/removal case?

Thanks
Andrea