new standard CICE outputs at each resolution

[aekiss]

Similar to the standardised MOM outputs (issue https://github.com/COSIMA/access-om2/issues/203), I'm seeking input on the sea ice diagnostics we should generate by default from CICE in the new standard configurations.

Some basic objectives and constraints:

1. identical outputs for IAF and RYF at each resolution
2. a complete basic set across all three resolutions to facilitate resolution-dependence studies, plus an additional identical set of secondary diagnostics at 1 deg and 0.25 deg (ie omit secondary diagnostics at 0.1 deg to save storage)
3. minimise daily outputs - they drastically slow down the model at high resolution (at least until PIO is implemented: https://github.com/COSIMA/cice5/issues/34) and consume a lot of storage
4. minimise repeated storage of static fields, e.g. grid data: https://github.com/COSIMA/access-om2/issues/201

The output fields are defined in the several &icefields_*nml sections of the following files:

• 1 deg: cice_in.nml
• 0.25 deg (same as 1 deg): cice_in.nml
• 0.1 deg: cice_in.nml

A table highlighting differences between 1/0.25deg and 0.1 deg is here.

Fields are defined as f_<fieldname>, with 'm' and 'd' specifying monthly and daily means, respectively. 'x' indicates that the field will not be output. At present there are no daily outputs.

Some questions:

1. Am I missing anything important?
2. Is there anything that should be removed?
3. is there anything that really needs to be daily?

[willrhobbs]

Hi Andrew

As a bare minimum, I would request daily f_aice and f_hi fields; I think the work I showed at the COSIMA workshop on the 2016 sea ice loss indicates that the daily resolution is important. Still important (but possibly less crucial), would be daily f_hs, f_dvidtt and f_dvdtd

I'd also request the following monthly fields: f_dvidtt, f_dvdtd, f_daidtt, f)daidtd, f_snoice

I'm tempted to say that f_sig1 and f_sig2 aren't that helpful, but they may be really important ofr your/Petra's evaluation work. I can't see me using them though

[aekiss]

OK thanks @willrhobbs. Would there also be interest in daily area and thickness broken down by thickness category (aicen and vicen) or are the totals all you'd want?

[willrhobbs]

For me personally, no; those thickness categories were defined for the Arctic and I'm not sure they're that helpful fro Antarctic. Plus, I can always use hi to set my own thickness categories.

In regard to my previous post regarding daily data, I just realised that with some relatively simple offline calculations, from aice, hi, dvidtd (and possibly snoice) you could completely nail down the daily freeze/melt processes

[aekiss]

The thickness categories in vicen are not recoverable from hi - they form a histogram of the ice thickness distribution within each grid cell, whereas hi is just the total across all thicknesses categories in each cell.

[ofa001]

Hi Andrew, Will

Most of the list is Ok, I would suggest snoice for bth you have it on in 1 degree off in 0.1 degree also with ktherm2 it might be useful to ook at some point at tinz and sinz but that does through off some of the systems as you have 4-D data fields so we have dropped it from ACCESS -CM2 output.

For daily data for CMIP6 submission we had hi aice, hs uvel vvel which can be useful.

Cheers Siobhan

From: willrhobbs notifications@github.com Sent: Friday, 5 June 2020 3:05 PM To: COSIMA/access-om2 access-om2@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [COSIMA/access-om2] new standard CICE outputs at each resolution (#207)

Hi Andrew

As a bare minimum, I would request daily f_aice and f_hi fields; I think the work I showed at the COSIMA workshop on the 2016 sea ice loss indicates that the daily resolution is important. Still important (but possibly less crucial), would be daily f_hs, f_dvidtt and f_dvdtd

I'd also request the following monthly fields: f_dvidtt, f_dvdtd, f_daidtt, f)daidtd, f_snoice

I'm tempted to say that f_sig1 and f_sig2 aren't that helpful, but they may be really important ofr your/Petra's evaluation work. I can't see me using them though

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/COSIMA/access-om2/issues/207#issuecomment-639260694, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADNNDAT7SPSUGWC22LB2SALRVB4IVANCNFSM4NTGN4HQ.

[aekiss]

Thanks @willrhobbs and @ofa001 , I've made your suggested changes (except for f_tinz and f_sinz) - see diffs above.

I've also removed f_frz_onset and f_mlt_onset which are designed for the Arctic and in any case don't work with the 3mo runs at 0.1deg, and removed f_sig1 and f_sig2.

[access-hive-bot]

This issue has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/standard-ocean-outputs-for-esm1-5/2265/13