The input boundary data in #2 is coded to be daily frequency available yearly. It may be easier/more flexible to handle input via CDEPS inline. CICE already has CDEPS inline, for "prescribed ice" mode (https://github.com/CICE-Consortium/CICE/blob/main/cicecore/drivers/nuopc/cmeps/ice_prescribed_mod.F90#L181-L202) and we could leverage from it.
The input boundary data in #2 is coded to be daily frequency available yearly. It may be easier/more flexible to handle input via CDEPS inline. CICE already has CDEPS inline, for "prescribed ice" mode (https://github.com/CICE-Consortium/CICE/blob/main/cicecore/drivers/nuopc/cmeps/ice_prescribed_mod.F90#L181-L202) and we could leverage from it.