GfsParticle

From Gerris

(Difference between revisions)
Jump to: navigation, search
Revision as of 00:30, 22 March 2010
Delauxs (Talk | contribs)

← Previous diff
Current revision
Popinet (Talk | contribs)
(removed redundant/confusing syntax definition for GfsParticleList)
Line 1: Line 1:
-A [[GfsParticle]] is basically an inert Lagrangian particle.+A GfsParticle is a basic inert Lagrangian particle.
-It can be used as a particle type to define a list of Lagrangian particles ([[GfsParticleList]]).+
-Each [[GfsParticle]] is characterised by its id number (interger) and position (X,Y,Z).+
-The [[GfsParticle]] particle object is derived from [[GfsEvent]] but does not inherit of its read/write method i.e. timing (start, end ...) cannot be specified directly for a [[GfsParticle]] but has to be specify for the whole [[GfsParticleList]].+The syntax in parameter files is
-* [[GfsEvent]]+ ID X Y Z
-** [[GfsParticle]]+ 
 +where <code>ID</code> is a unique identifier (an [http://developer.gnome.org/glib/unstable/glib-Basic-Types.html#guint unsigned integer]) and <code>(X,Y,Z)</code> the particle position.
 + 
 +Although GfsParticle is derived from [[GfsEvent]], it inherits neither its read nor write methods, so timing (start, end ...) is not specified individually but only for whole [[GfsEventList]]s of particles.
 + 
 +Particles with more properties can be created using the [[GfsParticulate]] subclass.
 + 
 +<examples/>

Current revision

A GfsParticle is a basic inert Lagrangian particle.

The syntax in parameter files is

ID X Y Z

where ID is a unique identifier (an unsigned integer) and (X,Y,Z) the particle position.

Although GfsParticle is derived from GfsEvent, it inherits neither its read nor write methods, so timing (start, end ...) is not specified individually but only for whole GfsEventLists of particles.

Particles with more properties can be created using the GfsParticulate subclass.


Personal tools
communication