Time transformations

• LOCTRANS:

  LOCTRANS requires one configuring line on which a time transformation, automatically performed below the call to oasis_put, should be indicated:

   # LOCTRANS operation
     $TRANSFORM
  

  
  where $TRANSFORM can be
  • INSTANT: no time transformation, the instantaneous field is transferred;
  • ACCUMUL: the field accumulated over the previous coupling period is exchanged (the accumulation is simply done over the arrays field_array provided as third argument to the oasis_put calls, not weighted by the time interval between these calls);
  • AVERAGE: the field averaged over the previous coupling period is transferred (the average is simply done over the arrays field_array provided as third argument to the oasis_put calls, not weighted by the time interval between these calls);
  • T_MIN: the minimum value of the field for each source grid point over the previous coupling period is transferred;
  • T_MAX: the maximum value of the field for each source grid point over the previous coupling period is transferred;
  • ONCE: UNUSED ; not supported in OASIS3-MCT.

  With OASIS3-MCT, time transformations are supported more generally with use of the coupling restart file. The coupling restart file allows the partial time transformation to be saved at the end of a run for exact restart at the start of the next run. When LOCTRANS transformations are specified, the initial coupling restart file should not contain any LOCTRANS restart fields. For the following runs, it is mandatory that the coupling restart file contains LOCTRANS restart fields coherent with the current namcouple entries. For example, it will not be possible to restart a run with a multiple field entry in the namcouple with a coupling restart file created by a run not activating this multiple file option. This is also the reason why it is now possible to specify a restart file name on the OUTPUT namcouple input line.