[MITgcm-support] Monthly averaged OBCS with useOBCSYearlyFields

[Naughten, Kaitlin A.]

Hi everyone,

I am trying to run with monthly-averaged OBCS which change every year (useOBCSYearlyFields=true) and a Gregorian calendar meaning the months are different lengths. I am not sure that the code allows me to do this. I have tried two different things:

  1.  Set obcs*period to 2592000 (30 days) and hope that the code turns it into a "real" month, as it does for the diagnostics. This doesn't seem to work as the model dies near the end of the first year when wants a 13th record to interpolate to, and can't find it.
  2.  Set obcs*period to -12 as you do for a repeating monthly climatology. Now the code dies because it's constructing a weird file name which doesn't exist (seems to be either UVEL_piControl.OBCS_N or UVEL_piControl.OBCS_N.001.001.data when it should just be UVEL_piControl.OBCS_N_1979). Looking through the code in obcs_exf_load, it seems that obcs*period=-12 isn't set up to work with useOBCSYearlyFields, because the variables year0 and year1 are never initialised.

What do you suggest I do? Is there a way to set a non-constant OBCS period so the months can be different lengths? Or, an easy way to add this functionality to the code?

Many thanks,
Kaitlin Naughten


Dr Kaitlin Naughten | Ocean-Ice Modeller | British Antarctic Survey

High Cross, Madingley Road, Cambridge CB3 0ET

Email: kaight at bas.ac.uk<mailto:kaight at bas.ac.uk>


This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system.
UK Research and Innovation has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UK Research and Innovation does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.
Opinions, conclusions or other information in this message and attachments that are not related directly to UK Research and Innovation business are solely those of the author and do not represent the views of UK Research and Innovation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20191025/6c824e59/attachment.html>