|Subject:||Re: [ESPResSo-users] boundary cmd warning|
|Date:||Thu, 15 May 2014 11:55:33 +0200|
OK, I answered myself:
lbboundary wall normal 0 1 0 dist 1
solves the problem.
Looks like you cannot put the lbboundary at the origin. Is this the
expected behavior? In case, should the special case dist==0 checked
for in the interface?
On Wed, May 14, 2014 at 8:33 PM, Marcello Sega
> Dear all,
> with this simple script:
> setmd box_l 10 10 10
> setmd skin 0.0
> thermostat off
> setmd time_step 0.01
> lbfluid gpu agrid 1 dens 1.0 visc 1.0 tau 1.0
> lbboundary wall dist 0.0 normal 0. 1. 0.
> integrate 0
> I get the following warning
> WARNING: boundary cmd executed but no boundary node found!
> If I call lbboundary before lbfluid, I get instead:
> WARNING: Specifying boundaries before using lbfluid assumes a CPU
> implementation of the LB.
> WARNING: This will lead to unexpected behavior if a GPU LB fluid is
> later used since the boundaries wont exist.
> What is happening ? Is it a "serious" warning, like, e.g., really no
> boundary node has been set?
> I'm kind of lost in the various init/reinit routines, so I cannot
> trace it back and understand what is going on. Maybe somebody out
> there has some experience with it to share...
> Kind Regards,
> Institut für Computergestützte Biologische Chemie
> University of Vienna
> PGP public key on MIT server http://goo.gl/zlIZix
Institut für Computergestützte Biologische Chemie
University of Vienna
PGP public key on MIT server http://goo.gl/zlIZix
|[Prev in Thread]||Current Thread||[Next in Thread]|