A FILE INPUT BASED BOUNDARY CONDITIONS FOR ELECTRIC POTENTIAL OR
FIELD-ALIGNED CURRENT.
NOTE: THIS IS ONLY CALLED BY THE ROOT PROCESS
COMPUTE SOURCE/FORCING TERMS FROM BACKGROUND FIELDS, ETC.
do not allow a background parallel field
bit of code duplication with worker code block below...
IF WE HAVE SINGLETON DIMENSION, ALLOCATE SOME SPACE FOR TEMP ARRAY INPUT TO INTERP1
NOW READ THE GRID
SPACE TO STORE INPUT DATA
these need to be initialized so that something sensible happens at the beginning
by default the code uses 300km altitude as a reference location, using the center x2,x3 point
GRID INFORMATION EXISTS AT THIS POINT SO START READING IN PRECIP DATA
read in the data from file
get the date for "next" params
will work even for 2D grids, just repeats the data in the lon direction
both min and max need to be read in from file and interpolated
Note: for 2D simulations we don't use Vmaxx2p, etc. data read in from the input file - these BC's will be set later
source data is 2D
UPDATE OUR CONCEPT OF PREVIOUS AND NEXT TIMES
INTERPOLATE IN TIME (LINEAR)
make sure to set solve type every time step, as it does not persiste between function calls
full 3D grid need to also handle lateral boundaries
SOME BASIC DIAGNOSTICS
LOAD POTENTIAL SOLVER INPUT ARRAYS, FIRST MAP THE ELECTRIC FIELDS
define a reference metric factor for a given field line
NOW THE BOUNDARY CONDITIONS
full 3D grid
some type of 2D grid, lateral boundary will be overwritten
Dirichlet: needs to be the same as the top corner grid points
Neumann in x1: sides are grounded...
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.