[luckyluke]

I work on the solver 'interFoam'.

I want to add a few codes in it to track the interface. Initial 'Gamma' field are defined using 'setGammaDamBreak'. I store the initial interface points with array.

In the code, the gamma, pd and U are updated using original VOF method. Then the interface points defined in the array are updated according to dx/dt=u,dy/dt=v, etc. The velocity u and v of the interface point is approximated using the value of the nearest cell.

Unfortunately, I can only achieve oscillating interface instead of smooth one. Why? What should be modified in my code?

Thank all.

[eugene]

Interpolate the U field onto your interface points instead of using the cell values.

Why do you want to track the interface with marker particles?

[rolando]

I´m checking in and out "geometricField"-objects in the object-registry on demand by using "regIOobject::checkIn()" and "regIOobject::checkOut()". That works fine.
Can anyone tell me if there is a method to check, whether a specific object is checked in or out?
As I see "regIOobject::registries()" doesn´t work as it just checks the ownership and not the status.
Rolando

[mattijs]

you could either add a const access function to the registered_ flag in regIOobject and recompile

or you can check the objectRegistry itself (access with db()) whether the object is registered:

objectRegistry::foundObject(...)

Why do you have to checkin/checkout manually?

[rolando]

Thanks Mattijs,
as I don´t want to manipulate the Foam core functionality I chose the second suggestion.
The reason to checkIn/Out is: I do some averaging of the simulation results. Which field´s to average is runtime selectable to save both memory and disk space. Therefore I do manually checkIn/Out of the geometricFields.
Rolando

[niklas]

This can be done more easily by just reading name-lists of
scalar/vector/tensor fields of the variables you want to average and adding them to the main application.

Much similar to the problem being discussed in the 'pollutant dispersion...' thread.

...or have i missed something.

N

[rolando]

Thanks Niklas,
I think that´s what I´m actually doing.
I do a runtime lookup of the field names to average. I create the fields and store them in a table (not a list).
As the fields should also be destroyed when they are no longer used, I (think I) need to check them out before destoying them.
It seems to work.

Rolando

[henry]

The checkIn and checkOut are automated, you shouldn't need to call these functions yourself.
When you destroy the field it should check itself out of the database however checking it out yourself should not cause any problems it's just unnecessary.

[rolando]

CheckingIn is done automated. I do not have to call "checkIn()".
I store the fields in a "HashPtrTable". When I destroy them by calling "HashPtrTable::erase()" the field is not checked out of the database. At least calling "objectRegistry::names()" still displays the name of the field. If I call "checkOut()" before calling "HashPtrTable::erase()" the field name doesn´t appear any longer.

[henry]

It looks like you are creating a copy which you are deleting but leaving the original in the database.

[rolando]

Thanks Henry
That´s not good. I have to check this out.

Rolando

[rolando]

As you said Henry. Now it works fine.
Thanks
Rolando