Personal tools

Difference between revisions of "Module LagrangianGlobal"

From MohidWiki

Jump to: navigation, search
Line 30: Line 30:
 
=== Goal 3 - Decrease redundances in Lagrangian_x.dat ===
 
=== Goal 3 - Decrease redundances in Lagrangian_x.dat ===
  
To decrease this redundance the "clone origin" concept was created. There are several origins options [[Editing Module Lagrangian (section)]]
+
To decrease this redundance the "clone origin" concept was created. There are several [[Module Lagrangian#Concepts|Lagrangian Origins]] options.
  
  
 
[[Category:Modules]]
 
[[Category:Modules]]
 
[[Category:MOHID Water]]
 
[[Category:MOHID Water]]

Revision as of 15:16, 21 March 2011

Overview

The LangrangianGlobal Module is a deep upgrade of the Lagrangian Module. These upgrade has three main goals:

1 - Run only one lagrangian model in a multi-nesting implementation. This way particles can go from grid to grid without any problems (Media:SideBySideCloud.gif). In the Lagrangian module particles are destroyed when they leave the grid where they were emitted. This is the reason way a lagrangian model is runned for each grid in the Lagrangian Module;

2 - Centralise all the interpolation and particle location (in a grid) methods in Module HorizontalGrid and (see source code [1]);

3 - Avoid redundances in the particle origin definitions. This way is possible to compress the input file (Lagrangian_x.dat).

Goal 1 - Run only one Lagrangian Model

The LagrangianGlobal module is a module very similar to the Lagrangian module. The input data file keywords are exactly the same. The modules give the same lagrangian result if the user only runs one model (no nesting). In the case of the first module when are run several nesting levels. The user only define one lagrangian input data file in the data file of the first nesting level (first model in the tree.dat). Each lagrangian tracer will use the hydrodynamic field with the higher priority depending on the tracer position. By default the priority is define inverting the tree.dat order. The user can specify the oder using a block define in the lagrangian input file where the user can define the model priority:

<BeginModelPriority> 
Model name x
Model name y
<EndModelPriority>

The first model are the one with the higher priority.

If the mohid user wants to activate this module it needs to predefined a preprocessor symbol called _LAGRANGIAN_GLOBAL_ in the compilation phase of the mohid.

Goal 2 - Centralize all interpolation and particle location methods

Relative position of particle


Goal 3 - Decrease redundances in Lagrangian_x.dat

To decrease this redundance the "clone origin" concept was created. There are several Lagrangian Origins options.