You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't want to rely on io_fallback to initialize the cocco tracers. I wrote a python script to add cocco tracers to the existing initial condition files, but it doesn't quite capture coccoP correctly... the Fortran code was doing this:
and I'm having trouble generating a coccoP field in the netCDF that exactly matches this. I think what I need to do is write a Fortran program to overwrite this field with spC*(1/117) (unless the problem is that io_fallback is using (1/117)*spC
The text was updated successfully, but these errors were encountered:
Kristen is testing a non-bfb option to see if it still looks okay. Last question will be for Keith: should we just use the new initial condition file (identical to old one except for new cocco fields) all the time?
Modifications for adding spatial sst filter.
Description of changes:
Added functionality to allow spatial filtering of the SST. This is turned off by default and enabled by
"l_sst_filter = .true."
Testing:
Test case/suite:
Test status: bit for bit by default
Fixes [POP2 Github issue #]
N/A
User interface (namelist or namelist defaults) changes?
Yes, new namelist options and group (filter_nml). Default is that filtering is turned off.
We don't want to rely on
io_fallback
to initialize thecocco
tracers. I wrote a python script to addcocco
tracers to the existing initial condition files, but it doesn't quite capturecoccoP
correctly... the Fortran code was doing this:and I'm having trouble generating a
coccoP
field in the netCDF that exactly matches this. I think what I need to do is write a Fortran program to overwrite this field withspC*(1/117)
(unless the problem is thatio_fallback
is using(1/117)*spC
The text was updated successfully, but these errors were encountered: