In POP2, there is an error check to make sure the sum of per-ice-category fields are close to the aggregate values passed from the ice model:
if ((abs(qsw_col_dagg_1pt) > mcog_dagg_qsw_abort_thres) .or. &
(abs(qsw_bin_dagg_1pt) > mcog_dagg_qsw_abort_thres)) then
this_block = get_block(blocks_clinic(iblock),iblock)
write(stdout, '(a,2(1x,a,i0),2(1x,a,e13.6))') &
'qsw aggregation mismatch exceeds threshold', &
'i_glob=', this_block%i_glob(i), &
'j_glob=', this_block%j_glob(j), &
'qsw_col_dagg_1pt=', qsw_col_dagg_1pt, &
'qsw_bin_dagg_1pt=', qsw_bin_dagg_1pt
call shr_sys_abort ('Error: (ocn_import): qsw aggregation mismatch exceeds threshold')
endifWhen I brought the per-ice-category fields into MOM6, I cut out a lot of the complexity from the POP2 code... in doing so, I also removed this error check and it should be implemented before the CESM 3.0 release. Note that we have verified CICE6 was passing this error check in CESM 2.3 beta tags and we do not expect issues in the current MOM6 code base, but it's still a good error check to have (one of our collaborators triggered this abort when modifying POP2 code in an experiment)
In POP2, there is an error check to make sure the sum of per-ice-category fields are close to the aggregate values passed from the ice model:
When I brought the per-ice-category fields into MOM6, I cut out a lot of the complexity from the POP2 code... in doing so, I also removed this error check and it should be implemented before the CESM 3.0 release. Note that we have verified CICE6 was passing this error check in CESM 2.3 beta tags and we do not expect issues in the current MOM6 code base, but it's still a good error check to have (one of our collaborators triggered this abort when modifying POP2 code in an experiment)