From 065cd7ac40970dcb08f79df10a8ed109a485ad69 Mon Sep 17 00:00:00 2001
From: Ryan Mulhall <35538242+rem1776@users.noreply.github.com>
Date: Thu, 26 Oct 2023 17:06:00 -0400
Subject: [PATCH] remove line for amip_interp

---
 CHANGELOG.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0e63c2121..35c916395 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -18,7 +18,6 @@ sequential patch number (starting from `01`).
 - MIXED PRECISION: Most directories in FMS have been updated to accept both 4 byte and 8 byte reals as input for public interfaces and routines. This deprecates the `--enable-mixed-mode` option, which enabled similar functionality but was limited to certain directories and was not enabled by default. To facilitate easier testing of these code changes, the CMake precision options for default real size were left in (along with an equivalent `--disable-r8-default` flag for autotools). The resulting libraries will support both real kinds regardless of default real size. It should also be noted that many routines that accept real arguments have been moved to include files along with headers in order to be compiled with both kinds.
 - Some type/module changes were made to facilitate mixed precision support. They are **intended** to have minimal impact to other codebases:
   - COUPLER_TYPES: In coupler_types.F90,  `coupler_nd_field_type` and `coupler_nd_values_type` have been renamed to indicate real kind value: `coupler_nd_real4/8_field_type` and `coupler_nd_real4/8_values_type`. The `bc` field within `coupler_nd_bc_type` was modified to use r8_kind within the value and field types, and an additional field added `bc_r4` to use r4_kind values.
-  - AMIP_INTERP: Several variables and arrays which were previously public have been made private. These variables and arrays are not used in ice_amip or ocean_amip. `amip_interp_type(r4_kind)` and `amip_interp_type(r8_kind)` should be used for `r4_kind` and `r8_kind` precision, respectively. `amip_interp_type` without a kind parameter defaults to `r8_kind`.
   - TRIDIAGONAL: Module state between r4 and r8 calls are distinct (ie. subsequent calls will only be affected by calls of the same precision). This behaviour can be changed via the `save_both_kinds` optional argument to `tri_invert`.
 - CODE_STYLE: has been updated to reflect the formatting used for the mixed precision support updates.