compass.landice.tests.ismip7_calibration.ais.melt_model.read_run

compass.landice.tests.ismip7_calibration.ais.melt_model.read_run(filename, mesh_file)[source]

Read the fields a melt diagnostic run writes.

Parameters:

filename (str) – An output_melt.nc written by a RunState step
mesh_file (str) – The MALI mesh file the run started from, used for the geometry the melt was computed from

Returns:

fields (dict) – melt (kg m-2 yr-1, positive for melting), tf_draft, floating, basin (MALI’s 1-based numbering), delta_t and area

Notes

The contributing cells come from the initial geometry, not from the output. MALI computes melt where the ice is floating and the cell is connected to the open ocean, evaluated on the geometry at the start of the timestep. The cellMask in the output is post-step, and over a single step some cells with no ice at the start end up with a trace of it, so the output mask marks thousands of cells as floating that MALI never computed melt for. Their melt is zero, which does not change an integral, but it would dilute the area-weighted basin means that J3 is built from – and it would make any comparison against an independent implementation disagree on cells MALI never calculated.