In the NUOPC cap (at least in CESM-MOM6), if I move tauuo and tauvo to a history file that is written every time step then the first time step will be entirely populated by NaNs. This is also the case for nutrient river flux forcing fields in the MARBL driver. For tauuo and tauvo, the calls to post_data() come from mech_forcing_diags() and in mom_ocean_model_nuopc.F90 that call comes immediately after the time step is incremented:
For the river nutrient fluxes, I am reading in the data from call_tracer_set_forcing() (prior to incrementing the time step) and calling post_data() immediately... so I think there might be different mechanisms at play resulting in similar behavior.
In the NUOPC cap (at least in CESM-MOM6), if I move
tauuoandtauvoto a history file that is written every time step then the first time step will be entirely populated byNaNs. This is also the case for nutrient river flux forcing fields in the MARBL driver. Fortauuoandtauvo, the calls topost_data()come frommech_forcing_diags()and inmom_ocean_model_nuopc.F90that call comes immediately after the time step is incremented:For the river nutrient fluxes, I am reading in the data from
call_tracer_set_forcing()(prior to incrementing the time step) and callingpost_data()immediately... so I think there might be different mechanisms at play resulting in similar behavior.