Add MALI data mode #6945
Add MALI data mode #6945
Conversation
MALI data mode uses the MALI component but rather than making prognostic calculations it reads an ice thickness field from a previous simulation. For now, it is assumed there is a single datamode file per mesh. This could be expanded if needed. Details: * replace MALI%STATIC, which is not being used, with MALI%DATA * set MALI namelist options appropriate for a data mode * add an input stream for data stream to MALI streams file when data mode is activated * add MPAS_DISLISIO_JRA1p5 compset (DIS=Data Ice Sheet) * remove two unused compsets that had reference %STATIC mode
This is necessary for MALI data mode input file, which starts in 2000.
This suppressed irrelevant errors for the oQU240wLI mesh.
The previous changes made all the MALI_DYNAMIC changes in one place at the beginning, causing the subsequent options to get overridden later in the file. Also handle config_SGH.
This change supports three modes instead of two: * PROGNOSTIC=MALI runs prognostically * STATIC=MALI initial condition is held static over time * DATA=MALI thickness is read monthly from a data file
|
Draft version of this PR discussed at E3SM-Ocean-Discussion#111 |
|
It seems like I messed up the compsets with STATIC a couple years back: I think we want to remove both of those and instead have JRA1p5 compsets something like: I think we wouldn't use the DISMF version so let's not add it. @matthewhoffman, if you like, I can do this and push a commit. Then, we would want to add a test like this that uses this compset as well. |
|
I tried to run: and that failed with: I think that probably indicates that the necessary coupling files are maybe not there, another reason to switch to a JRA, rather than CORE IAF, test. |
|
@xylar -- the TL319 resolution is intended for JRA forcing. If you want to use CORE-II, the datm resolution should be T62 |
|
@jonbob, that makes sense and fits with the need to move away from the CORE-IAF and to the JRA1p5 forcing for MALI static mode as I already suggested above. |
We don't anticipate supporting or using this compset
|
Oh, sorry, I see. I just used the wrong atmosphere grid in my test. My mistake! |
|
@matthewhoffman, I made the compset and test changes. I successfully ran: |
| <alias>GMPAS-JRA1p5-DIB-PISMF-SIS</alias> | ||
| <lname>2000_DATM%JRA-1p5_SLND_MPASSI%DIB_MPASO%IBPISMFDATMFORCED_DROF%JRA-1p5_MALI%SIASTATIC_SWAV</lname> |
There was a problem hiding this comment.
@matthewhoffman, are you good with the SIS name here?
There was a problem hiding this comment.
@xylar , yes, I like the SIS name in the compset, and I agree the GLC component should use the %SIASTATIC variant.
|
Testing on Chrysalis
|
|
From But the test duration was 59 days, so I'm not sure where the 126 days is coming from. cpl log indicates that memory highwater was not at the end of the run: @jonbob, do you have any thoughts on this? |
This PR introduces a data mode for MALI that allows GLC to be active but the MALI ice thickness be prescribed from a previous MALI run. This capability is added by introducing a new component variable MALI_PROGNOSTIC_MODE, which replaces the existing MALI_DYNAMIC variable. MALI_PROGNOSTIC_MODE can take on values of PROGNOSTIC (full MALI model), STATIC (ice thickness held at its initial value), and DATA (ice thickness updated monthly from a specified MALI history file). A new compset is added to that include MALI in data mode in a G-case (GMPAS-JRA1p5-DIB-PISMF-DIS). A datamode history file is added for the mpas.ais8to30km mesh. The DATA and STATIC modes are needed for developing ocean/ice-sheet coupling and SMB evaluation in BG cases.