iHAMOCC support for tnx0.5v1 grid

[matsbn]

A 0.5 deg tripolar grid, tnx0.5v1, has been prepared for BLOM/CICE and is currently being tested in an OMIP2 simulation using a NorESM2.5 development branch (https://github.com/mvertens/NorESM/tree/feature/noresm2_5_alpha04_v3). To enable iHAMOCC with this grid, some files are needed. The cime_config/namelist_definition_blom.xml has entries for fedepfile, swaclimfile, rivinfile, and ndepfile. Can these files be produced @monsieuralok , @JorgSchwinger , @tjiputra , @TomasTorsvik , @jmaerz?

From BLOM meeting Oct. 24: We will only target NUOPC support for tnx0.5v1 grid resolution.

[tjiputra]

The swaclimfile contains climatology short wave radiation, which i calculated using NCO and 50 yrs blom outputs. So if you have 50 years with monthly outputs of swa variable, this can be created quickly.

The file is required only when running with bromoform. If
USE_BROMO = .false.
then it should work fine without this file.

[mvertens]

@matsbn @TomasTorsvik @jmaerz @JorgSchwinger @tjiputra @monsieuralok - using the CDEPS in line functionality (as was recently done for ingesting SSS and SST grid and time interpolation in the nuopc cap) it seems that I could add functionality to do the same type of interpolatin for the fdep, swaclim, fivinfile and ndepfile. This would eliminate the need to recreate these files every time a new blom grid is introduced. Of course - if a new file was to be needed - then the interpolation could simply be bypassed. I'm happy to take this on if others feel this would be useful. Thoughts?

[JorgSchwinger]

Dear @mvertens, this sounds like a very good idea to me. There are a few things to discuss, maybe this would be something for the upcoming BLOM-core meeting?

[jmaerz]

Dear @mvertens, thanks for the initiative. Technically, the CDEPS solution would be of course a very neat solution. In the meantime, I can provide the N-deposition file (if still needed @JorgSchwinger ?) early next week. In this course, I would like to encourage to think about and discuss, how to best share/store input-preparation scripts (even with the CDEPS approach, this will/might be needed in the future, since I expect that CDEPS requires some particular format).

[mvertens]

@jmaerz - I agree about thinking about the input scripts required moving forwards.

[jmaerz]

Hi @JorgSchwinger and @mvertens , I am about downloading the input4MIP N-deposition data in order to prepare the input files now - opened the issue #397 for this.

[jmaerz]

See also #398.