Strange issue with FreeSurface field definition

[stonepreston]

Most of what Ive done so far is based on the breakingDam3D tutorial. I am encountering an issue with the defined FreeSurface fields. For some reason, they are only applying to part of my geometry. The geometry is set up correctly (I think, still pretty new to this). The outer shell of my geometry looks like this in paraview (all outer cells are material 0):

https://ibb.co/sDvYCzM

I set the FreeSurface cell type using the following code:

AnalyticalConst3D<T,T> four( 4. );
sLattice.defineField<FreeSurface::CELL_TYPE>(superGeometry, 0, four);

However the field looks like this when viewed in paraview:

https://ibb.co/2YmDmrNy

Its only applying to a portion of the geometry instead (I would expect the entire outer shell to be red since that is all material 0)

Does anyone have any idea what is going on?

• This topic was modified 11 months, 2 weeks ago by stonepreston.
• This topic was modified 11 months, 2 weeks ago by stonepreston.

[stonepreston]

I tested whether this was a problem with only FreeSurface fields by adding a custom field to the descriptor. The custom field has the same problem.

This mainly seems to be affecting material 0 on the outer surface. If I apply fields to other materials inside the surface it looks correct, but its just that outer portion from x=10 onwards that isnt right.

[mathias]

Did you initialize the fields also at nodes with material number zero? Any fields needs to be initialized at all material numbers correctly!

[stonepreston]

Did you initialize the fields also at nodes with material number zero? Any fields needs to be initialized at all material numbers correctly!

Is that not what this line does?

sLattice.defineField<FreeSurface::CELL_TYPE>(superGeometry, 0, four);

I thought that would initialize any node with material number 0 in the lattice to 4? Is there something more that needs to be done?

• This reply was modified 11 months, 1 week ago by stonepreston.

[stonepreston]

This appears to not affect the simulation, I think it might be due to cleaning boundary cells in conjunction with not adding a layer around my STL.

[Author]

Posts