# Runoff conservative regrid JRA55 grid to ACCESS-OM2-01

**URL:** <https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678>\
**Category:** COSIMA\
**Created:** [10 December 2025 02:06 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678 "2025-12-10T02:06:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![fabiobdias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/fabiobdias/32/309_2.png) [@fabiobdias](https://forum.access-hive.org.au/u/fabiobdias)\
**Post date:** [10 December 2025 02:06 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/1 "2025-12-10T02:06:05Z")

</div>

Hi everybody,

I’m combining the JRA55-do runoff with a calving flux at the Antarctic margins (already on ACCESS-OM2-01 grid) into a single forcing file. My goal is to regrid the JRA55-do (720x1440) onto the OM2-01 grid (2700x3600), then merge with the calving flux. Just want to see if anyone has done this conservative remapping before and have any tips to share.

In my first attempt I’m using xESMF regridding (following this recipe: [cosima-recipes/03-Mains/Horizontal\_Regridding.ipynb at ebe6a4277a4f9bfe7efaa7f7e618b4777de2dcff · COSIMA/cosima-recipes · GitHub](https://github.com/COSIMA/cosima-recipes/blob/ebe6a4277a4f9bfe7efaa7f7e618b4777de2dcff/03-Mains/Horizontal_Regridding.ipynb) )  
to generate the regridder:

`xESMF Regridder Regridding algorithm: bilinear Weight filename: bilinear_tracer_weights_in025degJRA55_out01degACCESSOM2.nc Reuse pre-computed weights? False Input grid shape: (720, 1440) Output grid shape: (2700, 3600) Periodic in longitude? True`

this seems to work, but I wonder how I can ensure it does not put values in land cells on the OM2-01 grid?

Thank you,

Fabio

---

<div class="post-metadata">

**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\
**Post date:** [10 December 2025 02:24 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/2 "2025-12-10T02:24:46Z")

</div>

Hi Fabio

Will you use the new forcing file in ACCESS-OM2? If so, my understanding is OM2 handles it online / in the model to ensure the runoff doesn’t end up in land cells.

For a calving flux, are you choosing not to spread the runoff in some pattern for meltwater? (e.g. Merino et al. 2016 - [Freswater in the Southern Ocean - Nacho Merino Personal Site](https://neichin.github.io/personalweb/material/meltwater/))

---

<div class="post-metadata">

**Author:** ![fabiobdias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/fabiobdias/32/309_2.png) [@fabiobdias](https://forum.access-hive.org.au/u/fabiobdias)\
**Post date:** [10 December 2025 02:40 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/3 "2025-12-10T02:40:58Z")

</div>

Hi Anton,

yes the idea it to force back ACCESS-OM2 with those fluxes. This run is part of the basal melting project where we prescribed the meltwater at depth in ACCESS-OM2-01 (that I presented in the last NRI workshop).

In this setup, the calving fluxes are hard-wired in MOM5, and internally it’s ensured it goes at surface (upper-40m to be exact), whereas the JRA55-do runoff is inserted at the depths of the ice shelves.

In the experiment I’m setting up, I want to source the JRA55-do runoff + Merino calving flux at the surface–so that’s why I need to combine both into a single file. I want only a Meltwater anomaly to be spread at depth is (which replaced the JRA55-do runoff in the original control setup).

So I’m guessing MOM5 will want to read all in the same field (so the need of combined them after re-gridding etc). Maybe @adele-morrison or @aekiss could advice here too if I missed anything.

Cheers,

Fabio

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [10 December 2025 03:23 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/4 "2025-12-10T03:23:36Z")

</div>

Hi Fabio,

It’s not super clear to me what you’re trying to do - are you trying to split the solid runoff into basal and calving?

Here are some comments/thoughts

- bilinear is not conservative
- why not regrid to (rather than from) the JRA55-do grid and use the model to automatically redistribute it from land to ocean?
- if you’re on the JRA55-do grid you might be able to use this to do what you want [Tutorials · COSIMA/access-om2 Wiki · GitHub](https://github.com/COSIMA/access-om2/wiki/Tutorials#Scaling-the-forcing-fields)
- are you using JRA55-do v.3 or a later version? Only 1.4 and later has separate solid and liquid runoff (but the model combines these before MOM sees them - see [System description · COSIMA/access-om2 Wiki · GitHub](https://github.com/COSIMA/access-om2/wiki/System-description#overview))

---

<div class="post-metadata">

**Author:** ![fabiobdias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/fabiobdias/32/309_2.png) [@fabiobdias](https://forum.access-hive.org.au/u/fabiobdias)\
**Post date:** [10 December 2025 04:13 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/5 "2025-12-10T04:13:02Z")

</div>

Hi Andrew,

I’m trying to set up a control\_LH\_Antwater experiment. I want the control runoff imposed at the surface but the anomalies to be prescribed at a chosen min/max depths and to be adjusted by the Gade line approach. Here we set min\_depth=0 and max depth=40 to match with the control (i.e. we’re effectively prescribing the meltwater at the surface but using the existing code to do the temperature correction).

Investigating Pedro’s code for the basal\_LH\_brine experiment, I realised that calving flux in all our runs are imposed at surface, and the JRA55-do is the runoff passed at depth ([here](https://github.com/pedrocol/basal_routines/blob/master/MOM_routines/easterlies_ICB_brine/ocean_sbc.F90) around line 3696). So I want to use this logic to set up control\_LH\_Antwater as following:

- surface w/o temp. adjustment: JRA55-do runoff (RYF) + Merino calving flux
- surface w/ temp. adjustment: Antwater anomaly and setting

Following that, I want to replace the following files:

- INPUT/ocean\_month\_output\_GPC010\_calving\_365\_final.nc → for a file containing it plus the original JRA55-do runoff. And that where my regridding issues are.

- v1-3/RYF.runoff\_all.1990\_1991.nc → for a file containing only the Antwater anomalies.

Some responses to your comments:

- yes I realised I haven’t used conservative in my first attempt! 😅
- do you think regridding the calving to the JRA55 grid would be easier?
- thanks for the link, it seems like we could have used that to create the MW perturbation.
- using JRAv1.3.

Thank you!

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [10 December 2025 06:05 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/6 "2025-12-10T06:05:10Z")

</div>

Ah ok so with this approach you wouldn’t be using YATM to handle the JRA55 runoff forcing.  
Therefore you’d need to be responsible for conservatively regridding JRA55 runoff onto the same grid as `ocean_month_output_GPC010_calving_365_final.nc`, and ensuring that all the water is mapped to ocean cells.

You’d also need to put all the Antwater anomalies on the same grid as `RYF.runoff_all.1990_1991.nc` if you don’t want to generate new mapping files.

---

<div class="post-metadata">

**Author:** ![fabiobdias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/fabiobdias/32/309_2.png) [@fabiobdias](https://forum.access-hive.org.au/u/fabiobdias)\
**Post date:** [10 December 2025 08:05 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/7 "2025-12-10T08:05:06Z")

</div>

Thanks Andrew, yes that’s exactly the plan. I did regrid the JRA55 runoff to the OM2-01 grid:

 ![JRA55_runoff_regridding](https://us1.discourse-cdn.com/flex020/uploads/access1/original/2X/f/fca1c7c2b4d2d523c443bc9383f9450ca278f784.png)

Though integrating all the values (multiplied by respective grid area) doesn’t give exactly the same amount:

```auto
965702497.956681 (regridded)
965545363.8656995 (original)

```

Checking if there are non-zero values in land points (using land\_mask) does indicate values over land tho:

 ![Screenshot 2025-12-10 at 7.02.13 pm](https://us1.discourse-cdn.com/flex020/uploads/access1/original/2X/4/4cb992e7b9e3eb4f36a534b082f757664f1035a8.png)

Do you have any suggestion on how to avoid this?

---

<div class="post-metadata">

**Author:** ![JuliaN](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@JuliaN](https://forum.access-hive.org.au/u/JuliaN)\
**Post date:** [10 December 2025 09:15 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/8 "2025-12-10T09:15:32Z")

</div>

FYI: [Conservative regridding with xESMF -- puzzled because the integrals don't quite agree - #10 by dkhutch](https://forum.access-hive.org.au/t/conservative-regridding-with-xesmf-puzzled-because-the-integrals-dont-quite-agree/5343/10)

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [10 December 2025 22:27 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/9 "2025-12-10T22:27:51Z")

</div>

> Though integrating all the values (multiplied by respective grid area) doesn’t give exactly the same amount

They’re pretty close - the difference might be accounted for by the summation if you’re using single precision floats.

Is this with conservative or bilinear regridding?

---

<div class="post-metadata">

**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\
**Post date:** [10 December 2025 23:07 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/10 "2025-12-10T23:07:01Z")

</div>

So I think the liquid/river runoff - is still going through yatm (as its part of `RYF.runoff_all.1990_1991.nc`) but the meltwater runoff is handled seperately by `ocean_month_output_GPC010_calving_365_final.nc` ?

I think its important/easiest to use yatm for river runoff so that it spreads the runoff from high volume rivers. Without the spreading there would be issues with low salinity issues at those river mouths.

In the meltwater runoff, where there is overlap between the runoff and land :

a) then some sort of nearest neighbour algorithm could be used to move the water from land to the nearest adjacent cell. In OM3 we currently use a static remapping from land to ocean cells calculated using the BallTree functions from sklearn python package - this is the [link](https://github.com/ACCESS-NRI/om3-scripts/blob/01ea1098133e207c4cc88b920f04af6ea716d642/mesh_generation/generate_rof_weights.py#L93-L105) but google research is probably more useful.

b) the problem with the BallTree approach is that it will just move water to the nearest ocean cell. It might be easier/better just to make some hand edits to move the water to the most appropriate ocean cell (accounting for the different in cell area between cells when moving the water around) - depending how many cells are impacted ofcourse

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [10 December 2025 23:32 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/11 "2025-12-10T23:32:44Z")

</div>

> [@fabiobdias](#):
>
> Checking if there are non-zero values in land points (using land\_mask) does indicate values over land tho  
> Do you have any suggestion on how to avoid this?

YATM does this by conservatively moving runoff to the nearest ocean cells, using a k-d tree to represent cell proximity.

But first check how big a problem it is, i.e. what fraction of runoff is hitting land.

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [10 December 2025 23:53 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/12 "2025-12-10T23:53:32Z")

</div>

> [@anton](#):
>
> I think its important/easiest to use yatm for river runoff so that it spreads the runoff from high volume rivers. Without the spreading there would be issues with low salinity issues at those river mouths.

Good point Anton! Fabio, are you planning to put _all_ the JRA55-do runoff directly into MOM (rather than via YATM), or just the runoff around Antarctica? I don’t think it would work to do it for all runoff globally, for the reasons Anton mentioned. And the river runoff is daily-varying, so that could be a lot of data to handle. Liquid and solid runoff are combined in JRA55-do v1.3, so that makes it awkward to handle them separately.

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [11 December 2025 03:52 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/13 "2025-12-11T03:52:28Z")

</div>

You could use YATM to handle the JRA55-do runoff globally, except with the Antarctic runoff scaled to zero using [Tutorials · COSIMA/access-om2 Wiki · GitHub](https://github.com/COSIMA/access-om2/wiki/Tutorials#Scaling-the-forcing-fields). Then you could apply just the Antarctic JRA55-do runoff directly into MOM in the way you want.

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [11 December 2025 04:00 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/14 "2025-12-11T04:00:25Z")

</div>

However, ACCESS-OM2 normally closes the water budget by imposing a constraint of zero net water flux into the combined ocean-sea ice system from the coupler (zero\_net\_water\_coupler = true) by removing the area-mean of P − E + R (precipitation - evaporation + runoff) from P − E (also adjusting liquid\_precip for consistency) so that the area-integrated P − E + R = 0.

If you’re injecting runoff without passing through the coupler, will your directly-injected runoff be missed in the water budget, leading to incorrect global closure with knock-on effects elsewhere?

See [ACCESS-OM2 water balance - Google Docs](https://docs.google.com/document/d/1gdfU-yDVOl2O6c4LoAno2rNHhWW7LqfI1_4bIS6GPSI/edit?tab=t.0#heading=h.8hwms5y97exg) and sec 3.5.2 in [https://cosima.org.au/wp-content/uploads/2025/10/ACCESS-OM2-1-025-010deg-2025-10-02-b2c815b.pdf](https://cosima.org.au/wp-content/uploads/2025/10/ACCESS-OM2-1-025-010deg-2025-10-02-b2c815b.pdf)

---

<div class="post-metadata">

**Author:** ![fabiobdias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/fabiobdias/32/309_2.png) [@fabiobdias](https://forum.access-hive.org.au/u/fabiobdias)\
**Post date:** [12 December 2025 02:34 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/15 "2025-12-12T02:34:20Z")

</div>

Thanks all for your input @anton@aekiss. It sounds like this is more complex than I initially thought.

Though it look that the regridding works well (figure [here](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/7)), when I account for the land mask it becomes clear that most points with runoff values is located on land. (editting here to add a plot illustrating this; 3/4 of the runoff values are on land cells and only 1/4 is on ocean cells. Plot below has ocean (yellow) and land (purple) mask overlayed with some transparency by the regridded runoff in green-scale colormap:)

 ![test_runoff_regridding](https://us1.discourse-cdn.com/flex020/uploads/access1/original/2X/9/9258bddbb57d229f5108acdc4851b379549c4297.png)

When the JRA55 runoff goes through YATM this is not a problem, but in my case it will be, as the JRA55 runoff will be read straight by MOM5.

I’m inspecting the ocean\_sbc.F90 and these are my insights (from the [“basal” MOM5 code](https://github.com/pedrocol/basal_routines/blob/master/MOM_routines/easterlies_ICB_brine/ocean_basal_tracer.F90)):

1. around line 3696, when using “use\_basal\_module=true’“, it defines, for regions south of 60S:

```auto
basal = runoff - calving

icb = 0 

runoff = calving

calving = 0

```

where **runoff** is coming from YATM (JRA55-do runoff) and **calving** is the calving flux plotted above (already on OM2-01 grid).

1. around line 3740, it defines river = runoff + calving

2. around line 4114, it perform the “zero\_net\_water\_coupler” adjustment calculating:

pme\_river = pme + river + basal + icb + briner - melt - wrk1\_2d

Thus, my thoughts is that this runoff/calving/basal split doesn’t affect the zero net water flux @aekiss ?

If that’s the case, and consider Andrew and Anton inputs here, I think we could do the following to make this work (tagging @adele-morrison here as well):

- JRA55-do runoff file modified to:

- north of 60S: original JRA55-do runoff
- south of 60S: replace original JRA55-do runoff for the Antwater meltwater ANOMALY

-Calving file modified to:

- north of 60S: original calving flux
- **south of 60S: original calving flux + JRA55-do runoff**

In the bold case, the JRA55-do runoff will need to be redirected to ocean cells manually. I will look into @anton suggestion here (BallTree nearest neighbour algorithm).

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [12 December 2025 03:00 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/16 "2025-12-12T03:00:16Z")

</div>

The YATM runoff remapping is described here [GitHub - COSIMA/libaccessom2: ACCESS-OM2 library](https://github.com/COSIMA/libaccessom2?tab=readme-ov-file#river-runoff-remapping)

and the land-\>ocean mapping is done in [libaccessom2/atm/src/kdrunoff\_mod.F90 at master · COSIMA/libaccessom2 · GitHub](https://github.com/COSIMA/libaccessom2/blob/master/atm/src/kdrunoff_mod.F90)  
using [libaccessom2/atm/src/kdtree2\_module.F90 at master · COSIMA/libaccessom2 · GitHub](https://github.com/COSIMA/libaccessom2/blob/master/atm/src/kdtree2_module.F90)

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [12 December 2025 03:22 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/17 "2025-12-12T03:22:07Z")

</div>

Doesn’t `runoff = calving` and `river = runoff + calving` imply `river = 2*calving`? That seems wrong - have I missed something?

see [basal\_routines/MOM\_routines/easterlies\_ICB\_brine/ocean\_sbc.F90 at a54338453cd53e99b94419c3c70071958e1d59e2 · pedrocol/basal\_routines · GitHub](https://github.com/pedrocol/basal_routines/blob/a54338453cd53e99b94419c3c70071958e1d59e2/MOM_routines/easterlies_ICB_brine/ocean_sbc.F90#L3698)

and [basal\_routines/MOM\_routines/easterlies\_ICB\_brine/ocean\_sbc.F90 at a54338453cd53e99b94419c3c70071958e1d59e2 · pedrocol/basal\_routines · GitHub](https://github.com/pedrocol/basal_routines/blob/a54338453cd53e99b94419c3c70071958e1d59e2/MOM_routines/easterlies_ICB_brine/ocean_sbc.F90#L3740)

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [12 December 2025 03:37 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/18 "2025-12-12T03:37:52Z")

</div>

> [@fabiobdias](#):
>
> Thus, my thoughts is that this runoff/calving/basal split doesn’t affect the zero net water flux @aekiss ?

I think that’s true in the unperturbed case, since (if I understand correctly) it’s just splitting the runoff (input via the coupler from YATM, and therefore counted in the ocean budget) between basal and calving.

But what you’re proposing seems different, with JRA55 runoff bypassing the coupler, so it will be missing from the global water budget calculation, which may produce erroneous adjustment (extra global precip) to compensate?

---

<div class="post-metadata">

**Author:** ![fabiobdias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/fabiobdias/32/309_2.png) [@fabiobdias](https://forum.access-hive.org.au/u/fabiobdias)\
**Post date:** [12 December 2025 03:44 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/19 "2025-12-12T03:44:28Z")

</div>

> [@aekiss](#):
>
> true in the unperturbed case, since (if I understand correctly) it’s just splitting the runoff (input via the coupler from YATM, and therefore counted in the ocean budget) between basal and calving.
> 
> But what you’re proposing seems different, with JRA55 runoff bypassing the coupler, so it will be missing from the global water budget calculation, which may produce erroneous adjustment (extra global precip) to compensate?

My impression was that the JRA55 runoff being accounted in the calving array (point 1 in my earlier comment), then passed to river (point 2) would make it being accounted in the pme\_river array (point 3) use for zero net water adjustment? Or did I miss something?

---

<div class="post-metadata">

**Author:** ![fabiobdias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/fabiobdias/32/309_2.png) [@fabiobdias](https://forum.access-hive.org.au/u/fabiobdias)\
**Post date:** [12 December 2025 03:51 UTC](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678/20 "2025-12-12T03:51:59Z")

</div>

I think this is correct as it first defines calving = 0 too:

`if(use_basal_module==.true.) then`  
` do i=isc,iec`  
` do j=jsc,jec`  
` if ( Grd%yt(i,j) < -60.0 ) then`  
` if(use_icb_module==.false.) then`  
` basal(i,j) = runoff(i,j) - calving(i,j)`  
` icb(i,j) = 0.0`  
` runoff(i,j) = calving(i,j)`  
` `**`calving(i,j) = 0.0`**

[Next page](https://forum.access-hive.org.au/t/runoff-conservative-regrid-jra55-grid-to-access-om2-01/5678.md?page=2)
