COMPUTE INTERFACE VELOCITIES AND LOAD UP GHOST CELLS
FOR FLUID STATE VARIABLES
Note that it is done on a per species basis
5/23/2015 - may need to be changed for 2D/1D sims which
have only one element in the x2 direction...
v1i(lx1+1,:,:)=v1i(lx1,:,:) !avoids issues with top boundary velocity spikes which may arise vadvx1(1,:,6)=mean(vadvx1(1,:,6)); !for eq sims
FOR INTERNAL ENERGY
we only need one ghost cell to compute interface velocities
NOW DEAL WITH ADVECTION ALONG X3; FIRST IDENTIFY MY NEIGHBORS
PASS X3 VELOCITY BOUNDARY CONDITIONS WITH GENERIC HALOING ROUTINES
we only need one ghost cell to compute interface velocities
AFTER HALOING CAN COMPUTE THE X3 INTERFACE VELOCITIES NORMALLY
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.