Hello.
I'm running CICE5 + DART, and it worked as a "coupled system", not "standalone system".
In my case, i used two components of forcing: atmosphere and ocean.
The atmosphere uses forcing data uploaded to NCAR RDA, and the ocean uses pop_frc.gx1v6.100513.nc obtained via check_input_data.
When considering forcing when using CICE5 as a "standalone system", i've used to deal with ice_forcing.F90.
However, I think that in the current "coupled system", forcing data is not operated by ice_forcing.F90.
So my question is, I wonder what process forcing goes through in this "coupled system".
I know that the xxx_in file is modified from the user_nl_xxx file and the xxx_in file is finally read, but I still don't understand how the input is read.
Thanks for read this.
Inchae chung
I'm running CICE5 + DART, and it worked as a "coupled system", not "standalone system".
In my case, i used two components of forcing: atmosphere and ocean.
The atmosphere uses forcing data uploaded to NCAR RDA, and the ocean uses pop_frc.gx1v6.100513.nc obtained via check_input_data.
When considering forcing when using CICE5 as a "standalone system", i've used to deal with ice_forcing.F90.
However, I think that in the current "coupled system", forcing data is not operated by ice_forcing.F90.
So my question is, I wonder what process forcing goes through in this "coupled system".
I know that the xxx_in file is modified from the user_nl_xxx file and the xxx_in file is finally read, but I still don't understand how the input is read.
Thanks for read this.
Inchae chung