Requirement

Aug 9, 2012 (mlevy)

Each mixing scheme requires a combination of parameters and physical values for computation. These values need to be read in / calculated by the model and then sent to CVMix.

Design Solution

Aug 9, 2012 (mlevy)

A comprehensive list of the inputs needed for each scheme still needs to be compiled. Regardless of what the inputs are, there are two options for the dimensions of the inputs:

  1. Pass in a single column of water
  2. Pass in an array of columns
Implementation

Aug 9, 2012 (mlevy)

Under discussion, but I like the basic idea Todd outlined in his comment in ??Using CVMix with different ocean models about using a subroutine vmix_put() to update parameters / variables in CVMix. The exact setup of the CVMix datatypes still needs to be determined.

Regarding the "single column vs multiple columns" input: I think it comes down to "should we loop over each column in CVMix or should we loop over each column in the model?" I'm not sure that there is a performance gain either way, but I think conceptually it makes more sense for CVMix to act on a single column with the model responsible for column interactions -- which is to say, I support putting the loop in the model.

  • No labels