yade-dev team mailing list archive

[chiara modenese <c.modenese@xxxxxxxxx>]

2010/4/12 Václav Šmilauer <eudoxos@xxxxxxxx>

> > My current point of view is relying only on what I can find in your
> > presentation you did in Grenoble : "PartialEngine : act on some
> > bodies/interactions" (whereas "GlobalEngine : act on all
> > bodies/interactions") in slide 13.
> > So from what I understand from this, I would consider
> > "BoundaryController", which I see as Engines modifying directly the
> > position, speed... of few bodies, as PartialEngines.
>
> You have a point. It is a matter of interpretation, though.
>
> You act on a few bodies, but those bodies represent boundary conditions
> and you want to control the whole packing with them.... The same would
> be true for TriaxialStressController, which also controls only 6 bodies
> in fact...
>
> In the contrary case, the distintion would be almost meaningless, as
> among GlobalEngines, there would be perhaps ForceResetter and gravity
> engines. Then periodic engines (PeriIsoCompressor and
> PeriTriaxController would be in different groups, which doesn't seem
> very logical...)
>
> Some opinions from other people?
>
> v
>
> I think it is the definition of PartialEngine that has to be stated
clearly. Actually, I found this definition in ForceEngine where it says that
a PartialEngine should act only on some bodies modyfing velocity, position
and so on. This definition can obviously lead to some misunderstanding (as
pointed out by Jerome) since, for instance, TriaxialStressController is
actually working only on certain bodies in the simulation.That said, perhaps
we should find a different definition for PartialEngine. Or simply create
new blocks of Engines as rightly proposed by Vaclav.


I vote positive for those two new group engines (it is a logical and
intuitive distinction).


BTW, we have a couple of folders (I think, since I am not properly using the
last release), one called GlobalEngine and another one called PartialEngine
inside /pkg/dem/Engine. What is here the meaningful of the distinction? It
is just to know for future commitments. For instance in /pkg/dem/meta folder
I see ViscoelasticPM files that is a contact law, and in
/pgk/dem/Engine/GlobalEngine other contact laws, like
CohesionlessMomentRotation. Which folder should go a contact law into? With
a contact law, I mean not only the law functor lonely but say a collection
of classes like in ViscoelasticPM or HertzMindlin.


Cheers, Chiara



> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev<https://launchpad.net/%7Eyade-dev>
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev<https://launchpad.net/%7Eyade-dev>
> More help   : https://help.launchpad.net/ListHelp
>