Check units and ranges for forcing fields

[nichannah]

Strange things happen when forcing fields are in wrong/unexpected units. It can take a long time to find these problems, for example the confusion we had when we switched the CORE to JRA55 runoff fields and the units changed.

It would save a lot of time in the long run if we did some sanity checking on incoming fields. In this case of MATM this could be done without any hit to overall performance (because it does nothing most of the time anyway).

[ofa001]

Its possible we might want to use some CFSR forcing fields as well to match a CFSR wave climatology that Mark Hemer created that myself and Luke Bennetts have used with the old accice set up. We are going to have some discussions this week about whether we switch to using COSIMA and meet with other groups in the UK doing wave-ice interaction. Luke’s been here for a couple of weeks so been talking already, I caught a cold on the plane over so been less sociable. From: Nic Hannah [mailto:notifications@github.com] Sent: Tuesday, 12 September 2017 12:14 PM To: OceansAus/access-om2 <access-om2@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [OceansAus/access-om2] Check units and ranges for forcing fields (#38) Strange things happen when forcing fields are in wrong/unexpected units. It can take a long time to find these problems, for example the confusion we had when we switched the CORE to JRA55 runoff fields and the units changed. It would save a lot of time in the long run if we did some sanity checking on incoming fields. In this case of MATM this could be done without any hit to overall performance (because it does nothing most of the time anyway). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#38>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANrRgmuCdz-YVKmjO-7WTn059CVrqfueks5shejfgaJpZM4PUAZa>.

[nichannah]

Moved to COSIMA/libaccessom2#9